Overview
Introduction to the ADM taught the phases. This unit is about using them in a real enterprise, where one ADM cycle is never enough. You learn where the TOGAF Standard provides guidance on applying the method: the Applying the ADM part of the Fundamental Content and the TOGAF Series Guides. You also learn how iteration lets several phases and several ADM cycles operate at the same time.
Two structures keep this manageable. The Architecture Landscape divides architecture by level of detail into Strategic, Segment and Capability Architectures, and partitioning divides the enterprise into parts that different teams can work on without collisions. The four purposes of architecture work (to support strategy, portfolio, project and solution delivery) frame each effort's planning horizon, breadth and depth. The unit ends with how the TOGAF Standard can be applied to support the Digital enterprise, where change is continuous and fast.
How it's tested
Questions here are mostly recall of short lists and simple application: name the three Architecture Landscape levels, pick the purpose that fits a described effort, or choose the statement that explains why partitioning or iteration helps. Distractors are typically items from other TOGAF lists that sound similar.
-
Level identification
A described architecture (enterprise-wide direction over several years, or detail for one capability) is matched to Strategic, Segment or Capability Architecture.
-
Purpose of the effort
A scenario describes an architecture effort and you choose whether it supports strategy, portfolio, project or solution delivery, which in turn sets its horizon and detail.
-
Why it helps
A 'why' question about partitioning, iteration or Series Guides, where the right answer explains the benefit (manageable scope, parallel work, practical guidance) and distractors overstate or misstate it.
A stem describes an architecture covering one line of business, such as retail lending, over the next two years, used to steer a programme of related projects. Which Architecture Landscape level is this? Strategic is tempting because it guides several projects, but strategic architecture covers the whole enterprise over a long horizon. A single line of business with programme-level guidance is a Segment Architecture.
Learning outcomes 6
Official learning outcomes from the The Open Group outline, in outline order.
5.1 Describe where guidance on applying the TOGAF Standard is providedThe Applying the ADM document and the TOGAF Series Guides.
- What it means
- The 10th Edition splits the standard into Fundamental Content and TOGAF Series Guides. Guidance on using the ADM in practice is found in the Applying the ADM part of the Fundamental Content and in Series Guides that address specific contexts.
- What to understand
- Fundamental Content changes rarely and holds the core method and concepts. Series Guides are updated more often and give practical, situation-specific guidance, such as using the ADM with Agile delivery, establishing an Architecture Capability or digital topics.
- How it shows up
- A stem asks where an architect would look for practical guidance on applying the ADM in a particular context: the TOGAF Series Guides (and the Applying the ADM document).
- Common confusion
- Thinking all guidance sits in one monolithic document, as in older editions.
5.2 Explain how iteration enables concurrent operation of multiple ADM phasesSeveral phases and cycles running at once.
- What it means
- Because the ADM is iterative, different phases and different ADM cycles can run at the same time. One team can be governing implementation of a Transition Architecture in Phase G while another develops the next target in Phases B to D.
- What to understand
- Concurrency is managed through the Architecture Landscape levels and partitioning: higher-level cycles set direction for lower-level ones, and the iteration cycles (capability, development, transition planning, governance) can overlap.
- How it shows up
- A stem asks how the ADM handles governing current change while planning the next; iteration allows those phases to run concurrently.
- Common confusion
- Believing a new ADM cycle cannot start until the previous one has finished Phase H.
5.3 List the three levels of the Architecture LandscapeStrategic, Segment and Capability Architecture.
- What it means
- The Architecture Landscape is divided into three levels of granularity: Strategic Architecture (an organizing framework for the whole enterprise over a long horizon), Segment Architecture (a more detailed view of an area such as a line of business, often for programmes or portfolios) and Capability Architecture (a detailed description of how the enterprise can support a particular capability).
- What to understand
- Each level provides context and constraints for the one below it. The levels are about scope and detail, not about how generic an asset is, which is what the Enterprise Continuum measures.
- How it shows up
- A stem asks which list correctly names the Architecture Landscape levels.
- Common confusion
- Answering with Foundation, Common Systems, Industry and Organization-Specific, which are Enterprise Continuum levels.
5.4 Explain how partitioning simplifies EA developmentDivide the enterprise into parts teams can manage separately.
- What it means
- Partitioning divides the Enterprise Architecture into smaller, manageable pieces that can be developed by different teams, at different times and at different levels of detail. Partitions can be based on subject matter, time and maturity or volatility.
- What to understand
- Partitioning avoids overlapping work and conflicting architectures, supports reuse and lets different architectures be governed separately while staying consistent. How the enterprise will be partitioned is decided as part of establishing the Architecture Capability.
- How it shows up
- A stem asks the main benefit of partitioning; the answer is that it makes development and management of the architecture manageable by dividing it among teams without conflict.
- Common confusion
- Thinking partitioning means creating separate, unrelated architectures with no overall coherence.
5.5 List the four purposes that frame the planning horizon, breadth and depthStrategy, portfolio, project, solution delivery.
- What it means
- The TOGAF Standard identifies four purposes of architecture work: to support strategy, to support portfolio, to support project and to support solution delivery. The purpose sets how far ahead the architecture looks and how broad and deep it goes.
- What to understand
- Strategy-level work is broad, shallow and long-horizon; solution-delivery work is narrow, detailed and short-horizon. Portfolio and project sit between. Choosing the right purpose avoids over- or under-engineering the architecture.
- How it shows up
- A stem describes architecture produced to help select and sequence a set of initiatives over the next couple of years, and asks which purpose it serves: portfolio.
- Common confusion
- Mixing these with the four scoping dimensions (breadth, depth, time period, domains).
5.6 Explain how the TOGAF Standard supports the Digital enterpriseFast, continuous change supported by iteration, levels and Series Guides.
- What it means
- A Digital enterprise changes quickly and continuously, often driven by customer experience and new business models. The TOGAF Standard supports it through a modular structure, iterative and Agile-friendly application of the ADM, architecture at the right level of detail, and Series Guides on digital topics.
- What to understand
- The key idea is that EA provides direction and guardrails while delivery moves fast: strategic and segment architecture keep change coherent, and capability and solution-level work is done incrementally.
- How it shows up
- A stem asks how EA adds value to a digital transformation; the answer centres on providing coherent direction and guardrails while allowing rapid, iterative delivery.
- Common confusion
- Believing EA slows digital change by insisting on complete designs before any delivery.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Architecture Landscape levels
Strategic Architecture covers the whole enterprise over a long horizon; Segment Architecture covers an area such as a line of business; Capability Architecture details how one capability is supported.
- Remember
- The order runs from broadest and longest-term to narrowest and most detailed.
- Tested as
- Learning outcome 5.3 asks you to list them.
- Trap
- Answering with Enterprise Continuum levels.
-
Four purposes of architecture
Architecture to support strategy, portfolio, project and solution delivery, each with a different planning horizon, breadth and depth.
- Remember
- Strategy is broad and long-horizon; solution delivery is narrow and detailed.
- Tested as
- Learning outcome 5.5 asks you to list them.
- Trap
- Confusing them with the scoping dimensions.
-
Partitioning
Dividing the enterprise architecture into manageable parts, by subject matter, time or maturity and volatility, so teams can work in parallel without conflict.
- Remember
- Partitions must still fit together under the overall architecture.
- Tested as
- 'Why partition' questions.
- Trap
- Treating partitions as independent, unrelated architectures.
-
Concurrent ADM operation
Iteration lets different phases and different ADM cycles run at the same time, such as governing one transition while designing the next.
- Remember
- Higher-level cycles guide lower-level ones.
- Tested as
- Outcome 5.2.
- Trap
- Assuming cycles must run one after another.
-
Fundamental Content vs. Series Guides
Fundamental Content is the stable core of the 10th Edition; TOGAF Series Guides give practical, context-specific guidance and change more often.
- Remember
- Guidance on applying the ADM is in the Applying the ADM document and the Series Guides.
- Tested as
- Outcome 5.1.
- Trap
- Thinking Series Guides replace or override the Fundamental Content.
-
Segment Architecture
A detailed formal description of an area of the enterprise, used at programme or portfolio level to organize and align change.
- Remember
- It sits between Strategic and Capability Architecture.
- Tested as
- The most commonly misplaced landscape level.
- Trap
- Calling any multi-project architecture strategic.
-
Capability Architecture
A highly detailed description of how the enterprise can support a particular capability, often used to guide a specific change effort.
- Remember
- It is the most detailed landscape level.
- Tested as
- Level identification questions.
- Trap
- Confusing it with the Architecture Capability, the ability to do EA.
-
Digital enterprise support
TOGAF supports digital change through iterative, Agile-compatible application, architecture at multiple levels and digital Series Guides.
- Remember
- EA provides direction and guardrails while delivery stays fast.
- Tested as
- Outcome 5.6.
- Trap
- Assuming EA requires complete designs before delivery begins.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Architecture Landscape levels vs. Enterprise Continuum levels
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Architecture Landscape (Strategic, Segment, Capability) | Levels of scope and detail for the enterprise's own architectures | Measures breadth and granularity | Listing Foundation or Industry as a landscape level |
| Enterprise Continuum (Foundation, Common Systems, Industry, Organization-Specific) | Classification of assets from generic to specific | Measures how generic or reusable an asset is | Listing Segment or Capability as a continuum level |
Four purposes vs. four scoping dimensions
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Purposes (strategy, portfolio, project, solution delivery) | Why the architecture is being developed | Sets the planning horizon and the right breadth and depth | Listing time period or domains as a purpose |
| Scoping dimensions (breadth, depth, time period, architecture domains) | How much the architecture covers | Bounds the effort once its purpose is known | Listing portfolio or project as a dimension |
Capability Architecture vs. Architecture Capability
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Capability Architecture | Detailed architecture for how one business capability is supported | A level of the Architecture Landscape | Thinking it describes the EA team |
| Architecture Capability | The organization's ability to develop, use and sustain EA | Established in the Preliminary Phase | Placing it in the Architecture Landscape |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Continuum levels as landscape levels
- What candidates pick
- Foundation, Common Systems and Industry as the Architecture Landscape levels.
- Why it looks right
- Both are layered lists of architectures in the TOGAF Standard.
- Why it's wrong
- The landscape has three levels of scope and detail: Strategic, Segment and Capability.
Clue to watch for 'Architecture Landscape' and 'three levels' point to Strategic, Segment, Capability; 'continuum' points to the four-level generic-to-specific list.
-
Strategic for any multi-project work
- What candidates pick
- Strategic Architecture for an architecture covering one line of business and several projects.
- Why it looks right
- Guiding several projects feels strategic.
- Why it's wrong
- Strategic Architecture covers the whole enterprise; an area of the enterprise guiding a programme is Segment Architecture.
Clue to watch for Check the breadth: whole enterprise means strategic, one area means segment.
-
Purposes versus dimensions
- What candidates pick
- 'Time period' as one of the four purposes of architecture.
- Why it looks right
- The purposes do frame the planning horizon.
- Why it's wrong
- Time period is a scoping dimension; the purposes are strategy, portfolio, project and solution delivery.
Clue to watch for If the options mix nouns like 'portfolio' with 'depth', the question is testing which list you know.
-
Partitions as separate architectures
- What candidates pick
- An answer saying partitioning lets each business unit build its own unrelated architecture.
- Why it looks right
- Independence sounds efficient.
- Why it's wrong
- Partitioning divides the work so it is manageable, but partitions must remain consistent and integrate under the overall EA.
Clue to watch for Look for options that keep coherence across partitions.
-
Sequential cycles only
- What candidates pick
- A statement that a new ADM cycle may start only after the previous one completes.
- Why it looks right
- Diagrams show one cycle at a time.
- Why it's wrong
- Iteration allows multiple phases and cycles to run concurrently at different levels.
Clue to watch for Words such as 'only after' or 'must complete' about cycles signal the distractor.
Answer framework
Use these steps when a question asks how the ADM should be applied to a described situation.
- Decide the breadth of the described architecture: the whole enterprise, one area, or a single capability or solution.
- Map breadth to a landscape level: whole enterprise is Strategic, one area is Segment, one capability is Capability Architecture.
- Identify the purpose of the work, whether strategy, portfolio, project or solution delivery, which tells you the horizon and level of detail.
- If several teams or efforts are involved, consider partitioning and concurrent ADM cycles rather than one large sequential effort.
- Check each option against the right TOGAF list, rejecting continuum levels, scoping dimensions and other look-alike terms that belong to a different structure.
Practice question
Want more like this? The TOGAF EA Foundation practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
This is a compact unit, so learn it as a set of lists and one or two ideas behind them. Start with the 10th Edition structure: Fundamental Content for the stable core and TOGAF Series Guides for practical guidance. That answers outcome 5.1 and makes the rest easier to place.
Next, learn the three Architecture Landscape levels and the four purposes side by side, and write them next to the lists they are most often confused with: the Enterprise Continuum levels and the four scoping dimensions. Seeing the look-alike lists together is the most effective way to avoid the common traps.
The area most often underestimated is iteration and concurrency. Picture two ADM cycles drawn at different sizes, a large strategic one and a smaller segment one inside it, and imagine Phase G running for one transition while Phases B to D run for the next. That picture explains outcome 5.2 and partitioning at the same time.
Finish with the Digital enterprise outcome, which is conceptual: EA gives direction and guardrails while delivery moves quickly. Then practise level and purpose identification questions until you can answer each in well under a minute.
FAQ
How many questions are there on Applying the ADM?
The official OGEA-101 exam plan allocates 4 of the 40 questions to this unit, which is 10% of the paper.
What are the three levels of the Architecture Landscape?
Strategic Architecture, Segment Architecture and Capability Architecture, running from enterprise-wide and long-horizon to detailed and focused on one capability.
What are the four purposes of architecture work?
Architecture to support strategy, to support portfolio, to support project and to support solution delivery. The purpose frames the planning horizon and how broad and deep the architecture should be.
Why partition an Enterprise Architecture?
To divide a large architecture into manageable parts that different teams can develop and govern in parallel, while keeping them consistent with the overall architecture.
Where do I find guidance on applying TOGAF in specific situations?
In the Applying the ADM part of the Fundamental Content and in the TOGAF Series Guides, which give practical guidance for particular contexts.
Does the TOGAF Standard work for digital and Agile organizations?
Yes. The ADM can be applied iteratively and at different levels of detail, so architecture gives direction and guardrails while delivery proceeds in short increments.
How much study time does this unit need?
As a planning estimate, about 3 to 5 hours of a 40-hour plan, mainly spent separating the landscape levels and purposes from look-alike lists.
Other Enterprise Architecture & IT Governance certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 4 knowledge
You have just separated the Architecture Landscape levels, the four purposes and partitioning from their look-alike lists. Check that you can place a described architecture at the right level in a few seconds.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the TOGAF EA Foundation AI tutor Get any concept explained your way