ArchiMate® 4 — Enterprise Architecture Modelling Language
The international standard for enterprise architecture modelling — the visual language of TOGAF.
Understanding ArchiMate® 4 — Enterprise Architecture Modelling Language
What Is ArchiMate
ArchiMate is The Open Group's open and independent modelling language for enterprise architecture. Version 4 introduces architecture domains (previously called layers) — Business, Application, and Technology — anchored by a Common Domain providing shared elements across all three. ArchiMate 4 consolidates behaviour elements (service, process, function, event) into a single shared set, merges domain-specific collaborations into one collaboration element, and replaces the former business role with a generic role element. It provides a consistent visual language that makes enterprise architectures understandable across stakeholder groups.
ArchiMate & TOGAF
ArchiMate is the natural visual language for TOGAF. While TOGAF provides the methodology and process, ArchiMate provides the notation for expressing architecture artefacts — from architecture vision diagrams to application landscape maps and technology infrastructure views. Used together, they form a complete EA practice.
Portamus & ArchiMate
Portamus uses ArchiMate 4 in all EA design and architecture documentation work. This means clients receive architecture models that are tool-agnostic, standards-compliant, and understandable by architects, IT managers, and business stakeholders alike — ensuring architecture knowledge remains with the client.
Where Most Organisations Get Stuck
Inconsistent Architecture Diagrams
No Common Architecture Language
Architecture Knowledge Silos
Stakeholder Communication Gaps
Key Requirements
ArchiMate 4 organises enterprise architecture into three domains and a Common Domain, providing a complete notation system for modelling any aspect of the enterprise.
Business Domain
Models business actors, roles, processes, functions, and services — the 'what the business does' perspective. Business domain elements form the basis for all architecture decisions below.
Application Domain
Models application components, services, data objects, and their interactions — the software that supports business processes and exposes services to the technology domain.
Technology Domain
Models technology components, infrastructure services, networks, and physical devices — the technical infrastructure that hosts and runs application components.
Strategy & Motivation Extensions
Strategy extension adds capabilities, resources, and courses of action. Motivation extension adds stakeholders, drivers, assessments, goals, and principles — enabling architecture to be explicitly linked to business strategy.
Implementation & Migration Extension
Models work packages, deliverables, events, and plateaus — the extension that bridges architecture design to project execution and migration planning.
Scope of Engagement
ArchiMate Model Development
Creation of standards-compliant ArchiMate 4 models across the Business, Application, and Technology domains relevant to your architecture scope.
Architecture Views & Viewpoints
Development of targeted architecture viewpoints for different stakeholder groups — from executive landscape views to detailed technical component diagrams.
Architecture Repository
Establishment of an architecture model repository, ensuring models are version-controlled, accessible, and maintainable beyond the engagement.
Model Quality Review
Review and validation of existing architecture models for ArchiMate 4 compliance, consistency, and completeness.
Modelling Enablement
Practical workshops to build internal ArchiMate modelling capability so your team can maintain and extend models independently.
What You Walk Away With
ArchiMate Architecture Models
Fully documented Business, Application, and Technology domain models in ArchiMate 4 notation.
Architecture Viewpoint Library
A set of reusable viewpoints tailored to key stakeholder perspectives — strategic, operational, and technical.
Landscape Diagrams
Current-state and target-state enterprise landscape diagrams showing the full application and technology estate.
Architecture Repository Setup
A configured and populated architecture model repository for ongoing model management.
Modelling Standards Guide
An organisation-specific modelling convention guide ensuring consistent ArchiMate usage across architects and projects.
What Changes Once You're Certified
Common Architecture Language
Improved Stakeholder Communication
Consistent Architecture Documentation
Better Architecture Decisions
Reduced Architecture Knowledge Risk
How We Structure This Engagement
Understand
Assess the current architecture documentation landscape: existing diagrams, tools, and notation conventions in use, and the stakeholder communication gaps they create.
Scope & Viewpoints
Define the architecture scope and identify the stakeholder groups and viewpoints that will be modelled, ensuring ArchiMate effort is focused where it delivers most value.
Model Development
Develop ArchiMate 4 models domain by domain — starting with the Business domain to anchor the application and technology models in business context.
Validate & Review
Review models with architecture and business stakeholders, validate against TOGAF artefact requirements, and refine to ensure clarity and accuracy.
Embed & Enable
Establish the architecture repository, document modelling standards, and run enablement workshops to transfer ArchiMate capability to the client team.
Services that commonly pair with this engagement.
Questions About ArchiMate® 4 — Enterprise Architecture Modelling Language
Don't see your question here? Our team is happy to walk through the specifics of your environment.
Ask Our Team