TOGAF 10 Foundation Cheat Sheet (2026): Key Concepts + Exam Traps

Core Framework

TOGAF ADM (Architecture Development Method) Phases

TOGAF 10 Foundation tests understanding of the ADM, Architecture Content Framework, Enterprise Continuum, and Architecture Repository. Know the sequence of phases, what each produces, and the governance mechanisms.

01
Preliminary — Framework and principles setup
02
Phase A: Architecture Vision — Define scope and obtain approval
03
Phase B: Business Architecture — Baseline and target business architecture
04
Phase C: Information Systems — Data and application architectures
05
Phase D: Technology Architecture — Infrastructure supporting the IS architectures
06
Phase E: Opportunities & Solutions — Identify implementation projects
07
Phase F: Migration Planning — Detailed migration roadmap
08
Phase G: Implementation Governance — Oversee implementation
09
Phase H: Architecture Change Management — Monitor and manage changes
10
Requirements Management — Central, ongoing phase supporting all other phases

Scenario Traps

Wrong instinct vs correct approach

A new enterprise strategy requires a significant change to the architecture

✕ Wrong instinct

Start the ADM from Phase A

✓ Correct approach

Initiate Architecture Change Management (Phase H) to assess the impact — depending on the significance, the response may range from a simple architecture update to triggering a new ADM cycle from Phase A

Implementation teams are deviating from the approved architecture

✕ Wrong instinct

Revise the architecture to match what is being built

✓ Correct approach

This is an Implementation Governance (Phase G) issue — the Architecture Board must assess the deviation, determine whether to grant a dispensation or require conformance, and document the governance decision

A project team needs architecture guidance for a specific initiative

✕ Wrong instinct

Provide a complete enterprise architecture

✓ Correct approach

Develop an Architecture Contract with the specific architecture requirements and constraints relevant to the project — provide targeted guidance, not the full enterprise architecture

Quick Rules

Know these cold

▸ ADM is iterative — phases can be revisited as requirements change
▸ Requirements Management is continuous and central — not a sequential phase
▸ Deliverables = contractual outputs; Artifacts = descriptions within deliverables; Building Blocks = reusable components
▸ Architecture Governance ensures implementations conform to approved architectures
▸ Phase G (Implementation Governance) monitors implementation; Phase H manages ongoing changes
▸ Architecture Vision (Phase A) requires stakeholder buy-in before architecture development begins
▸ The Enterprise Continuum provides a classification system from Foundation to Organization-Specific architectures

Self Check

Can you answer these without checking your notes?

In this scenario: "A new enterprise strategy requires a significant change to the architecture" — what should you do first?

Initiate Architecture Change Management (Phase H) to assess the impact — depending on the significance, the response may range from a simple architecture update to triggering a new ADM cycle from Phase A

In this scenario: "Implementation teams are deviating from the approved architecture" — what should you do first?

This is an Implementation Governance (Phase G) issue — the Architecture Board must assess the deviation, determine whether to grant a dispensation or require conformance, and document the governance decision

In this scenario: "A project team needs architecture guidance for a specific initiative" — what should you do first?

Develop an Architecture Contract with the specific architecture requirements and constraints relevant to the project — provide targeted guidance, not the full enterprise architecture

Failure Patterns

Common Exam Mistakes — What candidates get wrong

Confusing ADM phases with project lifecycle phases

ADM phases are architecture phases, not project delivery phases. Phase E (Opportunities & Solutions) produces Architecture Roadmaps and Implementation Proposals — it does not execute implementations. Candidates confuse architecture work with project execution.

Treating Requirements Management as a phase in the ADM sequence

Requirements Management is a central, continuous phase that supports all other ADM phases — it is not sequenced before or after other phases. Candidates who place it sequentially in the ADM misunderstand its function.

Confusing deliverables, artifacts, and building blocks

Deliverables are contractual work products delivered to stakeholders. Artifacts are descriptions within deliverables (matrices, diagrams, catalogs). Building blocks represent business or technology components. These are distinct concepts with specific TOGAF meanings.

Misidentifying the Architecture Repository components

The Architecture Repository contains: Architecture Metamodel, Architecture Capability, Architecture Landscape, Standards Library, Reference Library, and Governance Log. Candidates who conflate these components fail content framework questions.

Ignoring stakeholder management in architecture work

TOGAF tests that architecture concerns must be identified per stakeholder and addressed in architecture views. Candidates who treat TOGAF as a purely technical framework miss the stakeholder-centric governance requirements.