TOGAF EA Foundation · Domain 2 of 6

TOGAF EA Foundation Domain 2: Introduction to the ADM

The largest unit on OGEA-101. You must know the purpose and objectives of the Preliminary Phase, Phases A to H and Requirements Management, how the ADM iterates, how to scope an architecture, and what flows from phase to phase.

Exam weight
35%
Official learning outcomes
26
Estimated questions estimate
14
Suggested study time estimate
12–16 hrs

About 26 min read Reviewed October 2026

Overview

The Architecture Development Method (ADM) is the core of the TOGAF Standard: a cycle of phases that takes an enterprise from establishing its architecture capability, through vision and target architectures for each domain, to planning, governing and changing the result. This unit asks you to describe the cycle, explain why it is iterative, scope an effort, weigh architecture alternatives and say why architecture work itself must be governed.

Most of the 26 learning outcomes come in pairs: the purpose of a phase and its objectives. Preliminary sets up the capability; A sets the vision and gets approval; B, C and D develop the Business, Data, Application and Technology Architectures; E identifies opportunities and Transition Architectures; F finalizes the migration plan; G governs implementation; H manages change; Requirements Management feeds every phase. The unit ends with the flow of deliverables between phases and how the ADM supports Agile delivery.

How it's tested

Questions in this unit describe an activity, objective or output and ask which phase it belongs to, or name a phase and ask for its objective. Some ask which statement about iteration, scoping or Requirements Management is correct. Answers depend on precise phase objectives, not on general project-management logic.

  • Which phase

    A stem describes an activity such as confirming whether Transition Architectures are needed, and you name the phase. The distractors are usually the phases just before and after it.

  • Objective of a phase

    A phase is named and four objectives are offered, three of which belong to neighbouring phases. Knowing one signature objective per phase eliminates them quickly.

  • True statement about the ADM

    Statements about iteration, scoping, Requirements Management or draft versus approved deliverables, where one detail is wrong in each distractor, such as 'Requirements Management prioritizes requirements'.

Reasoning it through

A stem says an architecture team is establishing the Architecture Board, defining Architecture Principles and selecting a modeling tool before any specific project begins. Which phase? Phase A is tempting because principles are also reviewed there. But setting up the organizational model, governance and tools is about building the Architecture Capability, which is the Preliminary Phase. Phase A starts once a Request for Architecture Work arrives for a specific effort.

Learning outcomes 26

Official learning outcomes from the The Open Group outline, in outline order.

3.1 Briefly describe the ADM and its phasesThe ADM cycle: Preliminary, A to H, Requirements Management at the centre.
What it means
The ADM is a tested, repeatable method for developing and managing an Enterprise Architecture. Its phases are Preliminary, A Architecture Vision, B Business Architecture, C Information Systems Architectures, D Technology Architecture, E Opportunities and Solutions, F Migration Planning, G Implementation Governance and H Architecture Change Management, with Requirements Management linked to all of them.
What to understand
Know the order and the one-line job of each phase. Requirements Management is a continuous process at the centre, not a phase in the sequence, and the method is meant to be adapted to the organization.
How it shows up
A stem lists phases out of order, or names the phase between C and E, and asks which one fits: Phase D, Technology Architecture.
Common confusion
Treating Requirements Management as a step that happens once between two phases.
3.2 Describe the difference between draft and approved deliverablesDeliverables evolve through versions until formally approved.
What it means
Many deliverables are created in draft in one phase and refined in later phases before they are approved. The ADM uses version numbers to show this, with 0.x versions as drafts and version 1.0 or higher indicating an approved output.
What to understand
A draft can still change and is used as working input; an approved deliverable has been reviewed and signed off by the relevant stakeholders and is then under change control. For example, the Architecture Definition Document starts as a draft in Phase A and is approved by the end of Phase D.
How it shows up
A stem asks which statement is true of an approved deliverable: it has been formally reviewed and signed off, so later changes go through change management.
Common confusion
Assuming a deliverable is complete as soon as a phase that touches it ends.
3.3 Explain the iterative approach of the ADMIterate within phases, between phases and across whole cycles.
What it means
The ADM is iterative: across the whole cycle, between phases and within each phase. The TOGAF Standard groups the iteration cycles as Architecture Capability (Preliminary and A), Architecture Development (B, C and D), Transition Planning (E and F) and Architecture Governance (G and H).
What to understand
Each iteration decides breadth, depth and how much detail is enough before moving on. Teams may also choose baseline-first or target-first development within B, C and D, and new ADM cycles can be triggered by Phase H.
How it shows up
A stem asks which phases are grouped in the Transition Planning iteration: E and F.
Common confusion
Believing the ADM must be run strictly in sequence, once, from Preliminary to H.
3.4 Explain the need to govern the creation, development and maintenance of EAArchitecture work itself needs governance, not only the projects it guides.
What it means
Architecture is an enterprise asset that must be managed. Governance ensures that architecture work is done to an agreed standard, that decisions are visible and accountable, and that the resulting architecture is maintained and used.
What to understand
Without governance, architectures drift from strategy, stakeholders lose trust, and projects ignore them. Governance is set up in the Preliminary Phase, exercised throughout the cycle with stakeholder review and sign-off, and is most visible in Phases G and H through compliance and change management.
How it shows up
A stem asks why the creation and maintenance of EA should be governed; the right answer refers to ensuring architectures stay aligned, compliant and fit for purpose over time.
Common confusion
Thinking governance applies only to implementation projects, not to the architecture function itself.
3.5 Briefly explain how to scope an architectureBreadth, depth, time period and architecture domains.
What it means
Scoping decides how much of the enterprise and how much detail an architecture effort covers. The TOGAF Standard describes four dimensions: breadth, depth, time period and architecture domains.
What to understand
Breadth is how much of the enterprise is in scope; depth is the level of detail; time period is the horizon the architecture covers; architecture domains says which of Business, Data, Application and Technology are included. Scoping is driven by stakeholder concerns, resources and the purpose of the work.
How it shows up
A stem lists four candidate scoping dimensions with one wrong item, such as 'budget' or 'number of projects'.
Common confusion
Confusing the time period of the architecture with the duration of the project that produces it.
3.6 Explain reasons for considering architecture alternatives, including concerns and trade-offSeveral options, weighed against stakeholder concerns.
What it means
Architects should develop and assess alternative architectures rather than settle on the first idea. Different stakeholders hold different concerns, such as cost, speed, risk or flexibility, and alternatives make the trade-offs visible.
What to understand
The aim is an informed choice: alternatives are evaluated, trade-offs are explained, and stakeholders agree a direction, which may combine elements of several options. This is part of developing the target in Phases B to D and continues in Phase E.
How it shows up
A stem asks why an architect presents more than one target option; the answer is that stakeholders' differing concerns must be balanced through explicit trade-offs.
Common confusion
Treating alternatives as wasted effort, or assuming the architect alone chooses the technically best option.
3.7 Briefly explain the purpose of the Preliminary Phase in developing an EA CapabilityPrepare the organization to do architecture.
What it means
The Preliminary Phase prepares the organization to undertake successful Enterprise Architecture. It defines where, what, why, who and how architecture will be done, and establishes the Architecture Capability.
What to understand
It is about the architecture practice, not any single project: the organizational model for EA, governance, principles, tailoring of the TOGAF Standard, tools and the repository. It is revisited when the capability needs to change.
How it shows up
A stem describes defining the organizational model for EA and tailoring the framework, and asks which phase this is.
Common confusion
Thinking the Preliminary Phase produces a vision for a specific change; that is Phase A.
3.8 Describe the objectives of the Preliminary PhaseDetermine, then establish, the Architecture Capability.
What it means
The objectives are to determine the Architecture Capability the organization wants and to establish it. Determining it includes reviewing the organizational context, identifying the parts of the enterprise affected, identifying existing frameworks and processes, and setting a capability maturity target.
What to understand
Establishing it includes defining the organizational model for EA, defining the governance processes and resources, selecting and implementing tools, and defining the Architecture Principles.
How it shows up
A stem offers 'define the Architecture Principles' among objectives of several phases; it belongs to the Preliminary Phase.
Common confusion
Selecting 'obtain approval for a Statement of Architecture Work', which is a Phase A objective.
3.9 Briefly explain the purpose of Phase ASet the vision and scope for one architecture effort.
What it means
Phase A, Architecture Vision, starts an ADM cycle for a specific piece of work. It sets the scope, identifies stakeholders and their concerns, confirms business goals and drivers, and creates a high-level picture of the target and the value it will bring.
What to understand
Phase A is triggered by a Request for Architecture Work. Its purpose is to secure agreement and sponsorship before detailed architecture work is funded.
How it shows up
A stem describes defining the scope of a new architecture effort and identifying its stakeholders after receiving a Request for Architecture Work.
Common confusion
Confusing Phase A with the Preliminary Phase because both deal with principles and direction.
3.10 Describe the objectives of Phase AHigh-level vision plus an approved Statement of Architecture Work.
What it means
Phase A has two objectives: to develop a high-level, aspirational vision of the capabilities and business value the proposed EA will deliver, and to obtain approval for a Statement of Architecture Work that defines the programme of work.
What to understand
The signed Statement of Architecture Work is the gate to Phases B to D. Phase A also produces the Architecture Vision, the Communications Plan and the Capability Assessment, and confirms principles, goals and drivers.
How it shows up
A stem asks which objective belongs to Phase A; 'obtain approval for a Statement of Architecture Work' is the signature answer.
Common confusion
Choosing 'develop the Target Business Architecture', which belongs to Phase B.
3.11 Briefly explain the purpose of Phases B, C and DDevelop baseline and target architectures for each domain.
What it means
Phases B, C and D develop the architecture for the domains in scope: Business (B), Data and Application (C) and Technology (D). Each describes the baseline and target, identifies gaps and proposes candidate roadmap components.
What to understand
They share a common step pattern: select reference models, viewpoints and tools; describe baseline and target; perform gap analysis; define candidate roadmap components; resolve impacts across the landscape; review with stakeholders; and update the Architecture Definition Document and Architecture Requirements Specification.
How it shows up
A stem asks in which phases gap analysis between baseline and target domain architectures is carried out: B, C and D.
Common confusion
Assuming B, C and D must always be done strictly one after another, rather than iterated together.
3.12 Describe the objectives of Phase BTarget Business Architecture and candidate roadmap components.
What it means
Phase B develops the Target Business Architecture that describes how the enterprise needs to operate to achieve its business goals and respond to the strategic drivers in the Architecture Vision. It also identifies candidate Architecture Roadmap components from the gaps between baseline and target.
What to understand
Business Architecture covers strategy, governance, organization, business capabilities, value streams and key processes. It usually comes first because the other domains exist to support it.
How it shows up
A stem describes defining how the organization must operate, its capabilities and processes, to meet the vision.
Common confusion
Thinking Phase B describes the applications that support the business; that is Phase C.
3.13 Describe the objectives of Phase C for Data and Application ArchitectureTarget Data and Application Architectures that enable the business.
What it means
For Data, Phase C develops the Target Data Architecture that enables the Business Architecture and the Architecture Vision. For Application, it develops the Target Application Architecture that does the same. Both identify candidate roadmap components from their gaps.
What to understand
Data and Application may be developed in either order or together; the TOGAF Standard calls them the Information Systems Architectures. Data covers major data types and sources; Application covers the major kinds of application system needed to process data and support the business.
How it shows up
A stem describes defining the major types of data and the applications that handle them in support of the target business.
Common confusion
Placing infrastructure platforms and networks in Phase C instead of Phase D.
3.14 Describe the objectives of Phase DTarget Technology Architecture enabling the application and data components.
What it means
Phase D develops the Target Technology Architecture that enables the logical and physical application and data components and the Architecture Vision, addressing the Request for Architecture Work and stakeholder concerns. It also identifies candidate roadmap components from the gaps.
What to understand
Technology Architecture describes the software and hardware capabilities, such as infrastructure, middleware, networks and platforms, needed to deploy business, data and application services.
How it shows up
A stem describes defining the platforms and infrastructure needed to host the target applications.
Common confusion
Thinking Phase D selects implementation projects; that work starts in Phase E.
3.15 Briefly explain the purpose of Phase ETurn the target architectures into a first roadmap and work packages.
What it means
Phase E, Opportunities and Solutions, is the first phase concerned with implementation. It consolidates the gaps from Phases B to D, groups changes into work packages and identifies the delivery vehicles, such as projects and programmes.
What to understand
It is where the architecture meets the realities of delivery: it checks readiness and risks, decides whether change should happen in increments, and produces the first complete version of the Architecture Roadmap.
How it shows up
A stem describes consolidating gap analysis results from all domains and grouping them into work packages.
Common confusion
Mixing Phase E with Phase F, which finalizes and costs the plan rather than identifying the opportunities.
3.16 Describe the objectives of Phase EInitial complete roadmap; decide on Transition Architectures.
What it means
Phase E generates the initial complete version of the Architecture Roadmap from the gap analysis and candidate components of Phases B to D. It also determines whether an incremental approach is needed and, if so, identifies Transition Architectures that deliver continuous business value.
What to understand
Transition Architectures are intermediate states between baseline and target; each should deliver value on its own. The Implementation and Migration Plan is started here and finished in Phase F.
How it shows up
A stem asks which phase determines whether Transition Architectures are required: Phase E.
Common confusion
Answering Phase F because Transition Architectures appear in the migration plan.
3.17 Briefly explain the purpose of Phase FFinalize how the change will be delivered and in what order.
What it means
Phase F, Migration Planning, works out how to move from baseline to target by finalizing a detailed Implementation and Migration Plan. It prioritizes work packages by business value, cost and risk, and coordinates the plan with the enterprise's wider change portfolio.
What to understand
Phase F turns the roadmap into a plan that can be funded and executed, and sets up the Implementation Governance Model that Phase G will use.
How it shows up
A stem describes assigning business value and cost to each work package and sequencing them into a funded plan.
Common confusion
Thinking Phase F performs implementation; it plans it, and Phase G governs it.
3.18 Describe the objectives of Phase FFinalized roadmap and plan, coordinated and understood by stakeholders.
What it means
Phase F finalizes the Architecture Roadmap and the supporting Implementation and Migration Plan, ensures the plan is coordinated with the enterprise's approach to managing and implementing change across its portfolio, and ensures that the business value and cost of work packages and Transition Architectures are understood by key stakeholders.
What to understand
The word 'finalize' is the clue for Phase F: E creates the initial roadmap, F completes it with costs, priorities and the governance model.
How it shows up
A stem asks which phase finalizes the Implementation and Migration Plan: Phase F.
Common confusion
Choosing Phase E for any roadmap-related objective without checking initial versus final.
3.19 Briefly explain the purpose of Phase GArchitectural oversight of implementation.
What it means
Phase G, Implementation Governance, provides architectural oversight of the projects that implement the target. It ensures implementation conforms to the architecture.
What to understand
Architecture Contracts are agreed with implementation partners, compliance reviews are carried out, and any deviations or change requests raised by implementation are handled through governance.
How it shows up
A stem describes performing compliance reviews of projects against the architecture and signing Architecture Contracts.
Common confusion
Thinking Phase G builds the solution; the projects build it, Phase G governs them.
3.20 Describe the objectives of Phase GConformance of implementation projects; governance of change requests.
What it means
Phase G ensures conformance with the Target Architecture by implementation projects, and performs the appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests.
What to understand
Its outputs include signed Architecture Contracts, Compliance Assessments, Change Requests and architecture-compliant solutions.
How it shows up
A stem asks which phase's objective is to ensure conformance with the Target Architecture by implementation projects: Phase G.
Common confusion
Choosing Phase H, which manages change to the architecture after deployment rather than conformance during implementation.
3.21 Briefly explain the purpose of Phase HKeep the architecture fit for purpose as things change.
What it means
Phase H, Architecture Change Management, monitors the business and technology environment and the deployed architecture, and manages changes so the architecture continues to meet the needs of the enterprise.
What to understand
Change is classified: simplification change can usually be handled by change management; incremental change may be handled by change management or partial re-architecting; re-architecting change needs a new ADM cycle, which Phase H starts with a new Request for Architecture Work.
How it shows up
A stem describes a change so significant that a new architecture cycle is needed, and asks which phase decides this.
Common confusion
Thinking every change requires a full new ADM cycle.
3.22 Describe the objectives of Phase HMaintain the lifecycle, execute governance, keep the capability fit.
What it means
Phase H ensures that the architecture lifecycle is maintained, that the Architecture Governance Framework is executed, and that the Enterprise Architecture Capability meets current requirements.
What to understand
Phase H closes the loop: it assesses the performance of the architecture, records lessons, and decides whether a change is handled locally or triggers a new cycle.
How it shows up
A stem asks which phase ensures the Enterprise Architecture Capability continues to meet current requirements.
Common confusion
Answering the Preliminary Phase, which establishes the capability; Phase H keeps it current.
3.23 Describe the objectives of the Requirements Management processSustain the process and make requirements available to every phase.
What it means
The objectives are to ensure the Requirements Management process is sustained and operates for all relevant ADM phases, to manage architecture requirements identified during any execution of the ADM cycle or a phase, and to ensure relevant requirements are available to each phase as it is executed.
What to understand
Requirements Management stores and manages the flow of requirements; it does not itself address, dispose of or prioritize them. That is done in the phase that deals with them.
How it shows up
A stem offers 'prioritize all architecture requirements' as an objective of Requirements Management; it is wrong.
Common confusion
Believing Requirements Management decides which requirements are implemented.
3.24 Describe the purpose of Requirements ManagementRequirements change, so they must be managed through the whole cycle.
What it means
The purpose of Requirements Management is to handle the dynamic nature of architecture requirements: they are identified, stored and fed into and out of the relevant ADM phases throughout the cycle.
What to understand
Requirements change constantly, and the process keeps them traceable and visible. Changes are assessed with a Requirements Impact Assessment, and requirements are recorded in the Architecture Requirements Specification and the Architecture Requirements Repository.
How it shows up
A stem asks why Requirements Management sits at the centre of the ADM: because requirements arise and change in every phase.
Common confusion
Thinking requirements are fixed after Phase A.
3.25 Explain the information flow between the ADM phasesWhich deliverables pass from phase to phase.
What it means
Each phase consumes and produces deliverables. A Request for Architecture Work starts the cycle; Phase A produces the Statement of Architecture Work and Architecture Vision; Phases B to D build the Architecture Definition Document and Architecture Requirements Specification; Phases E and F produce the Architecture Roadmap and the Implementation and Migration Plan; Phase G uses Architecture Contracts and Compliance Assessments; Phase H produces Change Requests and possibly a new Request for Architecture Work.
What to understand
Understanding the flow lets you answer 'which phase creates or uses this' without memorizing isolated lists. The Architecture Repository holds these outputs between phases.
How it shows up
A stem asks which deliverable is the main output of Phase A that authorizes the work in Phases B to D: the Statement of Architecture Work.
Common confusion
Thinking the Request for Architecture Work is produced in Phase A; it is the input that triggers it.
3.26 Explain how architecture for different purposes and levels of detail supports Agile developmentStrategic and portfolio architecture sets guardrails; solution architecture evolves in sprints.
What it means
The TOGAF Standard describes architecture to support strategy, portfolio, project and solution delivery. Higher-level architecture sets direction and constraints, while solution-level architecture can be developed just in time, alongside Agile teams.
What to understand
Agile teams need enough architecture to stay aligned without waiting for a full enterprise design. Iterating the ADM at the right level of detail, and in parallel with delivery, gives them that guidance.
How it shows up
A stem asks how an architecture team can support Agile delivery teams: by developing strategic and portfolio architecture as guardrails and detailing solution architecture iteratively.
Common confusion
Believing the ADM and Agile are incompatible because the ADM is a long, sequential process.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Phase order

    Preliminary, A Architecture Vision, B Business, C Information Systems, D Technology, E Opportunities and Solutions, F Migration Planning, G Implementation Governance, H Architecture Change Management, with Requirements Management at the centre.

    Remember
    Requirements Management is continuous and connects to every phase; it is not a step in the sequence.
    Tested as
    Every 'which phase' question depends on this order.
    Trap
    Placing Requirements Management between two phases.

  • Statement of Architecture Work

    The Phase A deliverable that defines the scope and approach of the architecture effort and is signed by the sponsor.

    Remember
    Its approval is a Phase A objective and the gate to Phases B to D.
    Tested as
    Signature answer for Phase A objective questions.
    Trap
    Confusing it with the Request for Architecture Work, which comes first from the sponsor.

  • Phase E vs. Phase F roadmap

    Phase E creates the initial complete Architecture Roadmap and decides whether Transition Architectures are needed; Phase F finalizes the roadmap and the Implementation and Migration Plan.

    Remember
    Initial equals E, final equals F.
    Tested as
    The most common near-miss pair on the paper.
    Trap
    Answering F for anything involving Transition Architectures.

  • Transition Architecture

    An intermediate state between baseline and target that delivers business value on its own.

    Remember
    Identified in Phase E when an incremental approach is needed, and scheduled in Phase F.
    Tested as
    Appears in Phase E objective questions and definition items.
    Trap
    Treating it as a temporary design with no business value.

  • Iteration cycles

    Architecture Capability (Preliminary and A), Architecture Development (B to D), Transition Planning (E and F) and Architecture Governance (G and H).

    Remember
    Iteration happens within phases, between phases and across whole ADM cycles.
    Tested as
    Asked directly as 'which phases form the X iteration'.
    Trap
    Grouping A with B to D, or G with F.

  • Scoping dimensions

    Breadth (how much of the enterprise), depth (level of detail), time period (horizon) and architecture domains (which of the four).

    Remember
    Scope is set in the Preliminary Phase and Phase A and limits effort to what stakeholders need.
    Tested as
    List and 'which is NOT a dimension' questions.
    Trap
    Adding budget or team size as a dimension.

  • Phase H change classes

    Simplification change is usually handled through change management; incremental change may be handled by change management or partial re-architecting; re-architecting change requires a new ADM cycle.

    Remember
    Only re-architecting change necessarily triggers a new Request for Architecture Work.
    Tested as
    Phase H purpose and objective questions.
    Trap
    Assuming every change restarts the ADM.

  • Requirements Management role

    A central process that identifies, stores and supplies architecture requirements to each phase and assesses changes with a Requirements Impact Assessment.

    Remember
    It does not dispose of, address or prioritize requirements; each phase does that.
    Tested as
    Classic false-statement distractor.
    Trap
    Choosing 'prioritizes requirements' as its objective.

  • Draft vs. approved

    Deliverables start as drafts (0.x versions) and are refined across phases until reviewed, signed off and approved (1.0).

    Remember
    Approved deliverables are under change control.
    Tested as
    Direct learning outcome 3.2.
    Trap
    Thinking a phase must finish its deliverables before the next phase starts.

  • Architecture alternatives

    Multiple candidate architectures evaluated against stakeholder concerns so trade-offs can be agreed.

    Remember
    The result may combine elements of several alternatives.
    Tested as
    Outcome 3.6 'why consider alternatives' questions.
    Trap
    Choosing an answer where the architect picks the most technically elegant option alone.

  • Architecture for strategy, portfolio, project and solution delivery

    Four purposes of architecture work that set its horizon and level of detail.

    Remember
    Higher-level architecture gives Agile teams guardrails; solution-level detail is added just in time.
    Tested as
    Outcome 3.26 and Unit 5 outcome 5.5.
    Trap
    Assuming one level of detail fits every architecture effort.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Preliminary Phase vs. Phase A

ConceptMeaningKey differenceCommon trap
Preliminary Phase Determine and establish the Architecture Capability About the architecture practice; not tied to one effort Expecting a vision for a specific change here
Phase A Develop a high-level vision and obtain approval for the Statement of Architecture Work Starts a specific ADM cycle after a Request for Architecture Work Placing tool selection or governance set-up here

Phase E vs. Phase F

ConceptMeaningKey differenceCommon trap
Phase E Initial complete Architecture Roadmap; decide whether Transition Architectures are needed Identifies opportunities, work packages and delivery vehicles Thinking E finalizes the plan
Phase F Finalize roadmap and Implementation and Migration Plan; coordinate with the change portfolio Prioritizes by value, cost and risk and makes stakeholders understand them Thinking F first identifies Transition Architectures

Phase G vs. Phase H

ConceptMeaningKey differenceCommon trap
Phase G Ensure implementation projects conform to the Target Architecture Oversight during implementation, via Architecture Contracts and compliance reviews Thinking G builds the solution
Phase H Manage changes to the architecture and keep the capability current After deployment; may trigger a new ADM cycle Using H for compliance reviews of in-flight projects

Request for Architecture Work vs. Statement of Architecture Work

ConceptMeaningKey differenceCommon trap
Request for Architecture Work Document from the sponsor asking the architecture function to start an ADM cycle Input that triggers Phase A; may be produced by Phase H Thinking it is produced in Phase A
Statement of Architecture Work Agreed scope, approach and plan for the architecture effort Output of Phase A, approved by the sponsor Treating it as the initial request

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Transition Architectures in Phase F

    What candidates pick
    Phase F as the phase that determines whether Transition Architectures are needed.
    Why it looks right
    Transition Architectures appear in the Implementation and Migration Plan that F finalizes.
    Why it's wrong
    Phase E determines whether an incremental approach is required and identifies the Transition Architectures; F schedules and finalizes them.

    Clue to watch for 'Determine', 'identify' or 'initial' points to E; 'finalize', 'cost' or 'prioritize' points to F.

  2. Preliminary versus Phase A

    What candidates pick
    Phase A for defining the organizational model for EA and selecting tools.
    Why it looks right
    Phase A is the first phase of a cycle and also reviews principles.
    Why it's wrong
    Establishing the Architecture Capability, including governance, tools and the organizational model, is the Preliminary Phase.

    Clue to watch for If no specific architecture effort or Request for Architecture Work is mentioned, think Preliminary.

  3. Requirements Management as decision-maker

    What candidates pick
    'Requirements Management prioritizes architecture requirements' as a true statement.
    Why it looks right
    Managing requirements sounds as if it includes prioritizing them.
    Why it's wrong
    The process identifies, stores and supplies requirements; the relevant phase addresses and prioritizes them.

    Clue to watch for Any option giving Requirements Management authority to dispose of or prioritize requirements is a distractor.

  4. Phase G versus Phase H

    What candidates pick
    Phase H for compliance reviews of projects that are still being built.
    Why it looks right
    Both phases are about governance after design.
    Why it's wrong
    Conformance of implementation projects is Phase G; Phase H manages change to the deployed architecture.

    Clue to watch for 'Implementation projects' or 'Architecture Contract' means G; 'change request after deployment' or 'new cycle' means H.

  5. Every change restarts the ADM

    What candidates pick
    A new ADM cycle as the response to any change request in Phase H.
    Why it looks right
    Starting again seems thorough.
    Why it's wrong
    Simplification changes and many incremental changes are handled through change management; only re-architecting change requires a new cycle.

    Clue to watch for Look for the size of the change: small or local changes stay in change management.

  6. Strictly sequential ADM

    What candidates pick
    A statement that each phase must be completed before the next starts.
    Why it looks right
    The ADM diagram looks like a sequence.
    Why it's wrong
    The ADM is iterative within and between phases, and phases can run concurrently; deliverables are often drafts until later phases.

    Clue to watch for Words such as 'must always' or 'strictly' about phase order usually mark the wrong answer.

Answer framework

Use these steps to place any activity, objective or deliverable in the right ADM phase.

  1. Ask whether the stem is about the architecture practice itself rather than one effort; if so, think Preliminary Phase or Phase H.
  2. Check whether a specific effort has just started with a Request for Architecture Work and still needs scope, stakeholders and sponsor approval, which signals Phase A.
  3. Identify the domain being designed: business operation is B, data and applications are C, platforms and infrastructure are D.
  4. For delivery planning, use 'initial roadmap and Transition Architectures' for E and 'finalize, cost, prioritize' for F.
  5. For work after planning, choose G when projects are being built under Architecture Contracts and H when the deployed architecture faces change.

Practice question

Target Business, Data, Application and Technology Architectures have been agreed. The architecture team now consolidates the gap analysis results from each domain, groups the changes into work packages, and decides whether the move to the target should be made through intermediate states. Which ADM phase is this?

Want more like this? The TOGAF EA Foundation practice test has questions for every domain.

Checklist

0 of 14

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Learn the ADM cycle as a story before learning the objectives. Draw the circle, write one verb for each phase (prepare, envision, design business, design data and applications, design technology, identify opportunities, plan migration, govern, manage change) and put Requirements Management in the middle. Once the story is fixed, learn the official objectives for each phase, since those are the wording the questions use.

Spend the most time on the near-miss pairs: Preliminary versus A, E versus F, and G versus H. For each pair, write one signature phrase: 'establish the capability' versus 'approve the Statement of Architecture Work', 'initial roadmap and Transition Architectures' versus 'finalize and coordinate the plan', 'conformance of projects' versus 'keep the architecture and capability current'.

Commonly underestimated areas are iteration cycles, scoping dimensions and Requirements Management. They are short lists, so they are easy marks once learned, but candidates often skip them while focusing on phases.

Finish by tracing deliverables through the cycle, which links this unit to Architecture Content. Then practise 'which phase' questions in sets of 14, the official allocation for this unit, aiming to answer each in under a minute.

FAQ

How much of the TOGAF EA Foundation exam covers the ADM?

The official OGEA-101 exam plan allocates 14 of the 40 questions to Introduction to the ADM, which is 35% and the largest single unit.

Do I need to know the detailed steps of each phase?

The Foundation learning outcomes focus on the purpose and objectives of each phase, iteration, scoping and information flow. Detailed steps are more relevant to the Practitioner level, though knowing the common B to D step pattern helps.

What is the difference between Phase E and Phase F?

Phase E creates the initial complete Architecture Roadmap and decides whether Transition Architectures are needed. Phase F finalizes the roadmap and the Implementation and Migration Plan and makes sure stakeholders understand the value and cost of each work package.

Is Requirements Management a phase?

It is shown at the centre of the ADM and runs continuously, feeding every phase. It manages requirements but does not prioritize or dispose of them; the phases do that.

Must the ADM be followed in strict order?

No. The ADM is iterative within phases, between phases and across cycles, and it should be tailored to the organization. Iteration cycles group phases that are often repeated together.

Which phase starts a new ADM cycle?

A cycle begins with a Request for Architecture Work. Phase H can produce one when a re-architecting change is needed, which starts a new cycle at Phase A.

How long should I spend on this unit?

As a planning estimate, about 12 to 16 hours of a 40-hour plan, which reflects its 35% share of the questions.

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 2 knowledge

You have just separated the purpose and objectives of every ADM phase, including the E and F, G and H near-misses. Test whether you can place an activity in the right phase within a minute.

Take the TOGAF EA Foundation practice test Check your TOGAF EA Foundation readiness

Keep going