Reference architecture

Source: Wikipedia, the free encyclopedia.

A reference architecture in the field of software architecture or enterprise architecture provides a template solution for an architecture for a particular domain. It also provides a common vocabulary with which to discuss implementations, often with the aim to stress commonality. A software reference architecture is a software architecture[1] where the structures and respective elements and relations provide templates for concrete architectures in a particular domain or in a family of software systems.

An implementation of a reference architecture is called a

application platform
.

A reference architecture often consists of a list of

interfaces (or APIs
) and interactions with each other and with functions located outside of the scope of the reference architecture.

Reference architectures can be defined at different levels of abstraction. A highly abstract one might show different pieces of equipment on a

methods
) within a computer program defined to perform a very specific task.

A reference architecture provides a template, often based on the generalization of a set of solutions. These solutions may have been generalized and structured for the depiction of one or more architecture structures based on the harvesting of a set of patterns that have been observed in a number of successful implementations. Further it shows how to compose these parts together into a solution. Reference Architectures will be instantiated for a particular domain or for specific projects.

Adopting a reference architecture within an organization accelerates delivery through the re-use of an effective solution and provides a basis for governance to ensure the consistency and applicability of technology use within an organization. In the field of software architecture, many empirical studies have shown the following common benefits and drawbacks from adopting a software reference architecture within organizations: (a) improvement of the

developers due to the need of learning its features.[2]

Examples

See also

References

  1. ^ Clements, Paul; Felix Bachmann; .
  2. .
  3. ^ The IBM Insurance Application Architecture
  4. ^ Healthcare Enterprise Reference Architecture (HERA)