Create your own awesome maps

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account?
Log In

Archimate® 2.1 study guide mind map by Mind Map: Archimate® 2.1 study guide mind
5.0 stars - 36 reviews range from 0 to 5

Archimate® 2.1 study guide mind map

ArchiMate®, DirecNet®, Jericho Forum®, Making Standards Work®, OpenPegasus®, The Open Group®, TOGAF®, and UNIX® are registered trademarks and Boundaryless Information Flow™, Dependability Through Assuredness™, FACE™, Open Platform 3.0™, and The Open Group Certification Mark™ are trademarks of The Open Group. Trademarks are properties of the holders, who are not affiliated with mind map author.

Motivation extension

The ArchiMate® Motivation extension can be used to model the principles, drivers, goals, and requirements of the architecture.

Motivational Concepts

Stakeholder, A stakeholder is defined as the role of an individual, team, or organization (or classes thereof) that represents their interests in, or concerns relative to, the outcome of the architecture.

Driver, A driver is defined as something that creates, motivates, and fuels the change in an organization.

Assessment, An assessment is defined as the outcome of some analysis of some driver.

Goal, A goal is defined as an end state that a stakeholder intends to achieve.

Requirement, A requirement is defined as a statement of need that must be realized by a system.

Constraint, A constraint is defined as a restriction on the way in which a system is realized.

Principle, A principle is defined as a normative property of all systems in a given context, or the way in which they are realized.

Motivation Extension Relationships





Motivation Extension Viewpoints

Stakeholder Viewpoint

Goal Realization Viewpoint

Goal Contribution Viewpoint

Principles Viewpoint

Requirements Realization Viewpoint

Motivation Viewpoint

Elements Relationships

Relationships can be classified as either:

Structural, Which model the structural coherence of concepts of the same or different types., Derived Relationships

Dynamic, Which are used to model (temporal) dependencies between behavioral concepts.

Other, Which do not fall into one of the two above categories.

Structural Relationships

Association, Association models a relationship between objects that is not covered by another, more specific relationship., weight, 1, weakest structural relationship

Access, The access relationship models the access of behavioral concepts to business or data objects., weight, 2

Used By, The used by relationship models the use of services by processes, functions, or interactions and the access to interfaces by roles, components, or collaborations., weight, 3

Realization, The realization relationship links a logical entity with a more concrete entity that realizes it., weight, 4

Assignment, The assignment relationship links units of behavior with active elements (e.g., roles, components) that perform them, or roles with actors that fulfill them., weight, 5

Aggregation, The aggregation relationship indicates that an object groups a number of other objects., weight, 6

Composition, The composition relationship indicates that an object is composed of one or more other objects., weight, 7, strongest structural relationship

Dynamic Relationships

Flow, The flow relationship describes the exchange or transfer of, for example, information or value between processes, function, interactions, and events.

Triggering, The triggering relationship describes the temporal or causal relationships between processes, functions, interactions, and events.

Other Relationships

Grouping, The grouping relationship indicates that objects, of the same type or different types, belong together based on some common characteristic.

Junction, A junction is used to connect relationships of the same type.

Specialization, The specialization relationship indicates that an object is a specialization of another object.

Implementation and Migration extension

The ArchiMate® Implementation and Migration extension is used to stage the work packages that are needed to implement the architecture.

Implementation and Migration Concepts

Work Package




Implementation and Migration Relationships

The Implementation and Migration extension re-uses the standard ArchiMate relationships.

Implementation and Migration Extension Viewpoints

Project Viewpoint

Migration Viewpoint

Implementation and Migration Viewpoint

ArchiMate® 2.1 Specification

consists of:

ArchiMate® Core (the core language)

Motivation extension

Implementation and Migration extension

Layering and Elements

The ArchiMate® language defines 3 main layers:

Business Layer, What is it?, Offers products and services to external customers, which are realized in the organization by business processes performed by business actors., Active Structure Concepts (formerly Structural Concepts), Business actor, What is it?, A business actor is defined as an organizational entity that is capable of performing behavior., Business role, What is it?, A business role is defined as the responsibility for performing specific behavior, to which an actor can be assigned., Business collaboration, What is it?, Business collaboration is defined as an aggregate of two or more business roles that work together to perform collective behavior., Business interface, What is it?, A business interface is defined as a point of access where a business service is made available to the environment., Location, What is it?, A location is defined as a conceptual point or extent in space., Behavioral Concepts, Business process, What is it?, A business process is defined as a behavior element that groups behavior based on an ordering of activities. It is intended to produce a defined set of products or business services., Business function, What is it?, A business function is defined as a behavior element that groups behavior based on a chosen set of criteria (typically required business resources and/or competences)., Business interaction, What is it?, A business interaction is defined as a behavior element that describes the behavior of a business collaboration., Business event, What is it?, A business event is defined as something that happens (internally or externally) and influences behavior., Business service, What is it?, A business service is defined as a service that fulfills a business need for a customer (internal or external to the organization)., Passive Structure Concepts (formerly Informational Concepts), Business object, What is it?, A business object is defined as a passive element that has relevance from a business perspective., Representation, What is it?, A representation is defined as a perceptible form of the information carried by a business object., Meaning, What is it?, Meaning is defined as the knowledge or expertise present in a business object or its representation, given a particular context., Value, What is it?, Value is defined as the relative worth, utility, or importance of a business service or product., Product, What is it?, A product is defined as a coherent collection of services, accompanied by a contract/set of agreements, which is offered as a whole to (internal or external) customers., Contract, What is it?, A contract is defined as a formal or informal specification of an agreement that specifies the rights and obligations associated with a product.

Application Layer, What is it?, Supports the business layer with application services which are realized by (software) applications., Active Structure Concepts (formerly Structural Concepts), Application component, Application collaboration, Application interface, Data object, Behavioral Concepts, Application function, Application interaction, Application service

Technology Layer, What is it?, Offers infrastructure services (e.g., processing, storage, and communication services) needed to run applications, realized by computer and communication hardware and system software., Active Structure Concepts (formerly Structural Concepts), Node, Device, System software, Infrastructure interface, Network, Communication path, Behavioral Concepts, Infrastructure function, Infrastructure service, Passive Structure Concepts (formerly Informational Concepts), Artifact

Elements (aka. Concepts)

Each layer has dedicated set of Elements called Concepts

ArchiMate® Core language consists of 3 types of elements (aka. Aspects):, Active Structure Concepts (formerly Structural Concepts), see Active Structure Concepts (formerly Structural Concepts), Behavior elements, see Behavioral Concepts, Passive Structure Concepts (formerly Informational Concepts), see Passive Structure Concepts

Elements can interact and collaborate.

Elements have relationships of different types.

ArchiMate® Framework

The aspects (passive structure, behavior, and active structure) and layers (business, application, and technology) can be organized as a framework of 9 “cells”,

Architecture Viewpoints


A “view” is what you see


A “viewpoint” is where you are looking from.

Introductory Viewpoint

Organization Viewpoint

Actor Co-operation Viewpoint

Business Function Viewpoint

Business Process Viewpoint

Business Process Co-operation Viewpoint

Product Viewpoint

Application Behavior Viewpoint

Application Co-operation Viewpoint

Application Structure Viewpoint

Application Usage Viewpoint

Infrastructure Viewpoint

Infrastructure Usage Viewpoint

Implementation and Deployment Viewpoint

Information Structure Viewpoint

Service Realization Viewpoint

Layered Viewpoint

Landscape Map Viewpoint

Viewpoint Classification

by purpose, 3 classifications, Designing, Deciding, Informing

by content, 3 classifications, Details, Coherence, Overview


End user


Upper-level management

Operational manager

Project manager



2 types of profiles:

Pre-defined profiles

User-defined profiles


Performed by a single structure element.

Collective behavior (interaction) that is performed by a collaboration of multiple structure elements.


A collaboration is defined as a (temporary) grouping (or aggregation) of two or more structure elements, working together to perform some collective behavior.


An interaction is defined as a unit of behavior performed by a collaboration of two or more structure elements.

This freeware, non-commercial mind map (aligned with the newest version of Archimate®) was created for promotion the Archimate® standard and as a learning tool for candidates wanting to gain Archimate® qualifications. (please share and give feedback - your feedback and comments are my main motivation for further elaboration. THX!)

Questions / issues / errors? What do you think about my work? Your comments are highly appreciated. Please don't hesitate to contact me for :-) Mirosław Dąbrowski, Poland/Warsaw.


Map is under development, current state is an early ALPHA

Recommended Reading

Mastering ArchiMate Edition II

Enterprise Architecture / Archimate modelling software

ARIS Archimate Modeller

ARIS IT Architect & Designer




BOC Management Office

BiZZdesign Architect

Enterprise Architect

Essential Project



System Architecture Management Utility (SAMU)

Troux Architect

Visual Paradigm