Solution architecture: Difference between revisions
wikification |
grammar |
||
| Line 6: | Line 6: | ||
The documentation is typically divided into a broad views, each known as an [[architecture domain]]. |
The documentation is typically divided into a broad views, each known as an [[architecture domain]]. |
||
Solution architecture is |
Solution architecture is related to [[enterprise architecture]].<ref>[[TOGAF]] (The Open Group Architecture Framework)</ref> The solution described may be all or part of what an enterprise architect's migration plan delivers. The solution might be unrelated to any such plan. Solution architecture often leads to [[software architecture]] work<ref>“Patterns of enterprise application architecture” by Martin Fowler.</ref> and [[technical architecture]] work, and often contains elements of those. |
||
A [[Solutions Architect]] is often but not always focused on [[technical architecture]] and the meeting of non-functional requirements, often in the context of deploying specific applications. |
A [[Solutions Architect]] is often but not always focused on [[technical architecture]] and the meeting of non-functional requirements, often in the context of deploying specific applications. |
||
Revision as of 19:39, 26 April 2009
Solution Architecture in enterprise architecture is a kind of architecture domain, that aims to address specific problems and requirements, usually through the design of specific information systems or applications.
Solution architecture is either:
- Documentation describing the structure and behaviour of a solution to a problem, or
- A process for describing a solution and the work to deliver it.
The documentation is typically divided into a broad views, each known as an architecture domain.
Solution architecture is related to enterprise architecture.[1] The solution described may be all or part of what an enterprise architect's migration plan delivers. The solution might be unrelated to any such plan. Solution architecture often leads to software architecture work[2] and technical architecture work, and often contains elements of those.
A Solutions Architect is often but not always focused on technical architecture and the meeting of non-functional requirements, often in the context of deploying specific applications.