Study guide

2.4 Applying the ADM: The TOGAF Library, Purpose-Based Architecture Projects & the Digital Enterprise

TOGAF Enterprise Architecture Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction to TOGAF & Enterprise Architecture Concepts

1.1 Overview of TOGAF Standard 10th Edition & Enterprise Architecture Concepts 1.2 The Structure of the TOGAF Standard (Easily Navigated Body of Knowledge) 1.3 Core Concepts: Enterprise, Architecture, Deliverables, Artifacts, and Building Blocks 1.4 TOGAF Certification Paths & the OGEA-101 Exam Plan

2 Chapter 2: ADM Foundation & Preliminary Phase

2.1 The Architecture Development Method (ADM) Cycle & Requirements Management 2.2 Preliminary Phase: Scope, Principles, and Architecture Capability Setup 2.3 Tailoring the ADM & Applying Iteration / Architecture Levels 2.4 Applying the ADM: The TOGAF Library, Purpose-Based Architecture Projects & the Digital Enterprise

3 Chapter 3: ADM Architecture Vision & Business Architecture

3.1 Phase A: Architecture Vision, Stakeholder Management & Value Proposition 3.2 Business Architecture Scope, Strategy & Capability Mapping 3.3 Phase B: Business Architecture Inputs, Steps, Outputs & Artifacts 3.4 Business Scenarios & Value Stream Modeling

4 Chapter 4: ADM Information Systems Architectures (Phase C)

4.1 Information Systems Architectures Overview & Phase C Strategy 4.2 Phase C Data Architecture: Principles, Data Models & Governance 4.3 Phase C Application Architecture: Logical Components, Services & Interfaces 4.4 Data and Application Integration, Migration & Interoperability

5 Chapter 5: ADM Technology Architecture & Solution Realization (Phases D, E, F)

5.1 Phase D: Technology Architecture, Platform Services & Infrastructure 5.2 Phase E: Opportunities and Solutions & Initial Implementation Strategy 5.3 Phase F: Migration Planning, Roadmap Development & Portfolio Prioritization 5.4 Transition Architectures & Implementation Dependencies

6 Chapter 6: ADM Governance, Change & Requirements Management (Phases G, H)

6.1 Phase G: Implementation Governance & Architecture Compliance 6.2 Phase H: Architecture Change Management & Driver Monitoring 6.3 Requirements Management: Central Flow, Impact Analysis & Traceability 6.4 Architecture Contracts, Dispensations & Compliance Reviews

7 Chapter 7: BDAT Architecture Domains Deep-Dive

7.1 Business Architecture Domain: Functions, Processes & Value Streams 7.2 Data Architecture Domain: Data Entities, Storage & Data Management 7.3 Application Architecture Domain: Application Services, Systems & Integration Patterns 7.4 Technology Architecture Domain: Hardware, Software, Cloud & Network Platforms

8 Chapter 8: Architecture Content — Content Framework, Enterprise Metamodel & Artifacts

8.1 Architecture Content Framework Overview & Deliverables vs Artifacts vs Building Blocks 8.2 Architecture Building Blocks (ABBs) vs Solution Building Blocks (SBBs) 8.3 The Enterprise Metamodel: Core Concepts, Entities & Attributes 8.4 Architecture Catalogs, Matrices & Diagrams (Visual Representation) 8.5 Stakeholders, Concerns, Architecture Views & Viewpoints

9 Chapter 9: Architecture Governance, Capability & Maturity

9.1 Architecture Governance Framework & The Role of the Architecture Board 9.2 Establishing an Architecture Capability & Organizational Structure 9.3 Architecture Skills Framework, Roles & Competency Levels 9.4 Architecture Maturity Models & Capability Assessments

10 Chapter 10: Enterprise Continuum, Reference Models & Key Techniques

10.1 Enterprise Continuum, Architecture Repository & Landscape Partitioning 10.2 Technical Reference Model (TRM) & Integrated Information Infrastructure Reference Model (III-RM) 10.3 Core EA Techniques: Gap Analysis, Interoperability, Risk, Capability-Based Planning & Architecture Patterns

2.4 Applying the ADM: The TOGAF Library, Purpose-Based Architecture Projects & the Digital Enterprise

Key Takeaways Explain This Topic AI

TOGAF distinguishes four purposes for architecture work: to support Strategy, Portfolio, Project, and Solution Delivery — each with a different scope, time horizon, and level of detail.

Purpose-based architecture projects map onto the three architecture levels: Strategy work produces Strategic Architecture, Portfolio work produces Segment Architecture, and Project and Solution Delivery work produce Capability and solution-level architecture.

The TOGAF Library supplies the Series Guides, templates, patterns, and reference models used to configure the ADM for a specific context; it is not part of the normative standard.

Applying the ADM in an agile enterprise means producing just enough architecture just in time, feeding an architecture runway, and treating architecture as a stream of increments rather than a single up-front deliverable.

The Foundation syllabus area 'Introduction to Applying the ADM' carries 4 of the 40 OGEA-101 questions, covering iteration, architecture levels, partitioning, purpose-based projects, and digital enterprise support.

Last updated: November 2026

2.4 Applying the ADM: The TOGAF Library, Purpose-Based Architecture Projects & the Digital Enterprise

Section 2.3 covered how much ADM to run — tailoring, iteration cycles, and architecture levels. This section covers the question that comes immediately before it: what is this piece of architecture work actually for? TOGAF's answer is more precise than "to produce an architecture," and getting it right is what stops an architecture team from producing beautifully modelled documents that nobody uses.

Purpose-Based Architecture Projects

The TOGAF Standard identifies four distinct purposes that an architecture project can serve. They are not maturity stages and they are not sequential — a healthy architecture practice runs all four concurrently for different parts of the enterprise.

Purpose Question It Answers Typical Sponsor Horizon Characteristic Output

Architecture to support Strategy "Where should the enterprise go, and what capabilities will it need?" CEO, CIO, strategy function 3–10 years Enterprise-wide target capability model, direction-setting roadmap

Architecture to support Portfolio "Which programs should we fund, in what order, and how do they fit together?" Portfolio board, business-unit executive 1–3 years Segment architecture, coordinated program roadmap, shared building blocks

Architecture to support Project "What must this project build so that it fits the enterprise?" Program or project sponsor Months to ~1 year Constraints, target architecture for the project scope, work packages

Architecture to support Solution Delivery "Is what is being built actually conformant, and how do we keep it that way?" Delivery lead, implementation partner Weeks to months Architecture Contract, compliance assessments, governance decisions

Three consequences follow, and each is worth internalizing:

The purpose determines the deliverable set, not the other way round. An Architecture Definition Document produced for Solution Delivery and one produced for Strategy should not look alike. Strategy work that descends to interface specifications has failed; Solution Delivery work that stops at capability maps has also failed.

The purpose determines the appropriate architecture level. Strategy work produces Strategic Architecture ; Portfolio work produces Segment Architecture ; Project and Solution Delivery work produce Capability Architecture and solution-level detail. This is the practical bridge between the abstract three-level landscape of Section 2.3 and a real engagement.

The purpose determines who governs it. Strategy and Portfolio architectures are governed by the Architecture Board directly; Project and Solution Delivery architectures are usually governed through Architecture Contracts and compliance reviews (Sections 6.1 and 6.4).

A common failure mode: an architecture team is asked for "an enterprise architecture," produces a Strategy-purpose artifact, and is then criticized by delivery teams for being abstract and by executives for being slow. The team never asked which purpose it was serving. Ask first.

Using the TOGAF Library to Configure the Framework

The ADM is deliberately generic. The TOGAF Library is where the specifics live: Series Guides, reference models, templates, patterns, and worked material published by The Open Group to help you configure the framework for a context. Applying the standard well means reaching for the Library rather than re-deriving guidance from first principles.

If you need to… Reach for…

Model business capabilities or value streams Series Guides: Business Capabilities , Value Streams , Organization Mapping , Information Mapping

Stand up or evolve an architecture practice Series Guide: The TOGAF Leader's Guide to Establishing and Evolving an EA Capability

Integrate security and risk into the ADM Series Guide: Integrating Risk and Security within a TOGAF Enterprise Architecture

Work in an agile delivery environment Series Guides on enterprise agility and applying the standard in the digital enterprise

Build a technology-standards taxonomy Series Guide: The TOGAF Technical Reference Model (TRM) , now marked Historical; use it as a starting taxonomy to tailor

Material you adopt from the Library is normally copied into the Reference Library class of your Architecture Repository (Section 10.1), where it sits alongside your own in-house patterns. Note the boundary carefully: adopting Library material does not by itself make it binding on your projects. Reference material informs practice; it is your Standards Library that binds compliance, so anything you intend to enforce has to be promoted into the Standards Library and governed. Be precise about the Library's status, too — it is the store that holds the TOGAF documentation set, and the Series Guides inside it are part of the TOGAF Standard (Section 1.2). What is advisory is the reference material you draw from it, not the standard itself.

Applying the ADM to Support the Digital Enterprise

"Digital enterprise" is not a slogan in the standard; it names a specific set of pressures that change how the ADM is executed:

Change is continuous, not episodic. The enterprise is never between architectures. Phase H stops being an occasional review and becomes a standing function that continuously triggers new Architecture Capability and Architecture Development iterations.

The unit of change is smaller. Instead of one multi-year transformation, the enterprise runs many small changes concurrently. That pushes work toward Capability Architecture and Solution Delivery purposes, with Strategic Architecture providing guardrails rather than blueprints.

Decisions must be made with less certainty. Architecture alternatives and trade-offs move to the foreground: the architect's job becomes framing options and their consequences for stakeholders, not declaring a single answer.

Architecture in an Agile Enterprise

Applying the ADM alongside agile software delivery is an explicit Foundation-level topic, and the reconciliation is simpler than the debate around it suggests:

Just enough architecture, just in time. Produce the architecture needed for the next increment at the level of detail that increment requires. Architecture work is itself iterative — that is what the four iteration cycles are for.

Feed an architecture runway. Architecture Building Blocks defined ahead of delivery (shared identity services, event backbones, data contracts) let delivery squads move fast without each inventing its own foundation.

Govern by contract, not by gate-keeping. An Architecture Contract that states the constraints a squad must respect scales far better across many concurrent teams than a review board approving every design.

Keep the Requirements Repository authoritative. Agile backlogs churn; architecture requirements need a stable home so traceability survives re-prioritization.

The failure mode to avoid is treating "agile" as a licence to skip architecture entirely. The result is a fast accumulation of technical debt that the enterprise pays for over the following decade — exactly the outcome enterprise architecture exists to prevent.

Exam Focus

The Introduction to Applying the ADM syllabus area is worth 4 of the 40 questions on OGEA-101. Across that area and Section 2.3, be able to state: how to apply the standard (via the Library and Series Guides), how iteration works, the three levels of the Architecture Landscape, why partitioning is used, the four purposes of architecture projects, and how the standard supports the digital enterprise.