Solution architecture

From Wikipedia, the free encyclopedia
  (Redirected from Solution Architecture)
Jump to: navigation, search

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 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.

An instance of a solution architecture will typically be an abstraction of an end-to-end subsystem,[3] consisting of application software supported by middleware which together provide:

  • An IT implementation of a specific business task or process necessary to support a business function with appropriate non-functional requirements (e.g. integrity, performance, security, recoverability, etc.)
  • A synchronization mechanism between the subsystem consumers/providers and the associated business task or process

e.g. an end-to-end eCommerce subsystem which allows customers to place orders for goods and services or an end-to-end Supply Replenishment subsystem which enables an enterprise to order new stock from its suppliers

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.

[edit] See also

[edit] References

  1. ^ TOGAF (The Open Group Architecture Framework)
  2. ^ “Patterns of enterprise application architecture” by Martin Fowler.
  3. ^ End-to-end subsystem defined within Patterns for e-business at http://www.ibm.com/developerworks/patterns/library/definitions.html

[edit] External links

Personal tools
Namespaces

Variants
Actions
Navigation
Interaction
Toolbox
Print/export