The purpose of the motivation extension is to model the motivation behind the core elements in some enterprise architecture. Therefore, it should be possible to relate motivational elements to core elements as shown in Figure below: Meaning and value can be associated with any structure or behavior element. Relating Core ElementsRead More →
The metamodels and examples from show the different types of relationships that can be used: between two motivational elements between one motivational element and one core element. The Table below provides a description of these relationships: Intentional Relationships Notation Association Association models that some intention is related to a sourceRead More →
As mentioned in Part I, the metamodel of motivational is an extension in ArchiMate as shown in the Figure below that includes two kind of motivational concepts: 1) Source of Intentions 2) Motivation There are four motivation elements: 1) Goal, 2) Principle, 3) Requirement, and 4) Constraint Goal A goal is defined as an end state thatRead More →
As mentioned in Part I, the metamodel of motivational is an extension in ArchiMate as shown in the Figure below that includes two kind of motivational concepts: 1) Source of Intentions 2) Motivation Source of Intentions: 1) Stakeholder, 2) Driver and 3) Assessment Stakeholder A stakeholder is defined as the roleRead More →
Enterprise Architecture is about responding to change and clearly describe how the effects of the change affect the Enterprise Architecture. The source of intention, such as drivers or stakeholders can be either External – such as changing mobile and web technology of the competitors, or Internal, such as a strategicRead More →
Motivational concepts are used to model the motivations, or reasons, that underlie the design or change of some enterprise architecture. These motivations influence, guide, and constrain the design. The metamodel of motivational is an extension in ArchiMate as shown in the Figure below that includes two kind of motivational concepts: SourceRead More →
Behavior Concepts Behavior elements in the Technology Layer are similar to the behavior elements in the other layers. A distinction is made between the external behavior of nodes in terms of technology services, and the internal behavior of these nodes; i.e., technology functions that realize these services. Technology Function ConceptRead More →
Active Structure Element The main active structure element for the Technology Layer is the node. This element is used to model structural entities in this layer which as the following characteristics: It is used to model application servers, database servers, or client workstations. It is often a combination of aRead More →
Technology Layer The Technology Layer depicts 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 added for modeling physical equipment, materials, and distribution networks to this layer. Metamodel TheRead More →
Aspects and Layers in ArchiMate Core Framework The active structure aspect represents the structural concepts (the business actors, application components, and devices that display actual behavior; i.e., the “subjects” of activity). The behavior aspect represents the behavior (processes, functions, events, and services) performed by the actors. Behavioral concepts are assignedRead More →