TOGAF® Standard, 10th Edition · OGEA-101 Foundation · Quick revision
Architecture Partition
Official definition — learn word for word
“A subset of architecture resulting from dividing that architecture to facilitate its development and management.”
Partitions are used to simplify the development and management of the EA. They lie at the foundation of Architecture Governance and are distinct from levels and the organizing concepts of the Architecture Continuum (APPLY §4.1).
Source: CC §4.18 · APPLY §4.1
Memory aid
Partition = WHO owns which piece. Level = how DETAILED. Continuum = how GENERIC.
Memory aid — not TOGAF wording.
In plain words
Cutting a big architecture into pieces that different teams can own and govern separately.
Plain-English summary — not TOGAF wording.
Worked example
DUK partitions its architecture into Admissions, Finance and Academics, each owned by a team of architects with its own governance — so the Finance team can move on payments without waiting for Academics.
Illustrative example (Digital University Kerala) — not from the Standard.
01Mind map — related concepts
Architecture Partition
WHY
Conflicts · parallel teams · re-use
CRITERIA
Subject matter · time · maturity · depth
SET UP IN
Preliminary — boundaries, governance, ownership
FOUNDATION OF
Architecture Governance
NO DEFINITIVE MODEL
Each enterprise fits its own operating model
NOT TO CONFUSE WITH
Levels or the Architecture Continuum
Source: APPLY §4.1–4.2.1 · CC §4.16, §4.18
02Partition vs Level vs Continuum
| Concept | Divides by | Source |
|---|---|---|
| Architecture Partition | Subsets to facilitate development and management (ownership) | CC §4.18 · APPLY §4.1 |
| Architecture Level | Granularity — Strategic, Segment, Capability | CC §4.16 |
| Architecture Continuum | Abstraction — generic to organization-specific | CC §4.10 |
Source: CC §4.10, §4.16, §4.18 · APPLY §4.1
03Why architectures are partitioned (APPLY §4.1)
Organizational unit architectures conflictwith one another
Teams work in parallelspecific groups own and develop specific elements
Effective re-useneeds modular architecture segments
Source: APPLY §4.1
04Where it appears in the ADM
Preliminary Phase
Establishing the Architecture Capability requires a number of architecture partitions, with defined boundaries, governance, and ownership.
APPLY §4.2.1
05Exam traps
“Partitions and levels are the same” → They are distinct (levels = granularity)
“TOGAF provides a definitive partitioning model” → Impractical — each enterprise adopts one that reflects its operating model
“Partitions are created in Phase E” → Established in the Preliminary Phase
“Partitions have nothing to do with governance” → They lie at the foundation of Architecture Governance
06Self-test — tap to reveal
Q1Define an architecture partition.
A subset of architecture resulting from dividing that architecture to facilitate its development and management.
Q2Give the three reasons to partition.
Conflicting unit architectures; parallel team work; effective re-use.
Q3Name the solution-partitioning criteria.
Subject matter (breadth), time, maturity/volatility.
Q4Which extra criterion is used for architecture partitioning?
Depth.
Q5Where are partitions established?
The Preliminary Phase.
Q6What do partitions lie at the foundation of?
Architecture Governance.
Q7Does TOGAF give a definitive partitioning model?
No.
Q8What do levels divide the landscape by?
Granularity.