ArchiMate Modeling Fundamentals
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:
More from thomasrohde/marketplace
drawio diagram creation
This skill should be used when the user asks to "create a diagram", "make a flowchart", "generate a .drawio file", "draw.io diagram", "diagrams.net", "architecture diagram", "sequence diagram", "ER diagram", "class diagram", "network diagram", "org chart", "workflow diagram", "UML diagram", "ArchiMate diagram", "C4 diagram", "C4 model", "enterprise architecture", or mentions "drawio", "mxGraph", or diagram visualization. Provides comprehensive knowledge for creating production-ready DrawIO XML files.
39archimate model quality
This skill should be used when the user asks about "ArchiMate naming conventions", "model quality", "EA smells", "anti-patterns", "ArchiMate best practices", "model review", "abstraction levels", "viewpoints", "model organization", or needs guidance on creating high-quality ArchiMate models.
20archimate relationships
This skill should be used when the user asks about "ArchiMate relationships", "composition vs aggregation", "realization relationship", "serving relationship", "assignment relationship", "triggering", "flow relationship", "access relationship", "influence", "specialization", "cross-layer relationships", or needs help connecting ArchiMate elements correctly.
18archimate architecture patterns
This skill should be used when the user asks about "ArchiMate patterns", "microservices in ArchiMate", "cloud architecture ArchiMate", "API gateway pattern", "event-driven architecture", "container architecture", "Kubernetes ArchiMate", "data architecture pattern", "security architecture", "capability mapping", "value stream", or needs to model modern architecture patterns in ArchiMate.
16jarchi scripting
This skill should be used when the user asks to "create a jArchi script", "write an Archi script", "automate ArchiMate", "export from Archi", "query ArchiMate elements", "create ArchiMate views", "run Archi headlessly", "Archi CLI", "batch process ArchiMate model", or mentions "jArchi", ".ajs script", "Archi automation", or ArchiMate scripting. Provides comprehensive jArchi API knowledge and CLI automation support.
13augment-plan
>
2