Restructure the explanations for the Full Framework and Core Framework

In the very beginning of the ArchiMate language onle what is now called Core Framework existed. With time the language evolved to the comprehensive Full Framework, which added many other layers and one aspect to the language, turning the Core Framework on a kind of subset of the whole language. However, the description of the language structure in Chapter 3 still has a prominent focus on the Core Framework, as if the Full Framework was still just some extensions to the core. The proposed change would bring the Full Framework to the front stage, correctly placing the Core Framework on a secondary plane.

3.3 The ArchiMate Full Framework

The ArchiMate Full Framework defines a structure to classify the elements that comprise the ArchiMate language. The Full Framework is organized into layers based on various domains in which the Enterprise Architecture may be segmented, and aspects related to the concerns of different stakeholders. The elements in the ArchiMate language are positioned in this structure, as a means to provide guidance about their nature and usage.

The five layers and four aspects that constitute the ArchiMate Full Framework (refer to figure 3) are:

Full Framework Layers:

1. The elements in the Strategy Layer model the strategic direction and choices of the enterprise (refer to Chapter 7 for a detailed description of these elements)
2. The elements in the Business Layer represent business services offered to customers, which are realized in the organization by business processes performed by business actors, acting upon business concepts (objects)
3. The elements in the Application Layer represent application services that support the business, the applications that realize them through automated processes, and the data needed for this
4. The elements in the Technology Layer represent technology services such as processing, storage, and communication services, needed to run the applications, and the computer and communication hardware and system software that realize those services. Physical elements are included for modeling physical equipment, materials, and distribution networks
5. The elements in the Implementation and Migration Layer support the implementation and migration of architectures. This includes modeling implementation programs and projects to support program, portfolio, and project management, and the deliverables they produce. It also includes support for migration planning and roadmapping

Full Framework Aspects

1. The elements in the Active Structure Aspect represent the structural elements of the organization, such as business actors, application components, and devices, that display actual behavior; i.e., the “subjects” of activities
2. The elements in the Behavior Aspect represent the behavior (processes, functions, events, and services) performed by the active structural elements. Active structural elements are assigned to behavioral elements to show who or what displays the behavior
3. The elements in the Passive Structure Aspect represent the objects on which behavior is performed; these are usually information objects in the Business Layer, data objects in the Application Layer, and physical objects in the Technology Layer
4. The elements in the Motivation Aspect encompass the factors that drive the design and operation of the enterprise. They address the way the Enterprise Architecture is aligned to its context and stakeholders intentions and correspond to the “Why” column of the Zachman framework [5].

Note that the ArchiMate language does not require the modeler to use any particular layout, such as the structure of this framework; it is merely a categorization of the language elements.

Figure 3: ArchiMate Full Framework

The ArchiMate language does not define a specific layer for information, in contrast to the TOGAF Framework. Elements from the passive structure aspect such as business objects, data objects, and artifacts, are used to represent information entities. Information modeling is supported across the different ArchiMate core layers (see Chapter 3.4).

It is important to understand that the classification of elements based on aspects and layers is only a global one. Real-life architecture elements need not strictly be confined to one aspect or layer because elements that link the different aspects and layers play a central role in a coherent architectural description. For example, running somewhat ahead of the later conceptual discussions, business roles serve as intermediary elements between “purely behavioral” elements and “purely structural” elements, and it may depend on the context whether a certain piece of software is considered to be part of the Application Layer or the Technology Layer.

3.4 The ArchiMate Core Language

The ArchiMate Core Language defines a structure of generic elements, which can be further specialized in different layers. Three layers (as defined in Section 3.3) are contained within the ArchiMate Core Language as follows: • The Business Layer • The Application Layer • The Technology Layer

The general structure of models within these layers is similar. The same types of elements and relationships are used, although their exact nature and granularity differ. In the next chapter, the structure of the generic metamodel for the ArchiMate Core Language is presented. In Chapter 8, Chapter 9, and Chapter 10 these elements are specialized to obtain elements specific to a particular layer.

In alignment with service-orientation, the most important relationship between core layers is the “serving” relationship, which show how the elements in one layer are served by the services of other layers. (Note, however, that services need not only to serve elements in another layer, but can also serve elements in the same layer.) A second type of link is formed by the realization relationship: elements in lower layers may realize comparable elements in higher layers; e.g., a “data object” (Application Layer) may realize a “business object” (Business Layer); or an “artifact” (Technology Layer) may realize either a “data object” or an “application component” (Application Layer).

3.5 The ArchiMate Core Framework The ArchiMate Core Framework is a framework of nine cells used to classify elements of the ArchiMate Core Language. It is made up of three aspects and three layers, as illustrated in Figure 2 below.

Figure 2: ArchiMate Core Framework

The structure of the core framework allows for modeling the enterprise from different viewpoints, where the position of an element in the cells highlights the stakeholder’s concerns. A stakeholder typically has concerns that cover multiple cells.