Study guide
1.2 The TOGAF Standard 10th Edition Structure & Core Concepts
TOGAF Enterprise Architecture Practitioner OGEA-103
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Mechanics & Foundation Overview
1.1 OGEA-103 Exam Structure, Gradient Scoring & Open-Book Strategy 1.2 The TOGAF Standard 10th Edition Structure & Core Concepts 1.3 Enterprise Architecture in Practice: Context, Scope, and Architecture Domains 1.4 The Context for Enterprise Architecture: Purpose, Capability, Security, and the Digital Enterprise
2 Chapter 2: Preliminary Phase & Establishing the EA Capability
2.1 Preliminary Phase Objectives, Inputs, and Activities 2.2 Scope of the Enterprise and Defining the Architecture Footprint 2.3 Establishing Architecture Governance, Frameworks, and Tools
3 Chapter 3: Architecture Vision & Stakeholder Management (Phase A)
3.1 Phase A Objectives, Request for Architecture Work, and Scope Definition 3.2 Stakeholder Management: Identification, Classification, the Power/Interest Grid, and the Stakeholder Map 3.3 Business Scenarios Technique for Problem Definition and Requirements Elicitation 3.4 Architecture Vision, Communications Plan, and Statement of Architecture Work Approval
4 Chapter 4: Business Architecture (Phase B)
4.1 Phase B Objectives, Steps, and Business Modeling Approaches 4.2 Business Capabilities, Capability Mapping, and Assessment 4.3 Value Streams, Value Stream Mapping, and Capability Cross-Mapping 4.4 Business Architecture Artifacts, Gap Analysis, and Architecture Definition Document Updates
5 Chapter 5: Information Systems Architectures — Data Architecture (Phase C)
5.1 Phase C Data Architecture Objectives, Approach, and Data Principles 5.2 Conceptual, Logical, and Physical Data Models and Data Management 5.3 Data Entity/Business Function Matrix, Data Architecture Gap Analysis, and Interoperability Requirements
6 Chapter 6: Information Systems Architectures — Application Architecture (Phase C)
6.1 Phase C Application Architecture Objectives, Approach, and Baseline vs. Target First 6.2 Application Portfolio Rationalization, Component Modeling, and Application Integration 6.3 Application/Organization Matrix, Application Gap Analysis, and Boundary Definitions
7 Chapter 7: Technology Architecture (Phase D)
7.1 Phase D Objectives, Cloud & Modern Platforms, and Technology Principles 7.2 Technology Standards, the Standards Library, Platform Services, and Infrastructure Modeling 7.3 Technology Gap Analysis, Non-Functional Requirements, and Reference Models
8 Chapter 8: Opportunities and Solutions (Phase E)
8.1 Phase E Objectives, Consolidated Gap Analysis, and Work Package Formulation 8.2 Architecture Building Blocks (ABBs) to Solution Building Blocks (SBBs) Transition 8.3 Transition Architectures, Incremental Delivery, and Dependency Analysis 8.4 Architecture Roadmap Development and Trade-Off Analysis 8.5 Business Transformation Readiness Assessment and Risk Management
9 Chapter 9: Migration Planning (Phase F)
9.1 Phase F Objectives, Stakeholder Collaboration, and Governance Alignment 9.2 Business Value Assessment, Cost-Benefit Analysis, and Risk/Feasibility Scoring 9.3 Implementation and Migration Plan Deliverable, Resource Allocation, and Transition Roadmaps
10 Chapter 10: Implementation Governance (Phase G)
10.1 Phase G Objectives, Implementation Governance Structure, and Project Architecture Hand-off 10.2 Architecture Contracts: Purpose, Types, Timing, and Stakeholder Commitments 10.3 Architecture Compliance Reviews: Conformance Levels, Process, Timing, and Checklists
11 Chapter 11: Architecture Change Management (Phase H) & Requirements Management
11.1 Phase H Objectives, Drivers of Architecture Change, and Value Monitoring 11.2 Change Classification: Simplification, Incremental, and Re-Architecting Changes 11.3 Ongoing Governance, Retirement of Solutions, and Maintenance vs. New ADM Cycle 11.4 Requirements Management: Central Role, Traceability, Mid-Phase Discovery, and Scope Conflict
12 Chapter 12: Architecture Governance, Boards, and Dispensations
12.1 Architecture Governance Framework, Organizational Roles, and RACI Matrix 12.2 Architecture Board Structure, Federation, Responsibilities, and Meeting Operations 12.3 Compliance Assessment, Dispensation Process, Expiration, and Remediation Tracking 12.4 Architecture Principles, the Decision Log, and Resolving Principle Conflicts
13 Chapter 13: Architecture Content Framework & Architecture Repository
13.1 The TOGAF Content Framework and Enterprise Metamodel 13.2 Deliverables, Artifacts (Catalogs, Matrices, Diagrams), and Building Blocks (ABBs vs SBBs) 13.3 Architectural Views, Viewpoints, Stakeholder Concerns, and ISO/IEC/IEEE 42010 13.4 The Enterprise Continuum and the TOGAF 10 Architecture Repository
14 Chapter 14: EA Capability, Tailoring, and Iteration
14.1 Tailoring the ADM: Enterprise Context, Process Weight, and Agile Integration 14.2 ADM Iteration Cycles, Levels, and Classes of Architecture Engagement 14.3 Architecture Maturity Models, Capability Assessment, and EA Performance Measures 14.4 Supporting the ADM Work: The TOGAF Library, Series Guides, Patterns, and Security
1.2 The TOGAF Standard 10th Edition Structure & Core Concepts
Key Takeaways Explain This Topic AI
The TOGAF Standard 10th Edition is structured into two main components: universal TOGAF Fundamental Content and adaptable TOGAF Series Guides.
TOGAF Fundamental Content establishes the enduring core of enterprise architecture, encompassing the ADM lifecycle, foundational concepts, ADM techniques, applying the ADM, architecture content, and EA capability and governance.
TOGAF Series Guides provide practitioner-focused guidance on applying the standard to specialized paradigms such as Business Architecture, Digital and Agile enterprises, Security Architecture, and Microservices.
An enterprise is defined as any collection of organizations sharing common goals, while architecture represents both a formal system description (ISO/IEC/IEEE 42010) and the structured arrangement of its components.
The Enterprise Continuum provides a categorization taxonomy and virtual repository framework, structuring assets from generic Foundation Architectures down to Organization-Specific Solutions.
Last updated: October 2026
1.2 The TOGAF Standard 10th Edition Structure & Core Concepts
The TOGAF Standard, 10th Edition is organized into two complementary parts: TOGAF Fundamental Content and the TOGAF Series Guides . Together they form the TOGAF Standard, and the wider TOGAF Library holds further reference material that supports it. Earlier releases, such as TOGAF 9.2, bound core methods and domain playbooks into a single volume. The 10th Edition separates universal, enduring concepts from rapidly evolving domain practices. Understanding this modular division and master terminology is essential for both foundational comprehension and scenario analysis.
The Modular Architecture of the 10th Edition
The modular structure addresses the diverging lifecycles of core architectural methods versus emerging technology practices. Universal concepts—such as running an iterative development cycle, defining building blocks, and governing change—remain stable over decades. In contrast, implementation practices for Cloud-Native platforms, DevOps pipelines, Agile operating models, and Zero Trust security evolve rapidly.
By decoupling the standard into two tiers, The Open Group maintains an enduring foundation while enabling specialized guides to update dynamically:
TOGAF Fundamental Content : The universal, enduring core of enterprise architecture. It establishes foundational principles, terminology, and governance mechanisms that apply across all industries, organizational models, and technological platforms.
TOGAF Series Guides : Practical, topic-specific playbooks authored by industry working groups. They provide detailed instructions for configuring and applying Fundamental Content to specific business domains and technology paradigms.
TOGAF Fundamental Content: The Enduring Core
The Fundamental Content constitutes the core syllabus tested across both exam sections, organized into six essential areas:
Introduction and Core Concepts : Defines standard terminology, architectural boundaries, and the organizational value of enterprise architecture.
Architecture Development Method (ADM) : The iterative method (Preliminary Phase through Phase H, governed continuously by Requirements Management) for developing and managing enterprise architectures.
ADM Techniques : Practical tools supporting the ADM, including Capability-Based Planning, Risk Management, Gap Analysis, Business Scenarios, and Architecture Principles.
Applying the ADM : Guidance on adapting the ADM across iterative cycles, managing partitioned architecture landscapes, and operating across strategic, segment, and capability levels.
Architecture Content : The Content Framework and TOGAF Enterprise Metamodel, which classify work products into Deliverables, Artifacts (Catalogs, Matrices, Diagrams), and Building Blocks (ABBs and SBBs), plus the Enterprise Continuum and Architecture Repository.
Enterprise Architecture Capability and Governance : Guidelines for establishing Architecture Boards, executing compliance reviews, managing contracts, and organizing architecture teams.
TOGAF Series Guides: Domain Extension Playbooks
While Fundamental Content explains what must be done, the TOGAF Series Guides demonstrate how to apply it in targeted environments. Some older guides in the Library, such as the Technical Reference Model (TRM) and the Integrated Information Infrastructure Reference Model (III-RM), are now marked as historical:
Business Architecture Guides : Provide practical methodologies for Business Capability Mapping, Value Stream Modeling, Information Mapping, and Organization Mapping. Business architecture ensures technical execution directly supports business strategy.
Digital & Agile Guides : Guide the application of enterprise architecture within Agile environments (such as SAFe and Scrum), providing intentional architecture runways without bureaucratic roadblocks.
Security & Risk Architecture Guides : Explain how to integrate risk and security considerations into every phase of the ADM (for example, Integrating Risk and Security within a TOGAF Enterprise Architecture ).
Information Systems & Technology Guides : Address contemporary technical patterns, including Microservices, Cloud ecosystems, and Service-Oriented Architecture (SOA).
Core Definitions and Terminology
Precise mastery of formal TOGAF definitions is essential for exam success:
The Enterprise
In TOGAF, an Enterprise is defined as any collection of organizations that have common goals . An enterprise is defined by shared objectives rather than legal boundaries. It may encompass a whole corporation, a business division, a government agency, a multi-firm consortium, or an extended supply chain partnership.
Architecture
The standard recognizes a dual definition of Architecture :
ISO/IEC/IEEE 42010 Definition : The fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.
Operational Definition : The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time.
TOGAF models the enterprise itself as a complex system operating within dynamic business and operational environments.
Architecture Framework
An Architecture Framework is a conceptual structure and set of tools used for developing, maintaining, and governing a broad range of architectures. It provides a common vocabulary, standardized processes, and classification taxonomy.
Deliverables, Artifacts, and Building Blocks
The Architecture Content Framework categorizes work products into three distinct constructs:
Work Product Formal Definition Examples
Deliverable A work product formally specified, reviewed, agreed upon, and signed off by stakeholders. Statement of Architecture Work, Architecture Definition Document, Architecture Contract
Artifact An architectural work product describing an aspect of the architecture, classified into Catalogs (lists), Matrices (relationships), and Diagrams (views). Application Portfolio Catalog, Role/Actor Matrix, Data Flow Diagram
Building Block A reusable component of enterprise capability, divided into Architecture Building Blocks (ABBs, defining logical needs) and Solution Building Blocks (SBBs, defining physical products). Customer Authentication (ABB) versus Okta Identity Engine (SBB)
The ADM Lifecycle and Requirements Management
The Architecture Development Method (ADM) forms the iterative core of TOGAF, executing across ten phases:
Preliminary Phase : Establishes architecture capability, tailors frameworks, and defines governance.
Phase A (Architecture Vision) : Validates scope, identifies stakeholders, and drafts the Statement of Architecture Work.
Phase B (Business Architecture) : Models strategy, capabilities, value streams, and processes.
Phase C (Information Systems Architectures) : Details Data and Application architectures.
Phase D (Technology Architecture) : Defines infrastructure, platforms, and networks.
Phase E (Opportunities & Solutions) : Outlines initial roadmaps and transitions from ABBs to SBBs.
Phase F (Migration Planning) : Finalizes implementation roadmaps with portfolio managers.
Phase G (Implementation Governance) : Enforces architecture compliance during implementation.
Phase H (Architecture Change Management) : Assesses change drivers and initiates new cycles.
Requirements Management : Continuously captures, validates, and prioritizes requirements across all phases.
The Enterprise Continuum
The Enterprise Continuum is a classification taxonomy and virtual repository framework for structuring architectural assets along a spectrum of increasing specialization:
Foundation Architectures : Universal principles and fundamental standards common to all systems (e.g., Technical Reference Model).
Common Systems Architectures : Reusable solutions across common operational domains (e.g., security or payment frameworks).
Industry Architectures : Standards and domain models specific to vertical industries (e.g., BIAN in banking, eTOM in telecommunications).
Organization-Specific Architectures : Tailored architectures reflecting the unique operating model and competitive advantages of an enterprise.
Parallel to the Architecture Continuum (classifying logical models) is the Solutions Continuum , which classifies physical implementations from commercial software to bespoke internal systems.