10 templates
ArchiMate templates
ArchiMate 3.2 enterprise architecture: business, application, technology, motivation, strategy and migration layers, with all eleven relationships drawn to the specification's own line styles and end decorations. The layer is derived from the element type rather than declared beside it, so the band and the colour cannot disagree.
ArchiMate — Order to Cash, Three Layers
The canonical layered view: a business process served by application services, realized by components, deployed on nodes. Every line is the specific ArchiMate relationship rather than a generic arrow — a component realizes its service and serves the process, which are two different claims that most drawings collapse into one.
ArchitectureArchiMate — Motivation: Drivers, Goals and Requirements
Why the architecture is being changed at all, in the layer most models skip. Stakeholders hold drivers, drivers influence goals, goals are realized by requirements, and requirements are realized by the things the other layers build — the only chain that connects a piece of software back to a reason for it.
ArchitectureArchiMate — Application Cooperation and Data Flow
How five applications actually depend on one another, drawn with flow for what moves and serving for what is used. The distinction is the point: a flow says data travels, a serving says one component needs another to work, and a landscape that draws both as one arrow cannot answer either question.
ArchitectureArchiMate — Technology Deployment, Composition vs Aggregation
A deployment view that keeps the two diamonds apart. A node is COMPOSED OF the parts that cannot exist without it (filled diamond) and AGGREGATES the things it merely collects (hollow diamond) — one attribute apart, the pair most often collapsed, and the collapse changes what the model says about lifecycle and ownership.
ArchitectureArchiMate — Business Process with Roles and Events
A business layer view on its own, where the trap is drawing the process chain with the wrong relationship. Triggering is what makes one process follow another; assignment is what puts a role on a process; access is what a process does to an object. Three different lines because they are three different facts, and only triggering carries sequence.
Business & StrategyArchiMate — Strategy: Capabilities and Courses of Action
The strategy layer, which exists so a capability map is connected to something rather than floating as a slide. Resources are assigned to capabilities, capabilities realize courses of action, and the courses of action are what the rest of the model is eventually built to deliver.
Business & StrategyArchiMate — Migration: Plateaus, Gaps and Work Packages
The implementation and migration layer, which answers the question a landscape diagram cannot: what changes between here and there, and in what order. Plateaus are the stable states, a gap names the difference between two of them, and work packages deliver the things that close it.
Project & PlanningArchiMate — One Service, All the Way Down
A single vertical slice from a customer-facing service to the artifact that implements it, which is the view that answers 'what breaks if this server goes down'. Every layer boundary is crossed by realization going up and serving going across, which is the ArchiMate pattern worth learning first.
ArchitectureArchiMate — Specialization and Generic Types
A reference model where the interesting line is specialization — the solid hollow triangle that says one element is a kind of another, and which shares its arrowhead with realization and differs only in whether the line is dashed. Collapsing the two makes the model claim that a subtype implements its supertype, which is a different statement entirely.
ArchitectureArchiMate — Grouping and Location Across Two Regions
Where things run, which is a compliance question before it is an architecture one. Location and grouping are the two elements that belong to no layer, and this model uses them to say which components sit in which jurisdiction and what crosses between them.
Architecture