The Layered viewpoint pictures several layers and aspects of an enterprise architecture in one diagram. There are two categories of layers, namely dedicated layers and service layers. The layers are the result of the use of the “grouping” relation for a natural partitioning of the entire set of objects and relations that belong to a model. The infrastructure, the application, the process, and the actors/roles layers belong to the first category. The structural principle behind a fully layered viewpoint is that each dedicated layer exposes, by means of the “realization” relation a layer of services, which are further on “used by” the next dedicated layer. Thus, we can easily separate the internal structure and organization of a dedicated layer from its externally observable behavior expressed as the service layer that the dedicated layer realizes. The order, number, or nature of these layers are not fixed, but in general a (more or less) complete and natural layering of an ArchiMate model will contain the succession of layers depicted in the example given below. However, this example is by no means intended to be prescriptive. The main goal of the Layered viewpoint is to provide overview in one diagram. Furthermore, this viewpoint can be used as support for impact of change analysis and performance analysis or for extending the service portfolio.
Stakeholders | Enterprise, process, application, infrastructure, and domain architects |
Concerns | Consistency, reduction of complexity, impact of change, flexibility |
Purpose | Designing, deciding, informing |
Abstraction Level | Overview |
Layer | Business layer, Application layer, Technology layer |
Aspects | Information, Behaviour, Structure |
Concepts and Relations
All concepts and relations.