M2 ArchiMate 3.2
A full implementation of the ArchiMate 3.2 modelling language from The Open Group. ArchiMate is used for describing, analysing, and visualising architecture across business domains.
Layers and Element Types (61)
Section titled “Layers and Element Types (61)”Strategy Layer (4)
Section titled “Strategy Layer (4)”Resource, Capability, Value Stream, Course of Action
Business Layer (11)
Section titled “Business Layer (11)”Business Actor, Business Role, Business Collaboration, Business Interface, Business Process, Business Function, Business Interaction, Business Event, Business Service, Business Object, Contract
Application Layer (7)
Section titled “Application Layer (7)”Application Component, Application Collaboration, Application Interface, Application Function, Application Interaction, Application Event, Application Service
Technology Layer (10)
Section titled “Technology Layer (10)”Node, Device, System Software, Technology Collaboration, Technology Interface, Technology Function, Technology Interaction, Technology Event, Technology Service, Artifact
Physical Layer (4)
Section titled “Physical Layer (4)”Equipment, Facility, Distribution Network, Material
Motivation Layer (8)
Section titled “Motivation Layer (8)”Stakeholder, Driver, Assessment, Goal, Outcome, Principle, Requirement, Constraint
Implementation & Migration (4)
Section titled “Implementation & Migration (4)”Work Package, Deliverable, Implementation Event, Plateau
Other (13)
Section titled “Other (13)”Junction (And/Or), Grouping, Location, Meaning, Value, Representation, Gap, and composite elements
Relationship Types (11)
Section titled “Relationship Types (11)”| Relationship | Line Style | Markers | Description |
|---|---|---|---|
| Composition | solid | filled diamond at source | Whole-part: the part is inseparable from the whole |
| Aggregation | solid | hollow diamond at source | Whole-part: the part can exist independently |
| Assignment | solid | filled arrow at target | Allocation of responsibility or execution |
| Realization | dashed | hollow arrow at target | Implementation of a specification |
| Serving | solid | arrow at target | Providing functionality to another element |
| Access | dashed | arrow (configurable) | Reading, writing, or accessing data |
| Influence | dashed | arrow at target | Affecting the implementation or achievement |
| Association | solid | none | General, untyped connection |
| Triggering | solid | filled arrow at target | Temporal or causal dependency |
| Flow | dashed | arrow at target | Transfer of information or goods |
| Specialization | solid | hollow arrow at target | More specific variant of the target |
Enumerations (1)
Section titled “Enumerations (1)”Junction Type — And, Or
Constraints
Section titled “Constraints”All 11 relationship types have pair-wise constraints derived from the ArchiMate 3.2 specification. These encode the full relationship validity matrix — which element types each relationship can connect in which direction. The constraint set is extensive (hundreds of valid pairs).
Colour Theme
Section titled “Colour Theme”Colours follow the ARIS colour convention:
- Strategy: cream/beige
- Business: yellow
- Application: blue
- Technology: green
- Physical: green (darker)
- Motivation: purple/lavender
- Implementation & Migration: pink/salmon
SVG icons are based on the Archi tool icon set, normalised to 24x24 viewBox.