Architecture domain

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.

Business, data, application and technology architectures are recognized as the core domains in the most of proposed concepts concerned with the definition of enterprise architecture.

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

Many EA frameworks combine data and application domains into a single layer, sitting below the business (usually a human activity system; that is a notational system expressing a purposeful human activity in a theoretical way using intellectual constructs and not descriptions of actual real-world activity[5]) and above the technology (the platform IT infrastructure).

Structure of the Federal Enterprise Architecture Framework (FEAF), presented in 2001, which determined four architectural domains. [ 1 ]
Layers of the EA
Enterprise architecture reference architecture with sub domains