Architecture domain

Structure of the "Federal Enterprise Architecture Framework" (FEAF), presented in 2001, which determined four architectural domains.[1]

An architecture domain in enterprise architecture is a broad view of an enterprise or system. It is a partial representation of a whole system that addresses several concerns of several stakeholders. It is a description that hides other views or facets of the system described.

Overview

Since Stephen Spewak's book called enterprise architecture planning (EAP) in 1993, and perhaps before then, it has been normal to recognise four types of architecture domain:

Note that the applications architecture is about the application portfolio, not the internal architecture of a single application - which is often called the application architecture.

Many EA frameworks combine data and application domains into a single layer, sitting below the business (usually a human activity system) and above the technology (the platform IT infrastructure). There are many variations on this theme.

Typical architecture domains

Typical architecture domains are listed below, and defined drawing on the definitions found in The British Computer Society's "Reference Model for Enterprise and Solution Architecture".

See also

References

  1. Chief Information Officer Council (2001) A Practical Guide to Federal Enterprise Architecture. Feb 2001.
This article is issued from Wikipedia - version of the Thursday, March 31, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.