TL;DR
TOGAF organizes the Architecture Landscape into three levels of granularity: Strategic, Segment, and Capability. They differ by breadth, depth, and time horizon.
Why architecture levels exist
At any point in time, a typical enterprise has many architectures:
- some are big-picture and executive-facing
- some are program or portfolio-focused
- some are detailed and delivery-focused
Architecture levels help organize this complexity.
The 3 levels in TOGAF
| Level | Main purpose | Breadth | Depth | Time horizon |
|---|---|---|---|---|
| Strategic Architecture | Direction setting and enterprise-wide change context | broad (enterprise-wide) | low | long |
| Segment Architecture | Program/portfolio direction and roadmap planning | medium (part of enterprise) | medium | medium |
| Capability Architecture | Detailed change design for a specific capability or initiative | narrow (small scope) | high | short |
flowchart TD S["Strategic Architecture<br/>Broad scope, low detail, long horizon"] G1["Segment Architecture A<br/>Medium scope and detail"] G2["Segment Architecture B<br/>Medium scope and detail"] C1["Capability Architecture 1<br/>Narrow scope, high detail"] C2["Capability Architecture 2<br/>Narrow scope, high detail"] C3["Capability Architecture 3<br/>Narrow scope, high detail"] C4["Capability Architecture 4<br/>Narrow scope, high detail"] S -.->|provides context for| G1 S -.->|provides context for| G2 G1 -.->|elaborates into| C1 G1 -.->|elaborates into| C2 G2 -.->|elaborates into| C3 S -.->|can also contextually guide| C4 C1 -.->|informs| G1 C2 -.->|informs| G1 C3 -.->|informs| G2 G1 -.->|informs| S G2 -.->|informs| S
1) Strategic Architecture
Strategic Architecture gives executives a direction-setting view.
It usually:
- covers the enterprise at large scope
- stays at lower detail
- looks further into the future
This level defines the guardrails and strategic intent for lower levels.
2) Segment Architecture
Segment Architecture translates strategic direction into a specific area (for example, a business unit, program, or portfolio).
It balances direction and implementation:
- more focused than strategic level
- more detailed than strategic level
- still broad enough to coordinate multiple initiatives
3) Capability Architecture
Capability Architecture is the most detailed level.
It usually:
- covers a narrow scope (single capability, process, or department)
- supports concrete change increments
- has a shorter planning horizon
This is often the level closest to delivery and implementation planning.
How the levels fit together
The levels are connected, not isolated.
- multiple Segment Architectures can detail one Strategic Architecture
- multiple Capability Architectures can detail one Segment Architecture
So the lower level increases detail, while the higher level keeps enterprise-wide coherence.
Practical interpretation
If your question is “Where should the enterprise go?”, you are likely at Strategic level.
If your question is “How should this portfolio evolve?”, you are likely at Segment level.
If your question is “How do we implement this specific change?”, you are likely at Capability level.
Exam note
- TOGAF Architecture Landscape uses three levels: Strategic, Segment, Capability.
- The same architecture topic can appear at different levels with different detail.
- Strategic is broad/long-term; Capability is narrow/short-term; Segment sits in between.
- Levels are recursive and connected through elaboration and feedback traceability.