1.2 The TOGAF Standard 10th Edition Structure & Core Concepts

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:

1. Introduction and Core Concepts: Defines standard terminology, architectural boundaries, and the organizational value of enterprise architecture.
2. Architecture Development Method (ADM): The iterative method (Preliminary Phase through Phase H, governed continuously by Requirements Management) for developing and managing enterprise architectures.
3. ADM Techniques: Practical tools supporting the ADM, including Capability-Based Planning, Risk Management, Gap Analysis, Business Scenarios, and Architecture Principles.
4. Applying the ADM: Guidance on adapting the ADM across iterative cycles, managing partitioned architecture landscapes, and operating across strategic, segment, and capability levels.
5. 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.
6. 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:

1. 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.
2. 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:

---

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:

1. Foundation Architectures: Universal principles and fundamental standards common to all systems (e.g., Technical Reference Model).
2. Common Systems Architectures: Reusable solutions across common operational domains (e.g., security or payment frameworks).
3. Industry Architectures: Standards and domain models specific to vertical industries (e.g., BIAN in banking, eTOM in telecommunications).
4. 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.