Actions

Difference between revisions of "Solution Architecture"

(Created page with "'''Content Coming Soon'''")
 
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]]

Revision as of 14:52, 12 December 2022

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
Reference Architecture