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

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?

Behavior: What Is Performed?

Passive Structure: What Is Acted Upon?

Common Confusion Points

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

1. •Layer consistency: Keep elements in appropriate layers; use cross-layer relationships to connect
2. •Service orientation: Expose functionality through services, not direct process/function access
3. •Separation of concerns: Distinguish who (actors/roles), what (behavior), and what's affected (objects)
4. •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 guidance
• •references/layer-details.md - Detailed patterns for each layer

Creating Elements via the API

To create elements in Archi, use the Archi Model API Server. Load the archi-server-api skill for full API workflow details.

Element Type to API Type Mapping

All element types use kebab-case in the API:

Quick API Examples by Layer

Business Layer:

curl -s -X POST http://localhost:8765/model/apply \
  -H "Content-Type: application/json" \
  -d '{"changes": [
    {"op": "createElement", "type": "business-actor", "name": "Customer", "tempId": "e1"},
    {"op": "createElement", "type": "business-process", "name": "Submit Order", "tempId": "e2"},
    {"op": "createElement", "type": "business-service", "name": "Order Processing", "tempId": "e3"}
  ]}'

Application Layer:

curl -s -X POST http://localhost:8765/model/apply \
  -H "Content-Type: application/json" \
  -d '{"changes": [
    {"op": "createElement", "type": "application-component", "name": "Order System", "tempId": "e1"},
    {"op": "createElement", "type": "application-service", "name": "Order Management", "tempId": "e2"},
    {"op": "createElement", "type": "data-object", "name": "Order Record", "tempId": "e3"}
  ]}'

Technology Layer:

curl -s -X POST http://localhost:8765/model/apply \
  -H "Content-Type: application/json" \
  -d '{"changes": [
    {"op": "createElement", "type": "node", "name": "Application Server", "tempId": "e1"},
    {"op": "createElement", "type": "system-software", "name": "PostgreSQL", "tempId": "e2"},
    {"op": "createElement", "type": "artifact", "name": "order-service.jar", "tempId": "e3"}
  ]}'

After each POST /model/apply, poll GET /ops/status?opId=OP_ID for the real IDs.