The Implementation and Migration Extension adds concepts to support the implementation and migration of architectures in Phase E (Opportunities and Solutions), Phase F (Migration Planning), and Phase G (Implementation Governance) of the TOGAF ADM. This extension includes concepts for modeling implementation programs and projects to support program, portfolio, and projectRead More →
The Technology Layer describes system software applications and infrastructure. Whenever applicable, the ArchiMate language has drawn analogies with the Business and Application Layers. Technology Layer Example In this example, structural, behavioral, and informational concepts of the Technology Layer are illustrated. The structural technology node “ (1)Mainframe” is shown to containRead More →
Motivation Extension Example In this example, there are two key stakeholders, the “ (1) CEO” and the “ (2) CFO”. The “ (1) CEO” has “ (3) Customer satisfaction” as a driver, with an associated goal of “ (5) Improve portfolio management”. The CFO meanwhile has “ (4) Costs” asRead More →
ArchiSurance – Business Layer Example In this example, (1) Client and (2) ArchiSurance are business actors, the active entities that perform behavior such as business processes or functions. A business role is assigned to each actor. (1) Client has the role of (3)Insurant and makes use of the Damage insuranceRead More →
ArchiSurance – Application Layer Example In this example below, both structural and behavioral concepts of the Application Layer are illustrated. “(1) Web front end” is the application interface that provides access to the application service called “(2) Policy creation service”. It is a composite part of the Home & Away policyRead More →
Active Structure Concept Notation Application component A modular, deployable, and replaceable part of a software system that encapsulates its behavior and data and exposes these through a set of interfaces. Application collaboration An aggregate of two or more application components that work together to perform collective behavior. ApplicationRead More →
The metamodel gives an overview of the application layer concepts and their relationships. Many of the concepts have been inspired by the UML 2.0 standard, as this is the dominant language and the de facto standard for describing software applications. As I mentioned before, ArchiMate core framework has 3 layers x 3 aspects:Read More →
ArchiMate Notation ArchiMate 3 – Technology Layer Notations Name Representation Definition * Node A computational or physical resource that hosts, manipulates, or interacts with other computational or physical resources. Device A physical IT resource upon which system software and artifacts may be stored or deployed for execution. System Software SoftwareRead More →
Informational Concepts are passive entities which provide a way to link the operational side of an organization to its business goals and the products (through behavior entities) that it offers to its customers. In the Metamodel above, you can see that: The contract entity is a kind of business objectRead More →
A behavior element is defined as a unit of activity performed by one or more active structure elements. The active structure concepts are assigned to behavioral concepts, to show who or what performs the behavior as shown in the metamodel below: Internal vs External Behavioral Concepts While the internal business services offerRead More →