๐Ÿ“
ArchiMate 3 โ€” Enterprise Architecture Modelling Language
The Open Group Standard ยท Version 3.2 ยท The visual language for TOGAF architectures
Interactive study manual covering all layers, aspects, 60+ elements, relationships, viewpoints, and TOGAF alignment.
6 Layers 3 Aspects 60+ Elements 10 Relationship Types 20+ Viewpoints 40 Flash Cards
ArchiMate is an open and independent enterprise architecture modelling language developed by The Open Group. It provides a uniform representation for diagrams that describe enterprise architectures โ€” enabling architects to describe, analyse, and visualise the relationships across business domains in an unambiguous way. ArchiMate is to TOGAF what UML is to software development.
6
Layers
3
Aspects
60+
Elements
10
Relationship Types
20+
Viewpoints
3.2
Current version
๐Ÿค” Why ArchiMate Exists
โŒ Without ArchiMate
โ†’ Each architect draws differently
โ†’ No shared notation across teams
โ†’ Business can't read IT diagrams
โ†’ Relationships hard to trace
โ†’ Models become stale and siloed
โœ… With ArchiMate
โ†’ Consistent notation across the org
โ†’ Business + IT speak same language
โ†’ Impact analysis across layers
โ†’ Traceability from strategy to tech
โ†’ Machine-readable models
๐Ÿ“ฆ The 3 Aspects โ€” Applied to Every Layer
๐Ÿข
Active Structure
Structural elements that perform behaviour โ€” actors, roles, components, nodes
Who / What does it
โšก
Behaviour
Dynamic elements that represent behaviour โ€” processes, functions, services, events
What it does
๐Ÿ“„
Passive Structure
Structural elements that are acted upon โ€” objects, data objects, artefacts
What it acts on
ArchiMate vs UML vs BPMN: UML models software systems. BPMN models business processes. ArchiMate models the whole enterprise โ€” spanning business, application, and technology layers with consistent notation and explicit relationship types. It is designed to show how layers interact, not to detail any single layer.
ArchiMate 3 has 6 layers arranged from strategy at the top to physical at the bottom. Each layer can be modelled across 3 aspects. The serving relationship is the key cross-layer connector โ€” lower layers serve upper layers.
Strategy
Active Structure
Resource
Resource Capability
Behaviour
Course of Action
Course of Action
Passive Structure
Value Stream
Value Stream
Motivation
Active Structure
Stakeholder
Stakeholder
Behaviour
Goals & Drivers
Goal Driver Assessment
Passive Structure
Requirements
Requirement Constraint Principle
Business
Active Structure
Business Actor Business Role Collaboration
Behaviour
Business Process Business Function Business Service Business Event
Passive Structure
Business Object Contract Product Representation
Application
Active Structure
Application Component Application Collaboration Application Interface
Behaviour
Application Process Application Function Application Service Application Event
Passive Structure
Data Object
Technology
Active Structure
Node Device System Software Technology Interface
Behaviour
Technology Process Technology Function Technology Service Technology Event
Passive Structure
Artefact
Physical
Active Structure
Equipment Facility Distribution Network
Behaviour
Physical Process Physical Function Physical Service Physical Event
Passive Structure
Material
โฌ‡๏ธ Serving direction: Lower layers serve upper layers. Technology services serve Application components. Application services serve Business processes. Business services serve external customers. This serving chain is the core architectural principle of ArchiMate.
ArchiMate defines 60+ elements across 6 layers and 3 aspects. The core elements are the most frequently used in practice. Filter by layer or aspect to browse them.
Strategy
Active Structure
Resource
An asset owned or controlled by the organisation that is used to perform activities or provide services.
e.g. IT budget, skilled team, data centre
Strategy
Active Structure
Capability
An ability the organisation, person, or system possesses โ€” enabling a desired outcome.
e.g. Cloud migration capability, CRM capability
Strategy
Behaviour
Course of Action
An approach or plan for configuring capabilities and resources to achieve a goal.
e.g. Cloud-first strategy, digital transformation plan
Strategy
Passive Structure
Value Stream
A sequence of activities that create an overall result for a customer, stakeholder, or end user.
e.g. Order-to-cash, loan origination
Motivation
Active Structure
Stakeholder
An individual, team, or organisation that has interests in or concerns relative to the outcome of the architecture.
e.g. CIO, regulator, end user
Motivation
Behaviour
Driver
An external or internal condition that motivates the organisation to change.
e.g. Regulatory change, competitive pressure
Motivation
Behaviour
Goal
A high-level statement of intent, direction, or desired end state for the organisation.
e.g. Reduce IT costs by 20%, improve customer NPS
Motivation
Passive Structure
Requirement
A statement of need that must be met by the architecture.
e.g. System must support 10,000 concurrent users
Motivation
Passive Structure
Principle
A qualitative statement of intent that should be met by the architecture โ€” normative guidance.
e.g. Cloud-first, data is a shared asset
Business
Active Structure
Business Actor
An organisational entity capable of performing behaviour โ€” a person, team, or department.
e.g. Sales department, customer, supplier
Business
Active Structure
Business Role
The responsibility for performing specific behaviour assigned to a Business Actor.
e.g. Account manager, approver, reviewer
Business
Behaviour
Business Process
A sequence of business behaviours that achieves a specific result for the organisation or customer.
e.g. Order fulfilment, employee onboarding
Business
Behaviour
Business Function
A collection of business behaviour based on a specific set of criteria โ€” typically organisational capabilities.
e.g. Finance function, HR function
Business
Behaviour
Business Service
A service that fulfils a business need for an internal or external customer.
e.g. Order placement service, payroll service
Business
Passive Structure
Business Object
A concept used within the business domain โ€” a passive element that business behaviour acts on.
e.g. Invoice, contract, customer record
Business
Passive Structure
Product
A coherent collection of services and/or passive structure elements offered to external customers.
e.g. Banking product, insurance policy
Application
Active Structure
Application Component
An encapsulation of application functionality aligned to implementation structure โ€” a deployable software unit.
e.g. CRM system, payment gateway, API service
Application
Active Structure
Application Interface
A point of access where application services are made available to users or other components.
e.g. REST API, user interface, messaging endpoint
Application
Behaviour
Application Service
A service that exposes automated behaviour to the environment โ€” what an application does for its users.
e.g. Authentication service, search service
Application
Behaviour
Application Function
Automated behaviour that can be performed by an application component.
e.g. Calculate tax, generate report
Application
Passive Structure
Data Object
Data structured for automated processing โ€” the passive information element in the application layer.
e.g. Customer record, transaction, message
Technology
Active Structure
Node
A computational or physical resource that hosts, manipulates, or interacts with other resources.
e.g. Server, cloud instance, virtual machine
Technology
Active Structure
Device
A physical IT resource on which system software and other software can run.
e.g. Physical server, laptop, network switch
Technology
Active Structure
System Software
Software that provides or contributes to the environment for storing, executing, and using software.
e.g. Operating system, database engine, middleware
Technology
Behaviour
Technology Service
A service that exposes technology functionality โ€” what infrastructure does for applications.
e.g. Compute service, storage service, DNS
Technology
Passive Structure
Artefact
A piece of data used or produced in a software development process โ€” a deployable or storable item.
e.g. Docker image, JAR file, database schema
Physical
Active Structure
Equipment
One or more physical machines, tools, or instruments that can create, use, store, move, or transform materials.
e.g. Datacentre UPS, cooling system, IoT sensor
Physical
Active Structure
Facility
A physical structure or environment โ€” a building, data centre, or site.
e.g. Datacentre building, office site
Physical
Passive Structure
Material
Tangible physical matter or physical elements โ€” used in physical processes.
e.g. Cables, hardware components
ArchiMate defines 10 relationship types that connect elements within and across layers. Understanding the precise meaning of each relationship is essential for building accurate and useful architecture models.
Structural
โ€”โ€”โ–ถAssociation
An unspecified relationship or one not represented by another relationship type. The most basic connection between elements.
Actor โ€” Business Object (general link)
Structural
โ—‡โ€”โ€”Aggregation
An element consists of a number of other concepts. The whole contains the parts but parts can exist independently.
Business Process aggregates Business Functions
Structural
โ—†โ€”โ€”Composition
An element is composed of other concepts โ€” strong containment. Parts cannot exist without the whole.
Application Component is composed of sub-components
Structural
โ€”โ€”โ–ทRealisation
An entity plays a critical role in the creation or achievement of another entity. Lower layers realise upper layers.
Application Service realises Business Service
Dependency
..โ–ทServing
An element provides functionality to another element โ€” the core cross-layer relationship. Lower serves upper.
Technology Service serves Application Component
Dependency
..โ–ถAccess
A behaviour element accesses (reads, writes, or read/writes) a passive structure element.
Application Process accesses Data Object
Dependency
..โ—‡Influence
An element affects โ€” but not fully determines โ€” the realisation of another element.
Driver influences Goal
Dependency
..โ–ทAssignment
Assigns a behaviour element to an active structural element โ€” who does what.
Business Role is assigned to Business Process
Dynamic
โ€”โ†’Triggering
A temporal or causal dependency between elements โ€” one triggers another.
Business Event triggers Business Process
Dynamic
โ•โ†’Flow
Transfer of information, data, or material from one element to another.
Process A flows to Process B (data handoff)
Other
โ–ณโ€”โ€”Specialisation
An element is a specialisation of another element of the same type โ€” inheritance.
Mobile App specialises Application Component
โšก Relationship strength: Composition > Aggregation > Realisation > Serving > Assignment. In the ArchiMate specification, the relationship with the strongest semantic meaning takes precedence when multiple could apply.
Viewpoints define which elements and relationships are shown for a specific audience and purpose. ArchiMate provides 20+ predefined viewpoints โ€” architects select the right viewpoint to communicate with each stakeholder group.
Strategy
Strategy Viewpoint
Purpose: Inform executive decision makers
Shows capabilities, resources, and courses of action โ€” how the organisation plans to create value.
StrategyMotivation
Strategy
Capability Map Viewpoint
Purpose: Capability planning and gap analysis
Presents a structured overview of capabilities, typically in a heat-map format showing current and target state.
Strategy
Motivation
Stakeholder Viewpoint
Purpose: Understand and align stakeholders
Shows stakeholders, their drivers, concerns, goals, and requirements โ€” essential for architecture engagement.
Motivation
Motivation
Goal Realisation Viewpoint
Purpose: Traceability from goals to requirements
Shows how goals are refined into sub-goals and requirements that can be implemented by the architecture.
Motivation
Business
Business Process Viewpoint
Purpose: Show business operations
Shows the structure and composition of business processes and their relationships to roles, objects, and services.
Business
Business
Organisation Viewpoint
Purpose: Show organisational structure
Shows the internal structure of the organisation โ€” actors, roles, and collaboration relationships.
Business
Business
Product Viewpoint
Purpose: Define product/service offering
Shows the product and its composition in terms of services, contracts, and other elements.
BusinessApplication
Application
Application Usage Viewpoint
Purpose: Show how apps support business
Shows how application components are used by business processes and roles โ€” the key business-IT alignment view.
BusinessApplication
Application
Application Co-operation Viewpoint
Purpose: Show application integration
Shows how application components interact โ€” interfaces, data flows, and application collaboration.
Application
Technology
Technology Viewpoint
Purpose: Show infrastructure
Shows the structure and composition of the technology layer โ€” nodes, devices, system software, and their relationships.
Technology
Technology
Technology Usage Viewpoint
Purpose: Show how tech supports apps
Shows how applications are supported by the technology infrastructure โ€” the infrastructure-application alignment view.
ApplicationTechnology
Cross-Layer
Layered Viewpoint
Purpose: Full-stack architecture communication
Shows multiple layers simultaneously โ€” the most complete and most complex viewpoint. Used for impact analysis.
BusinessApplicationTechnology
Cross-Layer
Migration Viewpoint
Purpose: Show transition / change roadmap
Shows the transition from baseline to target architecture โ€” gaps, migration projects, and interim states.
BusinessApplicationTechnology
ArchiMate 3 is designed to work hand-in-hand with TOGAF. ArchiMate provides the notation and modelling language; TOGAF provides the process and governance. Together they form the industry-standard enterprise architecture approach.
๐Ÿ”„ TOGAF ADM โ†’ ArchiMate Layer Mapping
Phase A โ€” Architecture Vision
Motivation + Strategy layers
Stakeholders, drivers, goals, principles, capabilities, and courses of action. ArchiMate motivation elements support the architecture vision statement.
MotivationStrategy
Phase B โ€” Business Architecture
Business layer
Business actors, roles, processes, functions, services, and objects. Business Process and Organisation viewpoints are key outputs.
Business
Phase C โ€” Information Systems Architecture
Application layer + Data
Application components, interfaces, services, data objects, and flows. Application Usage and Co-operation viewpoints are primary outputs.
Application
Phase D โ€” Technology Architecture
Technology + Physical layers
Nodes, devices, system software, technology services, and artefacts. Technology and Technology Usage viewpoints are primary outputs.
TechnologyPhysical
Phase E โ€” Opportunities & Solutions
Cross-layer + Implementation
Identify work packages, gaps, and migration projects. Migration and Gap Analysis viewpoints become relevant here.
All layers
Phase F โ€” Migration Planning
Implementation + Migration layer
Work packages, projects, and plateaus modelled in ArchiMate's Implementation & Migration layer โ€” showing transition states.
Impl. & Migration
๐Ÿ› TOGAF 4 Architecture Domains โ†’ ArchiMate Layers
Business Architecture
โฌ‡๏ธ
Business Layer
Processes, roles, services
Data Architecture
โฌ‡๏ธ
Application Layer (Data)
Data Objects
Application Architecture
โฌ‡๏ธ
Application Layer
Components, services
Technology Architecture
โฌ‡๏ธ
Technology Layer
Nodes, devices, infrastructure
Key tools for ArchiMate modelling: Archi (free, open-source โ€” most popular for learning), Enterprise Architect (Sparx), BiZZdesign, Mega, Alfabet, and Orbus iServer. All support ArchiMate 3 notation and can export to TOGAF-compatible formats.
40 flash cards covering ArchiMate 3 elements, relationships, viewpoints, and exam-relevant knowledge. Click a card to flip it.
Card 1 of 40
Question
Tap to reveal answer
Answer