Key takeaways
- Levels identify scale rather than a mandatory sequence of phases.
- Partitioning supports parallel work and requires coordination.
- A local architecture should respect constraints from its wider context.
Three scales of description
Strategic Architecture provides a high-level view for executive decisions and longer-term direction. Segment Architecture describes part of the enterprise in more detail to organize a portfolio or program of change. Capability Architecture focuses on a capability and the concrete increments needed for its evolution.
These levels connect strategy with realization. A broad direction towards accessible services may be developed within a citizen-service segment and then within a request-processing capability. The levels differ in scope and detail; they do not automatically correspond to the Business, Data, Application, and Technology domains.
Distribute work without fragmentation
Partitioning defines architecture boundaries so several teams can progress in parallel. It should consider the operating model, responsibilities, and dependencies. Shared rules, explicit interfaces, and governance mechanisms help resolve conflicts and support reuse. A portfolio boundary does not remove shared data or a technical dependency.
- Define the scope and authority of each partition.
- Maintain links between enterprise-wide and local decisions.
- Plan coordination for shared elements and dependencies.
TERMS TO KNOW
The terms, in context.
- Segment Architecture
- Detailed description of part of an enterprise associated with a program or portfolio.
- Partitioning
- Definition of coordinated architecture scopes.