Solution architecture: Difference between revisions

Revision as of 20:24, 25 November 2023

Revision as of 20:24, 25 November 2023

Line 7:

* [[Gartner]] (2013): ''A solution architecture (SA) is an architectural description of a specific solution. SAs combine guidance from different enterprise architecture viewpoints (business, information and technical), as well as from the enterprise solution architecture (ESA).''<ref>Gartner, "[http://www.gartner.com/it-glossary/solution-architecture IT Glossary]," at ''gatner.com,'' 2013. Accessed 8 March 2015.</ref>

* [[Danny Greefhorst|Greefhorst]] and [[Erik Proper|Proper]] (2013): ''An architecture of a solution, where a solution is a system that offers a coherent set of functionalities to its environment. As such, it concerns those properties of a solution that are necessary and sufficient to meet its essential requirements''<ref>[[Danny Greefhorst]] & [[Erik Proper]], ''Architecture Principles: The Cornerstones of Enterprise Architecture,'' 2011. p. 25</ref>

A typical property of Solutionsolution Architecturearchitecture, in contrast to other types of Enterprise Architecture, is that it often seeks to define a solution within the context of a project or initiative.<ref>{{Cite web|title=What is Solution Architecture? {{!}} Orbus Software|url=https://www.orbussoftware.com/solution-architecture/what-is-solution-architecture/|access-date=2020-11-24|website=www.orbussoftware.com}}</ref> This close association to actual projects and initiatives means that solution architecture is the means to execute or realise a technology strategy.

==Coverage==

According to [[Forrester Research]], Solutionsolution Architecturearchitecture is one of the key components by which [[Enterprise architecture|Enterprise Architecture]] delivers value to the organization. It entails artifacts such as a solution business context, a solution vision and requirements, solution options (e.g. through [[Request for information|RFI]]s, [[Request for proposal|RFP]]s or prototype development) and an agreed optimal solution with build and implementation plans ("road-map").<ref>Forrester Research, Inc., (2012), Solution Architecture Toolkit: Overview</ref>

Since The Open Group does not recognize a unique Solution Architect role, a relevant link for these mentioned artifacts can be to the [[Business analyst|Business]] and [[Systems analyst|Systems Analyst]] roles. It is also worth noting that The Open Group's definition of Solutionsolution Architecturearchitecture is broader than Forrester's (see aforementioned definition).

According to a 2013 paper published by the Federation of Enterprise Architecture Professional Organizations, solution architecture includes [[business architecture]], [[Data architecture|information architecture]], [[application architecture]], and [[technology architecture]] operating at a tactical level and focusing on the scope and span of a selected business problem. In contrast, enterprise architecture, which also includes the aforementioned four types of architecture, operates at the strategic level and its scope and span is the enterprise rather than a specific business problem.<ref>FEAPO, "A Common Perspective on Enterprise Architecture" in: Architecture and Governance Magazine, 2013(11).</ref><ref>Mistrík Ivan, Antony Tang, Rami Bahsoon, Judith A. Stafford. (2013), Aligning Enterprise, System, and Software Architectures. Business Science Reference.</ref>