ArchiMate 3.2 cheat sheet: relationships, layers, derivation and the exams
Everything a working architect needs on one page: the eleven relationships and the junction with their notation, the layers and aspects, the elements, how derivation actually works, and how the ArchiMate 3 Foundation and Practitioner exams are built. ArchiMate 4 was published in April 2026, but the certification still tests 3.2, so 3.2 is what this page covers.
ArchiMate 3.2 relationships cheat sheet
ArchiMate 3.2 has eleven relationships in four families (structural, dependency, dynamic and other), plus one relationship connector, the junction. This is the table worth keeping next to the modelling tool: what each relationship means, how it is drawn, and how it reads aloud. Element and relationship names keep the specification's spelling.
| Relationship | Family | How it is drawn | What it means | Reads as |
|---|---|---|---|---|
| Composition | Structural | Solid line, filled diamond at the whole | The whole consists of the part, and the part does not exist without the whole | composed of / composed in |
| Aggregation | Structural | Solid line, hollow diamond at the whole | The whole combines parts that can exist on their own | aggregates / aggregated in |
| Assignment | Structural | Solid line, dot at the source, arrowhead at the target | Who or what performs, is responsible for, stores or executes something | assigned to / has assigned |
| Realization | Structural | Dotted line, hollow triangle at the more abstract element | A more concrete element brings a more abstract one into being, or achieves it | realizes / realized by |
| Serving | Dependency | Solid line, open arrowhead at the user | An element offers its functionality to another element | serves / served by |
| Access | Dependency | Dotted line, optional small arrowhead | Behaviour or active structure reads or writes a passive structure element; the arrowhead shows which way the data goes | accesses / accessed by |
| Influence | Dependency | Dashed line, open arrowhead, optional +/- label | Something helps or hinders a motivation element without being decisive for it | influences / influenced by |
| Association | Dependency | Plain solid line; a half arrowhead if directed | An unspecified link, or one that no other relationship covers | associated with |
| Triggering | Dynamic | Solid line, filled arrowhead | Time or cause: part of the source has to happen before the target can start | triggers / triggered by |
| Flow | Dynamic | Dashed line, filled arrowhead | Something (information, goods, money) passes from one behaviour to another, with no causality implied | flows to / flows from |
| Specialization | Other | Solid line, hollow triangle at the general element | The source is a particular kind of the target, of the same element type | specializes / specialized by |
| Junction | Connector | Filled dot (and junction) or hollow circle (or junction) | Joins relationships of one type to say "all of these together" or "at least one of these" | no role name |
Three facts settle a surprising number of exam questions. Composition, aggregation and specialization are always allowed between two elements of the same type. Association is always allowed between any two elements, and between an element and a relationship. Everything else is governed by the relationship tables in Appendix B of the specification, which list every permitted pair.
Direction matters more than people expect. Most arrows in a well-drawn ArchiMate view point upwards, towards the business and the user: a service serves a process, an application realizes a business behaviour, a technology service serves an application. If you come from UML, your instinct for dependency arrows runs the other way, and that instinct is wrong here.
ArchiMate 3.2 or ArchiMate 4: which version to learn now
The Open Group published the ArchiMate 4 Specification (document C260) on 27 April 2026, and its publication record lists it as superseding the ArchiMate 3.2 Specification (C226, published 19 October 2022). So 3.2 is no longer the newest version of the language.
The certification has not moved. On 10 November 2026 The Open Group's certification page still says that the current program is the ArchiMate 3 certification, covering the 3.2 release of the specification, and its exam fact sheets describe the ArchiMate 3 Part 1 and Part 2 exams. No ArchiMate 4 exam is announced on that page. If you are studying for a certificate, study 3.2.
ArchiMate 4 is a restructuring rather than a point release. The Open Group's own publication page lists the main changes:
- The three interaction elements are gone, as are constraint, contract, gap and representation.
- Behaviour is merged across layers into one set of service, process, function and event; the implementation event becomes a generic event.
- Business, application and technology collaboration merge into a single collaboration, and business role becomes a generic role.
- "Layer" becomes "domain", the generic metamodel chapter becomes a common domain chapter, and path moves into it.
- Relationships can carry multiplicity, and the framework is drawn as a layered hexagon rather than a grid.
The Open Group's announcement stresses strong user-level compatibility and retention of the core concepts, so time spent learning 3.2 properly is not wasted.
My advice: learn 3.2 if you need the certificate this year or maintain a repository built in 3.2. Check the certification page before you book, though. Given how much the element set changes in ArchiMate 4, expect the exam content to change substantially when a new exam arrives.
The ArchiMate framework: layers and aspects
The ArchiMate Core Framework is a grid of nine cells: three layers (Business, Application, Technology) crossed with three aspects. The aspects borrow the grammar of a sentence. Active structure is the subject, the thing that does the work (an actor, an application component, a device). Behaviour is the verb (processes, functions, events, services). Passive structure is the object that behaviour works on (business objects, data objects, artifacts).
The Full Framework adds the rest of the language around that core:
| Part | What it models | Where it sits |
|---|---|---|
| Strategy | Strategic direction and choices: capabilities, resources, value streams, courses of action | A layer above Business |
| Business | Business services offered to customers, realized by processes performed by actors | Core layer |
| Application | Application services that support the business, and the applications that realize them | Core layer |
| Technology | Information and operational technology: processing, storage, networks, system software | Core layer |
| Physical | Equipment, facilities, distribution networks and materials | Inside the Technology Layer in 3.2, so physical elements count as core elements |
| Implementation and Migration | Programmes, projects, deliverables, plateaus and gaps | A layer below Technology |
| Motivation | Why: stakeholders, drivers, goals, outcomes, principles, requirements | An extra aspect beside the other three, relating to every layer |
Two refinements run through every core layer. First, internal versus external: an interface is the external face of active structure (a point of access), a service is the external face of behaviour (what is exposed), and processes, functions and interactions are the internal behaviour that realizes it. Second, the event, a behaviour element that marks a state change and may carry a time.
Some elements deliberately span aspects. These are composite elements: grouping and location at the generic level, plus product in the Business Layer and plateau in Implementation and Migration.
Notation conventions worth knowing
- Corner shape carries meaning: square corners for structure, rounded corners for behaviour, cut (diagonal) corners for motivation.
- Colour carries none. Yellow for business, blue for application and green for technology is a convention used in the specification's examples, not a rule.
- An optional letter in the top-left corner (M, S, B, A, T, P or I) marks Motivation, Strategy, Business, Application, Technology, Physical or Implementation and Migration elements.
- There is no information layer. Information runs through the layers as business object (conceptual), data object (logical) and artifact (physical), joined by realization.
- ArchiMate models types and exemplars, not instances. One "Insurance Policy" business object stands for every policy the company issues.
Core elements in each ArchiMate layer
The same pattern repeats in every core layer, which is the single most useful thing to notice when learning the element set. Once you know the generic shape, each layer is a specialization of it.
| Layer | Active structure | Behaviour | Passive structure |
|---|---|---|---|
| Strategy | Resource (structure, neither active nor passive) | Capability, Value Stream, Course of Action | No separate element |
| Business | Business Actor, Business Role, Business Collaboration, Business Interface | Business Process, Business Function, Business Interaction, Business Event, Business Service | Business Object, Contract, Representation (Product is a composite) |
| Application | Application Component, Application Collaboration, Application Interface | Application Process, Application Function, Application Interaction, Application Event, Application Service | Data Object |
| Technology | Node, Device, System Software, Technology Collaboration, Technology Interface, Path, Communication Network | Technology Process, Technology Function, Technology Interaction, Technology Event, Technology Service | Artifact |
| Physical (part of Technology) | Equipment, Facility, Distribution Network | No separate elements; technology behaviour is used | Material |
Motivation elements (10): Stakeholder, Driver, Assessment, Goal, Outcome, Principle, Requirement, Constraint, Meaning, Value.
Implementation and Migration elements (5): Work Package, Deliverable, Implementation Event, Plateau, Gap.
Generic composite elements (2): Grouping, Location.
The pairs that cause most wrong answers
- Business Actor versus Business Role. The actor is who (a person, team or organisation). The role is the responsibility, which actors are assigned to. Assign behaviour to roles and the model survives a reorganisation.
- Process versus function. A process is a sequence that reaches a defined result; you can draw triggering arrows between its steps. A function groups behaviour by a criterion such as competence or resources, and has no inherent order.
- Interaction versus collaboration. An interaction is behaviour that needs two or more performers; a collaboration is the aggregate of active structure elements that performs it together.
- Service versus interface. The service is the behaviour you expose; the interface is where it is reached. "Online claims submission" is a service; the customer portal is an interface.
- Capability, function and value stream. A capability is what the enterprise is able to do, stated at strategy level and realized by core elements. A value stream is the sequence of stages that creates value for a stakeholder. A business function is how the organisation groups its own behaviour. A value stream and a business process may look alike, but they sit at different levels of abstraction.
- Goal, outcome, principle, requirement, constraint. A goal states intent or direction. An outcome is an end result actually achieved. A principle applies to any system in a context; a requirement applies to a specific system. A constraint limits the architecture, its implementation or its realization.
- Driver versus assessment. The driver is the condition that motivates change (regulation, customer churn); the assessment is the result of analysing it.
- Node, device and system software. A device is physical IT hardware; system software provides the environment software runs in; a node is a computational or physical resource that hosts others, and is often composed of a device and system software.
ArchiMate relationship rules that decide most diagrams
ArchiMate relationships are deliberately overloaded: the same relationship means slightly different things depending on what it connects. The rules below are the ones that decide whether a diagram is valid and whether it says what you intended.
Hard restrictions
- Every relationship has exactly one source and one target.
- No relationship may connect two relationships.
- A relationship from an element to another relationship can only be an association, or an aggregation or composition from a composite element (for example a grouping or plateau holding a relationship). The classic case is associating a business object with a flow to say what is transferred.
- A junction joins relationships of one type only, and a path through junctions is valid only if a direct relationship of that type would be valid. You cannot use a junction to smuggle in a relationship the tables forbid.
Direction conventions
- Assignment runs from active structure to behaviour (the component to the function it performs), from an actor to a role, and from a node to the artifact it stores or executes.
- Serving runs from provider to consumer. It deliberately abstracts from who initiates the exchange; use triggering if the initiative is what you want to show.
- Access is always modelled from the behaviour or active structure element to the passive one. The arrowhead shows read or write, not the direction of the relationship, which matters when you derive.
- Realization runs from the concrete to the abstract: process to service, data object to business object, artifact to application component, core element to requirement.
Choosing between near neighbours
- Realization or influence? Realization when the source is critical to the target existing or being achieved; influence when it contributes, positively or negatively, without being decisive. Influence can carry a sign and strength such as ++ or -.
- Triggering or flow? Triggering is about order and cause. Flow is about something moving between behaviours and says nothing about which happens first.
- Two triggers or an or junction? Two triggering lines out of one process mean both targets follow. To show a choice, route them through an or junction and label the branches.
- Nesting or lines? Structural relationships may be shown by nesting one element inside another. The model stays unambiguous, but the view does not when more than one structural relationship would be legal. In any view someone else will reuse, I draw the line.
Across the layers
Business-IT alignment in ArchiMate rests on two relationships. Serving links them behaviourally and structurally: an application service serves business behaviour, an application interface serves a business role, a technology service serves application behaviour. Realization links them by implementation: an application process or function realizes a business process or function, a data object realizes a business object, and an artifact realizes a data object or an application component. Applications never realize business actors or roles, because technology cannot realize people; it can realize the behaviour they perform.
The other extensions follow the same logic. Core behaviour realizes capabilities and value streams, and structure realizes resources. Deliverables realize core elements and requirements; plateaus aggregate the parts of the architecture valid in their time span (in 3.2 they may also aggregate outcomes); a gap is associated with the two plateaus it compares; implementation events trigger, or are raised by, work packages. Note one deprecation that catches people out: work package realizes deliverable is deprecated in 3.2, and the specification recommends an access relationship instead.
ArchiMate derivation rules, explained for practitioners
Derivation is ArchiMate's most distinctive feature and its least understood. It lets you replace a chain of relationships with one summary relationship, so a CIO-level view can show "this application serves this business process" without the functions and services in between. Derivation always goes from more detail to less. It never works backwards: a derived relationship tells you nothing about which intermediate elements produced it.
Appendix B of the specification distinguishes two kinds. Valid derivations (rules DR 1 to DR 8) are always true in a well-formed model. Potential derivations (rules PDR 1 to PDR 12) might be true and might not, and the modeller decides. Here is the valid set, paraphrased:
| Rule | When two relationships meet like this | You can derive |
|---|---|---|
| DR 1 | Specialization followed by specialization | Specialization: it is transitive |
| DR 2 | Two structural relationships in a chain | The weaker of the two. Strength order: realization (weakest), assignment, aggregation, composition (strongest) |
| DR 3 | A structural relationship from a to b, then a dependency from b to c | The dependency, from a to c |
| DR 4 | A structural relationship from a to b, and a dependency from c into b | The dependency, from c to a |
| DR 5 | A structural relationship from a to b, then a dynamic relationship from b to c | The dynamic relationship, from a to c |
| DR 6 | A structural relationship from a to b, and a flow from c into b | A flow from c to a |
| DR 7 | A triggering from a to b, then a structural relationship from b to c | A triggering from a to c |
| DR 8 | Triggering followed by triggering | Triggering: it is transitive |
Put informally: a chain of structural relationships collapses to its weakest link, and the ends of a dependency or flow can slide back along a chain of structural relationships.
A worked example
The "Billing Engine" application component is assigned to the "Calculate Charges" application function, which realizes the "Charge Calculation" application service, which serves the "Issue Invoice" business process. Assignment followed by realization collapses to realization, the weaker of the two (DR 2), so Billing Engine realizes Charge Calculation. Realization followed by serving gives serving (DR 3), so Billing Engine serves Issue Invoice. That last relationship is the one the process owner wants to see, and it is valid without the two elements in the middle.
Potential derivations and the limits
The potential rules cover cases that are often, but not always, true: pushing a relationship onto a specialized or generalized element, copying a dependency from a whole onto its parts, chaining two dependencies (where the result is the weaker, in the order association, influence, access, serving), combining dynamic and structural relationships, chaining flows, and inferring relationships through a grouping. Treat every one as a question to answer, not a fact.
Derivation also has boundaries. The rules do not carry relationships between core elements and the motivation, strategy or implementation and migration elements, except for realization and influence. In general the intermediate element has to sit in the same domain as one of the two ends. The relationship tables in Appendix B already apply all of this, which is why they are the final word on what is allowed.
Views and viewpoints in ArchiMate 3.2
A view is what you show; a viewpoint is the position you show it from: the stakeholders and concerns it addresses, and the conventions for building it. ArchiMate's mechanism follows ISO/IEC 42010. Defining a viewpoint takes two steps: select the subset of elements and relationships that answers the stakeholder's concern, then choose a representation they understand. That can be a standard diagram, a catalogue, a matrix or something else entirely; a view does not have to be a picture.
The specification classifies viewpoints along two dimensions:
- Purpose: designing (architects and designers, usually diagrams), deciding (managers, usually cross-references, landscape maps, lists and reports) and informing (anyone who needs to understand or commit, usually illustrations).
- Content: details (one layer and one aspect), coherence (several layers or several aspects) and overview (several layers and several aspects).
Appendix C lists example viewpoints. Since ArchiMate 3 they sit in an informative appendix precisely so that nobody mistakes them for a mandatory or complete set.
| Group | Example viewpoints |
|---|---|
| Basic: composition | Organization, Application Structure, Information Structure, Technology, Layered, Physical |
| Basic: support | Product, Application Usage, Technology Usage |
| Basic: cooperation | Business Process Cooperation, Application Cooperation |
| Basic: realization | Service Realization, Implementation and Deployment |
| Motivation | Stakeholder, Goal Realization, Requirements Realization, Motivation |
| Strategy | Strategy, Capability Map, Value Stream, Outcome Realization, Resource Map |
| Implementation and Migration | Project, Migration, Implementation and Migration |
Grouping and junctions may be used in every viewpoint. Do not confuse a grouping with a view: a grouping is part of the model and says its contents belong together; a view is a selection from the model for a stakeholder.
In practice, the Layered viewpoint is overused. It is the one everyone draws first, and it rarely answers anyone's actual question. Start from the concern ("what breaks if we retire this server?") and the right viewpoint usually picks itself.
Common ArchiMate modelling mistakes
These are the errors I see most often in real repositories and in exam answers. Several of them pass a tool's validation, which is exactly why they survive.
| Mistake | Why it is wrong | What to do instead |
|---|---|---|
| Serving arrow pointing at the provider | Serving runs from provider to user; the UML dependency habit reverses it | Read it aloud: "the service serves the process" |
| Assigning an application component to a business process | Not permitted since ArchiMate 3; assignment means an active structure element performing behaviour | Let the component realize the business process (through its function), or let an application service serve it |
| An application realizing a business actor or role | Technology cannot realize people | Realize the behaviour the role performs, or serve the role through an application interface |
| Association everywhere | Always legal, so it never fails validation, and it says nothing | Use it in early sketches, then replace it with the specific relationship |
| Modelling a function as a process, or the reverse | A process has order and a result; a function is a stable grouping of behaviour | If the steps can be joined by triggering arrows, it is a process |
| Treating capabilities as the organisation chart | A capability says what the enterprise is able to do, not how it is organised to do it | Realize capabilities with processes, functions, applications and resources |
| Modelling instances | ArchiMate models types and exemplars, not individual records or executions | One "Invoice" business object, not one per invoice |
| Letting colour carry meaning | Colour has no formal semantics in ArchiMate | Rely on the element type; use the letter notation or attribute-based colouring with a legend |
| A junction mixing relationship types | A junction connects one type only and cannot legalise a forbidden relationship | Split it into separate junctions per type |
| Two triggers for a decision | Without an or junction, both targets follow | Route the branches through an or junction and label them |
| Reading detail out of a derived relationship | Derivation summarises; it cannot be reversed | Model the intermediate elements where the detail matters |
| Work package realizes deliverable | Deprecated in 3.2 | Use an access relationship from the work package to the deliverable |
A last one that no validator catches: diagrams with no stated concern. If you cannot say in one sentence which stakeholder question a view answers, it is decoration, however correct the notation.
ArchiMate 3 Foundation and Practitioner certification
The ArchiMate 3 certification program has two levels, both defined for the ArchiMate 3.2 Specification. Foundation validates knowledge and comprehension of the notation, terminology, structure and basic concepts, and is achieved by passing the Part 1 exam. Practitioner validates that you can analyse and apply that knowledge, and is achieved by passing the Part 2 exam. The syllabus is The Open Group's ArchiMate 3 Conformance Requirements (Multi-Level), Version 3.2.
| Part 1 (OGA-031) | Part 2 (OGA-032) | |
|---|---|---|
| Leads to | ArchiMate 3 Foundation, plus partial credit towards Practitioner | ArchiMate 3 Practitioner |
| Questions | 40, simple multiple choice | 8 complex, scenario-based questions |
| Scoring | 1 point per correct answer | Gradient: 5 points for the best answer, 3 for the second best, 1 for the third, 0 for the distractor |
| Pass mark | 60% (24 of 40) | 65% (26 of 40 points) |
| Time | 60 minutes | 90 minutes |
| Open book | No | Yes: an electronic copy of the ArchiMate 3 Specification is built into the exam; no paper books |
| Prerequisite | None | ArchiMate 3 Foundation, or a pass in Part 1 on the same day at the same test centre |
| Delivery | Pearson VUE test centres, or online through OnVUE | Pearson VUE test centres, or online through OnVUE |
Both exams are supervised. Extra time may be given to candidates sitting the English exam whose first language is not English, and the provider's booking may show a longer slot than the exam time because it includes registration, a tutorial and a survey (typically about 15 extra minutes). Accredited training courses include the exam in the course fee by voucher; you can also pay the exam provider directly when booking.
The Practitioner fact sheet lists what a certified Practitioner can apply: the language structure including its advanced concepts, the generic metamodel, the relationships, the motivation, strategy, business, application and technology elements, cross-layer modelling, implementation and migration, the viewpoint mechanism and the language customization mechanisms. That is the whole specification, so do not skip the last two chapters.
You will also see an ArchiMate Essentials 3.2 credential on The Open Group's site. It is aimed at accredited trainers, not a third level of practitioner certification.
How I would prepare
- Part 1 is recall under time pressure. Forty questions in sixty minutes leaves no time to reason from first principles. Element names, their layer and aspect, the notation and the meaning of each relationship need to be instant.
- Part 2 rewards judgement, not memory. All four answers will look plausible, and gradient scoring pays for choosing the best one while still giving partial credit for the second best. Read the scenario's stakeholder and concern first, then check each option's relationships against the rules.
- Learn to navigate the specification before exam day. It is built into the Part 2 exam, so knowing where the Appendix B relationship tables, the derivation rules and the Appendix C viewpoints sit is worth more than memorising them.
- Do not study from ArchiMate 4 material for these exams. Elements that ArchiMate 4 removed, such as contract, gap and the interactions, are still part of 3.2, and 3.2 is what the exams cover.
Practise it, not just read it
Reading a cheat sheet is not the same as spotting a misdrawn assignment against the exam clock. ArchiMate 3.2 Practice drills the layers, elements and relationships until the notation is second nature, with an explanation behind every answer: what the element actually means, and what the distractor confuses it with. It concentrates on the relationship rules people actually get wrong, tracks your accuracy and pace per topic so revision goes where it is needed, and on Pro runs timed mock exams in exam format. The AI tutor runs on your iPhone through Apple Intelligence (iOS 26), so your questions never leave the device. There is a free daily practice allowance, and a web version too.
Common questions
What are the relationships in ArchiMate 3.2?
Eleven relationships in four families, plus a connector. Structural: composition, aggregation, assignment, realization. Dependency: serving, access, influence, association. Dynamic: triggering, flow. Other: specialization. The junction (and or or) connects relationships of the same type.
Is ArchiMate 3.2 still current now that ArchiMate 4 is out?
The Open Group published ArchiMate 4 (C260) on 27 April 2026 and lists it as superseding the 3.2 specification. The certification program, however, still covers ArchiMate 3.2 according to The Open Group certification page checked on 10 November 2026, so exam candidates should study 3.2.
How many questions are in the ArchiMate 3 Foundation exam, and what is the pass mark?
The ArchiMate 3 Part 1 exam (OGA-031), which leads to Foundation, has 40 simple multiple-choice questions in 60 minutes. The pass mark is 60%, which is 24 correct answers. It is closed book.
Is the ArchiMate Practitioner exam open book?
Yes. The ArchiMate 3 Part 2 exam (OGA-032) has an electronic copy of the ArchiMate 3 Specification built in; paper books are not allowed. It has 8 scenario questions in 90 minutes with gradient scoring (5, 3, 1 or 0 points) and a 65% pass mark, 26 of 40 points.
What is a derived relationship in ArchiMate?
A relationship that summarises a chain of modelled relationships. For example, a component assigned to a function that realizes a service that serves a process can be shown as the component serving the process. Valid derivations are always true; potential ones need the modeller to confirm them.
What is the difference between a view and a viewpoint?
A viewpoint defines the stakeholders, concerns and conventions; a view is the actual selection of model content built according to it. Put simply, the viewpoint is where you look from and the view is what you see.
Sources
- ArchiMate Certification, The Open Group
- ArchiMate Examinations fact sheet (Part 1 and Part 2), The Open Group
- ArchiMate 3 Certification Program Summary, The Open Group
- ArchiMate 3 Practitioner fact sheet, The Open Group
- ArchiMate 3 Conformance Requirements (Multi-Level), Version 3.2 (X238), publication record, The Open Group
- ArchiMate 3.2 Specification (C226), publication record, The Open Group
- ArchiMate 4 Specification (C260), publication record, The Open Group
- The Open Group Announces ArchiMate 4 Specification, The Open Group
- ArchiMate 3.2 Specification Reference Cards (N221), The Open Group
- ArchiMate 3.2 Specification, chapter 3: Language Structure (Open Group sign-in required)
- ArchiMate 3.2 Specification, chapter 4: Generic Metamodel (Open Group sign-in required)
- ArchiMate 3.2 Specification, chapter 5: Relationships and Relationship Connectors (Open Group sign-in required)
- ArchiMate 3.2 Specification, chapter 7: Strategy Layer (Open Group sign-in required)
- ArchiMate 3.2 Specification, chapter 11: Relationships Between Core Layers (Open Group sign-in required)
- ArchiMate 3.2 Specification, chapter 12: Implementation and Migration Layer (Open Group sign-in required)
- ArchiMate 3.2 Specification, chapter 13: Stakeholders, Architecture Views, and Viewpoints (Open Group sign-in required)
- ArchiMate 3.2 Specification, Appendix B: Relationships (Open Group sign-in required)
- ArchiMate 3.2 Specification, Appendix C: Example Viewpoints (Open Group sign-in required)
- ArchiMate 3.2 Specification, Appendix E: Changes from Version 2.1 to Version 3.2 (Open Group sign-in required)
Checked against The Open Group ArchiMate certification page and exam fact sheets, the ArchiMate 3.2 Specification and its Reference Cards, and the ArchiMate 4 publication record on 10 November 2026. Spotted something out of date? Tell me.