Solution Architecture - Revision history

User at 00:08, 28 March 2024

2024-03-28T00:08:47Z

User at 16:30, 26 March 2024

2024-03-26T16:30:36Z

User at 16:30, 26 March 2024

2024-03-26T16:30:11Z

User at 14:52, 12 December 2022

2022-12-12T14:52:52Z

User: Created page with "'''Content Coming Soon'''"

2018-12-05T19:49:58Z

Created page with "'''Content Coming Soon'''"

New page

'''Content Coming Soon'''

@@ Line 51: / Line 51: @@
 *[[Project Management]]: Covering the discipline of initiating, planning, executing, controlling, and closing the work of a team to achieve specific goals and meet specific success criteria. Solution architecture is often delivered within the constraints of project management.
 *Cloud Computing Architecture: Explaining the components and subcomponents required for cloud computing, which includes a front-end platform, back-end platforms, cloud-based delivery, and a network. Cloud solutions are increasingly important in modern solution architecture.
-*Data Architecture: Discussing the structure of an organization's logical and physical data assets and data management resources. It's a critical aspect of solution architecture when the solution involves managing data at scale.
+*[[Data Architecture]]: Discussing the structure of an organization's logical and physical data assets and data management resources. It's a critical aspect of solution architecture when the solution involves managing data at scale.
-*Microservices Architecture: Covering an architectural style that structures an application as a collection of loosely coupled services, which is a common approach in modern solution architecture for building scalable and flexible systems.
+*[[Microservices Architecture]]: Covering an architectural style that structures an application as a collection of loosely coupled services, which is a common approach in modern solution architecture for building scalable and flexible systems.
 *API Design: Explaining the process of developing application programming interfaces (APIs) that expose backend data and application functionality for use in new applications and systems. APIs are often key components of solution architectures, enabling integration and communication between different systems.
 *Cybersecurity Architecture: Discussing the framework and processes designed to ensure the security of solution architectures. This includes considerations for data encryption, secure software development practices, and compliance with security standards and regulations.

@@ Line 1: / Line 1: @@
 == What is Solution Architecture? ==
-Solution Architecture refers to designing, describing, and managing the solution engineering in relation to specific business problems. A solution architect is responsible for bridging the gap between business problems and technology solutions, finding the best tech solution to solve the existing business problems. This involves understanding the business requirements and processes and then designing a comprehensive solution that leverages technology to meet those needs effectively and efficiently.
+'''Solution Architecture''' refers to designing, describing, and managing the solution engineering in relation to specific business problems. A solution architect is responsible for bridging the gap between business problems and technology solutions, finding the best tech solution to solve the existing business problems. This involves understanding the business requirements and processes and then designing a comprehensive solution that leverages technology to meet those needs effectively and efficiently.
 == Key Components of Solution Architecture ==
-*Business Requirements: Understanding the business needs, challenges, and objectives that the solution aims to address.
+*[[Business Requirements]]: Understanding the business needs, challenges, and objectives that the solution aims to address.
 *[[Systems Architecture]]: The high-level structure of the software systems involved in the solution, including their interactions and dependencies.
 *Technology Stack: Choosing the appropriate technologies, platforms, and frameworks to build the solution, considering factors like scalability, performance, and maintainability.

@@ Line 1: / Line 1: @@
-A '''Solution Architecture''' describes the fundamental decisions in the design of a specific solution, covering business- as well as IT-aspects. Note that the system as a whole may be composed of multiple other (software) systems. This form of architecture is what TOGAF calls a “capability architecture”, and is close to what is also called “software architecture” (Shaw and Garlan 1996; Kruchten 1998) in the domain of application development. It strongly relies on the instructive role of architecture. Given its strong design bias, there is some discussion about whether solution architecture should be considered architecture at all, or just (high-level) design.
+== What is Solution Architecture? ==
-===See Also===
+== Key Components of Solution Architecture ==
-[[Enterprise Architecture]]<br />
-[[Reference Architecture]]
+*Business Requirements: Understanding the business needs, challenges, and objectives that the solution aims to address.

← Older revision		Revision as of 14:52, 12 December 2022
Line 1:		Line 1:
−	'''~~Content Coming Soon~~'''	+	A '''Solution Architecture''' describes the fundamental decisions in the design of a specific solution, covering business- as well as IT-aspects. Note that the system as a whole may be composed of multiple other (software) systems. This form of architecture is what TOGAF calls a “capability architecture”, and is close to what is also called “software architecture” (Shaw and Garlan 1996; Kruchten 1998) in the domain of application development. It strongly relies on the instructive role of architecture. Given its strong design bias, there is some discussion about whether solution architecture should be considered architecture at all, or just (high-level) design.
		+
		+
		+	===See Also===
		+	[[Enterprise Architecture]]<br />
		+	[[Reference Architecture]]