ArchiMate 3.2 Specification
The ArchiMate 3.2 Specification (The Open Group, 2022) defines the ArchiMate enterprise architecture modelling language: its layers (strategy, business, application, technology, physical), the motivation and implementation and migration aspects, the relationships and derivation rules, the viewpoint mechanism and the customization mechanisms, together with the conformance requirements a model or tool must meet to claim ArchiMate conformance.
ArchiMate 3.2 Specification is a compliance framework from International with 14 domains and 72 controls. The largest domains are Relationships and derivation rules (chapter 5 and Appendix B) – ArchiMate 3.2 Specification (20 controls), Language structure and generic metamodel: layers, aspects, element and relationship classification (chapters 3 and 4) – ArchiMate 3.2 Specification (12 controls), ArchiMate 3.2 element, relationship and viewpoint summary (3.2 reference cards) – ArchiMate 3.2 Specification (8 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are interpretations grounded in the published source, for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (14)
Application layer elements (chapter 9) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-9.1 | Application metamodel relationship legality |
| archimate-3-2-specification::AM-9.2 | Application active structure elements |
| archimate-3-2-specification::AM-9.3 | Level of detail for application behaviour |
ArchiMate 3.2 element, relationship and viewpoint summary (3.2 reference cards) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-p.-12 | Implementation and migration element set |
| archimate-3-2-specification::AM-p.-13 | Grouping and location elements |
| archimate-3-2-specification::AM-p.-2 | Relationship types and junction connectors |
| archimate-3-2-specification::AM-p.-3-4 | Motivation element set |
| archimate-3-2-specification::AM-p.-5 | Strategy layer element set |
| archimate-3-2-specification::AM-p.-6-7 | Business layer element set |
| archimate-3-2-specification::AM-p.-8 | Application layer element set |
| archimate-3-2-specification::AM-p.-9-11 | Technology layer element set |
Business layer elements (chapter 8) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-8.1 | Business layer types and their abstract base elements |
| archimate-3-2-specification::AM-8.2 | Internal active structure types used in the business layer |
| archimate-3-2-specification::AM-8.3 | Separating external from internal business behaviour |
Implementation and migration elements (chapter 13) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-13.1 | Non-exhaustive metamodel relationships |
| archimate-3-2-specification::AM-13.2 | Implementation and migration element semantics |
| archimate-3-2-specification::AM-13.3 | Standard relationships for implementation elements |
| archimate-3-2-specification::AM-13.4 | Links to core and motivation elements |
Introduction, definitions and conformance (chapters 1 and 2) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-1.3 | Conformance requirements for implementations |
Language customization mechanisms: specialization, attributes, profiles (chapter 15) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-15.1 | Attributes and profiles |
| archimate-3-2-specification::AM-15.2 | Profiles and specialization |
Language structure and generic metamodel: layers, aspects, element and relationship classification (chapters 3 and 4) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-3.3 | Core language layers |
| archimate-3-2-specification::AM-3.4 | Cells of the ArchiMate core framework |
| archimate-3-2-specification::AM-3.5 | Framework coverage beyond the core cells |
| archimate-3-2-specification::AM-3.6 | Modeling abstraction and refinement |
| archimate-3-2-specification::AM-3.7 | Concepts kept separate from notation |
| archimate-3-2-specification::AM-4.1 | Generic behavior and structure metamodel |
| archimate-3-2-specification::AM-4.1.1 | Internal and external active structure elements |
| archimate-3-2-specification::AM-4.1.2 | Behaviour, services and events as dynamic elements |
| archimate-3-2-specification::AM-4.1.3 | Passive structure elements |
| archimate-3-2-specification::AM-4.3 | Concrete element types in models |
| archimate-3-2-specification::AM-4.5.1 | Grouping membership and meaning |
| archimate-3-2-specification::AM-4.5.2 | Location through aggregation |
Motivation elements (chapter 6) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-6.1 | Motivation element set and permitted relationships |
| archimate-3-2-specification::AM-6.2 | Stakeholders, drivers and assessments |
| archimate-3-2-specification::AM-6.3 | Intent concepts: goals, outcomes, principles, requirements and constraints |
| archimate-3-2-specification::AM-6.4 | Recording meaning and value for concepts |
| archimate-3-2-specification::AM-6.6 | Connecting motivation elements with core elements |
Physical elements (chapter 11) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-11.1 | Physical metamodel permitted relationships |
| archimate-3-2-specification::AM-11.3 | No separate physical behaviour elements |
Relationships and derivation rules (chapter 5 and Appendix B) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-5 | Relationship validity and clarity |
| archimate-3-2-specification::AM-5.1 | Structural link endpoints |
| archimate-3-2-specification::AM-5.1.1 | Composition and existence dependency |
| archimate-3-2-specification::AM-5.1.2 | Aggregation without ownership |
| archimate-3-2-specification::AM-5.1.3 | Assignment direction and allocation |
| archimate-3-2-specification::AM-5.1.4 | Realization and critical contribution |
| archimate-3-2-specification::AM-5.1.5 | Structural link transitivity |
| archimate-3-2-specification::AM-5.2.1 | Serving direction and legacy label |
| archimate-3-2-specification::AM-5.2.2 | Access to passive structure |
| archimate-3-2-specification::AM-5.2.3 | Influence on motivation elements |
| archimate-3-2-specification::AM-5.2.4 | Association use and direction |
| archimate-3-2-specification::AM-5.2.5 | Dependency scope and derivation |
| archimate-3-2-specification::AM-5.3.1 | Triggering precedence |
| archimate-3-2-specification::AM-5.3.2 | Flow as transfer only |
| archimate-3-2-specification::AM-5.3.3 | Triggering and flow semantics |
| archimate-3-2-specification::AM-5.4.1 | Specialization hierarchy |
| archimate-3-2-specification::AM-5.5.1 | Junction validity and meaning |
| archimate-3-2-specification::AM-5.7 | Derived relationships only summarise, never add detail |
| archimate-3-2-specification::AM-B.1 | Limits on derivation rule use |
| archimate-3-2-specification::AM-B.2.1 | Transitivity of specialization relationships |
Relationships between core layers (chapter 12) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-12.1 | Business and lower layer alignment |
| archimate-3-2-specification::AM-12.2 | Application and technology alignment |
Stakeholders, architecture views and viewpoints (chapter 14) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-14.3 | Views governed by viewpoints |
| archimate-3-2-specification::AM-14.4 | Two-step viewpoint creation |
| archimate-3-2-specification::AM-14.4.1 | Viewpoint purpose and content classification |
| archimate-3-2-specification::AM-14.4.2 | Constructing views under a viewpoint |
Strategy elements (chapter 7) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-7.1 | Strategy element set and permitted relationships |
| archimate-3-2-specification::AM-7.2 | Resources as strategy structure elements |
| archimate-3-2-specification::AM-7.3 | Strategy behaviour: capability, value stream and course of action |
| archimate-3-2-specification::AM-7.6 | Linking strategy elements to motivation and core elements |
Technology layer elements (chapter 10) – ArchiMate 3.2 Specification
| Code | Title |
|---|---|
| archimate-3-2-specification::AM-10.1 | Technology metamodel permitted relationships |
| archimate-3-2-specification::AM-10.4 | Technology object passive structure |
What is ArchiMate 3.2 Specification and who does it apply to?
ArchiMate 3.2 Specification is a compliance framework from International with 14 domains and 72 controls. The ArchiMate 3.2 Specification (The Open Group, 2022) defines the ArchiMate enterprise architecture modelling language: its layers (strategy, business, application, technology, physical), the motivation and implementation and migration aspects, the relationships and derivation rules, the viewpoint mechanism and the customization mechanisms, together with the conformance requirements a model or tool must meet to claim ArchiMate conformance. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does ArchiMate 3.2 Specification actually require?
ArchiMate 3.2 Specification has 72 controls organised across 14 domains. The largest domains are Relationships and derivation rules (chapter 5 and Appendix B) – ArchiMate 3.2 Specification (20 controls), Language structure and generic metamodel: layers, aspects, element and relationship classification (chapters 3 and 4) – ArchiMate 3.2 Specification (12 controls), ArchiMate 3.2 element, relationship and viewpoint summary (3.2 reference cards) – ArchiMate 3.2 Specification (8 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of ArchiMate 3.2 Specification do I already cover?
ArchiMate 3.2 Specification does not currently have cross-framework mappings in our system. Check back as we continuously expand our mapping database.
How do I implement ArchiMate 3.2 Specification?
Start your ArchiMate 3.2 Specification compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about ArchiMate 3.2 Specification requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 72 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 1,305 frameworks.
Get Started Free →Free forever, no credit card required