Product Guide
Capability Map
Connect business outcomes to the architecture elements that realize them
The Capability Map explains what the business needs the architecture to support. Open Model → Capability Map.
Map And Catalog
| Mode | Use it for |
|---|---|
| Map | Arrange capabilities and inspect composition visually |
| Catalog | Search, compare, and review capabilities and realizations systematically |
The workbench includes read/edit mode, auto-layout, save-state feedback, palette, and inspector.
Capability Structure
- Name capabilities in business language.
- Explain the outcome rather than its implementation.
- Use composition to decompose broad capabilities.
- Use realization links to connect capabilities to Systems, Containers, Components, or Blocks.
- Record ownership, responsibility, or implementation gaps in notes.
A capability can have several realizers or none. Missing realizations are valuable evidence; they show where the architecture has not explained delivery responsibility.
Review Questions
- Which important capability lacks a realization?
- Which capability is spread across too many ownership boundaries?
- Which architecture element supports unrelated capabilities?
- Does the hierarchy reflect business decomposition rather than an org chart?
- Which gap should drive a Workflow, View, Decision, or Architecture Simulation?
Capability Maps are versioned, available to Archie and MCP, and can be included in Architecture Documents and publications.