ArchiMate

Enterprise Architecture Modeling Language

1. Overview: ArchiMate, the international standard for architecture visualization

    flowchart LR
    A["Informal, ad-hoc modeling"] -- "Shift to a standardized visual language" --> B["ArchiMate modeling"]

Definition: An open modeling language for visually representing the relationships among business processes, organizational structure, information flows, IT systems, and infrastructure within an Enterprise Architecture (EA).

Characteristics: (TOGAF compatible) High compatibility with the TOGAF EA framework provides consistent enterprise architecture representation. (Layer correlation) Visualizes vertical correlations between the business, application, and technology layers using formal notation. (Horizontal relationships) Structurally expresses horizontal relationships between aspects, communicating complex architecture clearly.

2. ArchiMate’s layer structure and core framework

A. ArchiMate core framework (Layers & Aspects)

    flowchart TB
    subgraph Aspects["Core Aspects"]
        direction LR
        PA["Passive Structure<br/>(information objects)"]
        BA["Behavior<br/>(activities/services)"]
        AA["Active Structure<br/>(performing actors)"]
    end

    subgraph Layers["Core Layers"]
        L1["Strategy Layer"]
        L2["Business Layer"]
        L3["Application Layer"]
        L4["Technology Layer (infrastructure)"]
        L5["Implementation & Migration"]
    end

    L1 --- L2 --- L3 --- L4 --- L5
    Aspects -.-> Layers

    style L2 fill:#FFF9C4,stroke:#FBC02D
    style L3 fill:#E1F5FE,stroke:#0288D1
    style L4 fill:#E8F5E9,stroke:#388E3C

Layer	Description	Key elements
Strategy	Represents the organization’s vision, goals, capabilities, and value streams	Resource, Capability, Course of Action
Business	Models business processes, roles, products, and services	Business Actor, Role, Process, Product
Application	Represents software components and their interactions	Application Component, Service, Interface
Technology	Hardware, software platforms, and network infrastructure technology	Node, System Software, Device, Path

B. Relationships and notation between ArchiMate elements

    flowchart TD
  ROOT["ArchiMate Relationships & Notation"]
  R1["Structural Relationships"]
  R2["Dynamic Relationships"]
  R3["Dependency Relationships"]
  R4["Other Relationships"]

  ROOT --> R1
  ROOT --> R2
  ROOT --> R3
  ROOT --> R4

  R1 --> C1["Composition"]
  R1 --> C2["Aggregation"]
  R1 --> C3["Assignment"]

  R2 --> D1["Triggering"]
  R2 --> D2["Flow"]

  R3 --> E1["Access"]
  R3 --> E2["Influence"]
  R3 --> E3["Serving"]

  R4 --> F1["Specialization"]
  R4 --> F2["Association"]

  style ROOT fill:#1E3A5F,color:#fff

Type	Name	Notation description
Serving	Serving	A service in one layer supports an activity in another layer
Realization	Realization	A physical/logical entity implements an abstract service
Assignment	Assignment	An actor is designated to perform a specific behavior

3. Expected benefits and practical application of adopting ArchiMate

Category	Key expected benefit	Practical application
Communication	Highly readable visualization	Standardized diagrams improve mutual understanding between business and IT departments
Traceability	Cross-layer impact analysis	Analyze connected relationships from strategy down to infrastructure to minimize change impact
Integration	Complements TOGAF	Used as the modeling standard for artifacts produced at each stage of the TOGAF ADM

DoDAF 4+1 View Model