Goal: enterprise architecture
Reader: Enterprise architects aligning capabilities with IT. Meta cluster: C — infrastructure & governance Scenarios: 3 · Examples: 3
Scenarios
| Scenario | Tier | Engines | Example files |
|---|---|---|---|
| archimate layered model | T2 | plantuml | archimate-layered-model.md |
| capability map | T2 | plantuml | capability-map.md |
| stakeholder map | T2 | infographic | stakeholder-circle-wheel.md |
Reading order
ArchiMate layering for the full model, capability maps for the business view, stakeholder maps for the political view.
Engines in this goal
infographic— template-driven boards, sequences and comparisonsplantuml— diagrams with icon families and UML/ArchiMate/BPMN semantics
Details, limits and anti-patterns: ../engines/infographic.md · ../engines/plantuml.md.
Palette
Every figure takes its colours from a theme. Pick one in
../styles/palette.md — the token contract, the theme index and the
per-engine blocks all start there.
Most figures in this set want Default. Depart from it for the medium, not the topic: Print when it may be photocopied, Contrast for low vision or large-print handouts, Vivid when it will be projected, Accessible when colour must not be the only cue, Editorial for long-form reading, Slate for technical reference, Pastel when the figure sits inside gentle prose, Nord for a cool Nordic register. Every theme is designed for a light ground — the set has no dark page.
Don't
- ArchiMate elements used as decoration rather than with layer semantics
- Capability maps with no maturity or ownership dimension