← Dashboard
T20Scenario-Heavy

Applying the ADM — Iteration, Levels & Partitioning

TOGAF Applying the ADM — The Open Group↗
Iteration, levels of architecture, and partitioning
TOGAF Architecture Partitioning↗
Why and how to partition the architecture
4 Cycles
ADM iteration groups
3 Levels
Strategic · Segment · Capability
Not Linear
ADM is iterative
Partition
To manage complexity
💡 The Big Idea

The ADM is a method to be adapted, not a fixed script. You apply it iteratively (four iteration cycles), at three levels of granularity (Strategic, Segment, Capability), and you partition the architecture into manageable pieces.

The circular ADM diagram is a hint: you go around it, and around parts of it, many times.

  • ▸🔄 You iterate around the whole ADM, between phases, and within a phase
  • ▸📈 Each iteration can add detail, widen scope, or respond to change
  • ▸🧭 TOGAF groups the phases into FOUR iteration cycles (see the explorer)
  • ▸⚠️ "The ADM must be executed strictly A → B → C → … → H once" is FALSE

Explore the four iteration cycles, the three levels of architecture, and how architecture partitioning works.

The ADM is not strictly sequential. TOGAF groups the phases into four iteration cycles that you repeat as needed. Iteration lets you deepen detail, react to change, and manage scope.

Architecture Capability iterationPreliminary + A▾

Establishes or changes the architecture capability itself — the practice, governance, and framework tailoring.

Architecture Development iterationB · C · D (+ A)▾

Creates or changes architecture content by cycling through the Business, Information Systems (Data + Application) and Technology Architecture phases until they are consistent — framed by the Vision from Phase A.

Transition Planning iterationE · F▾

Produces and updates the Architecture Roadmap and the Implementation & Migration Plan — the "how do we get there" work.

Architecture Governance iterationG · H▾

Governs implementation and manages change — feeding lessons and change requests back into the architecture.

TOGAF describes applying iteration to the ADM as four cycles:

Sequence:B→D→A→T"Big Dogs Always Triumph"

The same ADM is used at three levels of granularity, each nested within the one above:

  • ▸🌍 Strategic Architecture — long-term, enterprise-wide, low detail, direction-setting
  • ▸🧩 Segment Architecture — detailed, for one business segment, within the strategic framework
  • ▸🔧 Capability Architecture — detailed, for one capability increment, feeding implementation projects
  • ▸💡 These are also the three levels at which the Architecture Landscape is held

Partitioning splits the architecture into pieces that can be developed and governed independently.

  • ▸📐 Partition along dimensions: breadth (subject matter), depth (level of detail), time (period), and maturity
  • ▸🎯 Reasons: manage complexity, avoid conflicting requirements, let teams work in parallel, enable reuse, align with governance
  • ▸🗂️ Partitions are classified (often by Strategic/Segment/Capability, and by domain) and stored in the Architecture Landscape
  • ▸⚠️ Partitioning is an organizing technique — it does not change WHAT the ADM does, only how the work is divided
← T19T21 →