ArchiMate Modeling Fundamentals
ArchiMate is The Open Group's standard for enterprise architecture modeling, providing a visual language with 56 elements across 6 core layers connected by 11 relationship types.
The Six Layers
| Layer |
Purpose |
Key Elements |
| Motivation |
Why (stakeholder concerns, goals) |
Stakeholder, Driver, Goal, Requirement, Principle |
| Strategy |
What enterprise intends to achieve |
Capability, Resource, Value Stream, Course of Action |
| Business |
Business operations |
Business Actor, Role, Process, Function, Service, Object |
| Application |
Software and data |
Application Component, Service, Interface, Data Object |
| Technology |
Infrastructure |
Node, Device, System Software, Artifact, Network |
| Implementation & Migration |
Change management |
Work Package, Deliverable, Plateau, Gap |
Three Fundamental Aspects
Every layer contains elements organized into three aspects:
- Active Structure (Nouns): Elements that perform behavior—actors, components, nodes, interfaces
- Behavior (Verbs): Activities performed—processes, functions, services, events
- Passive Structure (Objects): Elements behavior acts upon—business objects, data objects, artifacts
Element Selection Decision Guide
Active Structure: Who/What Performs Behavior?
| Need to model... |
Use |
Not |
| Specific person/system |
Business Actor / Application Component |
Role |
| Responsibility pattern |
Business Role |
Actor |
| Collaboration |
Business Collaboration |
Multiple separate actors |
| External access point |
Interface |
Component |
Behavior: What Is Performed?
| Need to model... |
Use |
Not |
| Sequence with defined result |
Process |
Function |
| Ongoing capability/grouping |
Function |
Process |
| Externally visible functionality |
Service |
Process/Function |
| Something that triggers behavior |
Event |
Process step |
Passive Structure: What Is Acted Upon?
| Need to model... |
Use |
Not |
| Business-level concept |
Business Object |
Data Object |
| Structured application data |
Data Object |
Business Object |
| Perceptible information form |
Representation |
Artifact |
| Deployable file/module |
Artifact |
Data Object |
Common Confusion Points
| Pair |
Use First When... |
Use Second When... |
| Component vs Function |
Static structural unit |
Behavior performed (no structure) |
| Process vs Function |
Has sequence, start/end |
Continuous, no sequence |
| Service vs Process |
External view, what's offered |
Internal, how it's done |
| Actor vs Role |
Specific entity |
Responsibility that can be filled by different actors |
Output Formats
When creating ArchiMate models, use these formats:
Textual Description Format
Element Type: [Name]
Layer: [Layer Name]
Description: [What this element represents]
Relationships:
- [relationship type] → [Target Element]
Notation Format
[Element Type: Name] → [relationship] → [Element Type: Name]
Example:
[Business Role: Claims Handler] → [assignment] → [Business Process: Handle Insurance Claim]
[Business Process: Handle Insurance Claim] → [realization] → [Business Service: Claims Processing]
Key Principles
- Layer consistency: Keep elements in appropriate layers; use cross-layer relationships to connect
- Service orientation: Expose functionality through services, not direct process/function access
- Separation of concerns: Distinguish who (actors/roles), what (behavior), and what's affected (objects)
- Realization chains: Connect logical to physical through realization relationships
Additional Resources
Reference Files
For detailed element catalogs and layer-specific guidance:
references/element-catalog.md - Complete catalog of all 56 ArchiMate elements with usage guidancereferences/layer-details.md - Detailed patterns for each layer
1---2name: archimate-modeling-fundamentals3description: This skill should be used when the user asks about "ArchiMate elements", "which element to use", "ArchiMate layers", "business layer", "application layer", "technology layer", "motivation layer", "strategy layer", "active structure", "passive structure", "behavior elements", or needs help selecting the correct ArchiMate element type for modeling enterprise architecture.4---56# ArchiMate Modeling Fundamentals78ArchiMate is The Open Group's standard for enterprise architecture modeling, providing a visual language with **56 elements** across **6 core layers** connected by **11 relationship types**.910## The Six Layers1112| Layer | Purpose | Key Elements |13|-------|---------|--------------|14| **Motivation** | Why (stakeholder concerns, goals) | Stakeholder, Driver, Goal, Requirement, Principle |15| **Strategy** | What enterprise intends to achieve | Capability, Resource, Value Stream, Course of Action |16| **Business** | Business operations | Business Actor, Role, Process, Function, Service, Object |17| **Application** | Software and data | Application Component, Service, Interface, Data Object |18| **Technology** | Infrastructure | Node, Device, System Software, Artifact, Network |19| **Implementation & Migration** | Change management | Work Package, Deliverable, Plateau, Gap |2021## Three Fundamental Aspects2223Every layer contains elements organized into three aspects:2425- **Active Structure (Nouns)**: Elements that perform behavior—actors, components, nodes, interfaces26- **Behavior (Verbs)**: Activities performed—processes, functions, services, events27- **Passive Structure (Objects)**: Elements behavior acts upon—business objects, data objects, artifacts2829## Element Selection Decision Guide3031### Active Structure: Who/What Performs Behavior?3233| Need to model... | Use | Not |34|------------------|-----|-----|35| Specific person/system | **Business Actor** / **Application Component** | Role |36| Responsibility pattern | **Business Role** | Actor |37| Collaboration | **Business Collaboration** | Multiple separate actors |38| External access point | **Interface** | Component |3940### Behavior: What Is Performed?4142| Need to model... | Use | Not |43|------------------|-----|-----|44| Sequence with defined result | **Process** | Function |45| Ongoing capability/grouping | **Function** | Process |46| Externally visible functionality | **Service** | Process/Function |47| Something that triggers behavior | **Event** | Process step |4849### Passive Structure: What Is Acted Upon?5051| Need to model... | Use | Not |52|------------------|-----|-----|53| Business-level concept | **Business Object** | Data Object |54| Structured application data | **Data Object** | Business Object |55| Perceptible information form | **Representation** | Artifact |56| Deployable file/module | **Artifact** | Data Object |5758## Common Confusion Points5960| Pair | Use First When... | Use Second When... |61|------|-------------------|-------------------|62| **Component vs Function** | Static structural unit | Behavior performed (no structure) |63| **Process vs Function** | Has sequence, start/end | Continuous, no sequence |64| **Service vs Process** | External view, what's offered | Internal, how it's done |65| **Actor vs Role** | Specific entity | Responsibility that can be filled by different actors |6667## Output Formats6869When creating ArchiMate models, use these formats:7071### Textual Description Format72```73Element Type: [Name]74Layer: [Layer Name]75Description: [What this element represents]76Relationships:77- [relationship type] → [Target Element]78```7980### Notation Format81```82[Element Type: Name] → [relationship] → [Element Type: Name]83```8485Example:86```87[Business Role: Claims Handler] → [assignment] → [Business Process: Handle Insurance Claim]88[Business Process: Handle Insurance Claim] → [realization] → [Business Service: Claims Processing]89```9091## Key Principles92931. **Layer consistency**: Keep elements in appropriate layers; use cross-layer relationships to connect942. **Service orientation**: Expose functionality through services, not direct process/function access953. **Separation of concerns**: Distinguish who (actors/roles), what (behavior), and what's affected (objects)964. **Realization chains**: Connect logical to physical through realization relationships9798## Additional Resources99100### Reference Files101102For detailed element catalogs and layer-specific guidance:103- **`references/element-catalog.md`** - Complete catalog of all 56 ArchiMate elements with usage guidance104- **`references/layer-details.md`** - Detailed patterns for each layer
thomasrohde