Study guide
10.1 Enterprise Continuum, Architecture Repository & Landscape Partitioning
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
10.1 Enterprise Continuum, Architecture Repository & Landscape Partitioning
Key Takeaways Explain This Topic AI
The Enterprise Continuum acts as a conceptual framework and view of the Architecture Repository for classifying architectural and solution assets as they evolve from general to organization-specific.
The Architecture Continuum categorizes architectural abstractions (Foundation -> Common Systems -> Industry -> Organization-Specific), while the Solutions Continuum maps their real-world implementations (Foundation Solutions -> Common Systems Solutions -> Industry Solutions -> Organization-Specific Solutions).
The Architecture Repository holds eight classes of content: Architecture Metamodel, Architecture Capability, Architecture Landscape, Standards Library, Reference Library, Governance Repository, Architecture Requirements Repository, and Solutions Landscape.
Landscape Partitioning breaks the enterprise architecture into manageable, coherent partitions categorized across Strategic, Segment, and Capability architectures to enable concurrent architectural work and tailored governance.
Effective partitioning requires defining clear boundaries based on organizational ownership, time horizons, depth of detail, and cross-partition alignment to prevent architectural silos and governance gaps.
Last updated: November 2026
10.1 Enterprise Continuum, Architecture Repository & Landscape Partitioning
Enterprise Architecture (EA) within complex organizations produces vast quantities of architectural assets, reference models, governance records, standard definitions, and implementation decisions. Without a coherent structural framework, managing and reusing these assets across multiple architecture initiatives becomes unfeasible. The TOGAF Standard addresses this challenge through three interconnected structural constructs: the Enterprise Continuum , the Architecture Repository , and Landscape Partitioning .
Together, these mechanisms establish a consistent taxonomy for organizing architectural artifacts, a physical/logical repository structure for storing assets, and a strategic partitioning approach for dividing enterprise architectural labor.
The Enterprise Continuum: Context and Purpose
In TOGAF, the Enterprise Continuum is a conceptual framework and categorization mechanism that views all architectural assets available to the enterprise—both internal assets and external industry standards—along a continuum from general, reusable building blocks to highly specialized, organization-specific solutions.
Key Concept: The Enterprise Continuum is not a physical database or single software application; rather, it is a view of the Architecture Repository that illustrates how architectural concepts, models, and solution components evolve and relate to one another.
By leveraging the Enterprise Continuum, enterprise architects can:
Promote Architectural Reuse: Identify existing generic reference models, industry standards, and commercial products before building custom architectures from scratch.
Establish Clear Communication: Provide a standard vocabulary for discussing architectural abstractions and real-world implementations with technical and business stakeholders.
Navigate Abstraction Levels: Explicitly trace high-level generic concepts down to deployed operational software and hardware components.
Architecture Continuum vs. Solutions Continuum
The Enterprise Continuum is divided into two parallel, complementary continua that represent the dual nature of enterprise transformation: the Architecture Continuum and the Solutions Continuum . +-----------------------------------------------------------------------------------------+
- | ENTERPRISE CONTINUUM |
- | |
- | +-----------------------------------------------------------------------------------+ |
- | | ARCHITECTURE CONTINUUM | |
- | | Foundation -> Common Systems -> Industry -> Organization- | |
- | | Architectures Architectures Architectures Specific Arch. | |
- | +-----------------------------------------------------------------------------------+ |
- | | |
- | Guides & Constrains |
- | v |
- | +-----------------------------------------------------------------------------------+ |
- | | SOLUTIONS CONTINUUM | |
- | | Foundation -> Common Systems -> Industry -> Organization- | |
- | | Solutions Solutions Solutions Specific Solutions | |
- | +-----------------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------------+
- 1. The Architecture Continuum
The Architecture Continuum categorizes architectural assets and abstractions (such as principles, models, requirements, and enterprise blueprints) as they become increasingly tailored to the specific needs of the organization. It progresses through four distinct stages:
Foundation Architectures: Fundamentals that apply across any enterprise regardless of industry. Includes fundamental architectural principles, generic reference models (such as the TOGAF Technical Reference Model), and universal technology standards.
Common Systems Architectures: Guide the selection and integration of common systems shared across multiple industries or functional domains. Examples include security architecture patterns, high-availability cluster blueprints, and the TOGAF Integrated Information Infrastructure Reference Model (III-RM).
Industry Architectures: Integrate common systems architectures with industry-specific domain models, data standards, and regulatory requirements. Examples include banking frameworks (BIAN), telecommunications frameworks (eTOM), or healthcare interoperability standards (FHIR).
Organization-Specific Architectures: The target and baseline architectures tailored specifically to the unique business strategy, capabilities, structure, and operational environment of a single enterprise.
2. The Solutions Continuum
The Solutions Continuum mirrors the Architecture Continuum by describing the real-world physical assets, products, and implementations that realize the abstractions defined in the Architecture Continuum:
Foundation Solutions: Highly generic, reusable products and services such as commercial off-the-shelf (COTS) software, hardware components, cloud platform services, and supplier services (e.g., PostgreSQL, AWS S3, Linux OS).
Common Systems Solutions: Packaged configurations of products and services integrated to solve common enterprise problems (e.g., Enterprise Resource Planning (ERP) packages, Identity & Access Management platforms).
Industry Solutions: Commercial software packages or platform configurations pre-tailored for specific vertical markets (e.g., Core Banking software, Healthcare EHR systems).
Organization-Specific Solutions: The deployed operational applications, databases, custom code, and physical infrastructure running inside the specific enterprise.
Comparative Matrix: Continuum Stages
Stage / Level Architecture Continuum (Abstractions & Models) Solutions Continuum (Implementations & Products)
Foundation TOGAF Technical Reference Model (TRM), Universal Security Principles Operating Systems, Cloud Storage APIs, Generic Networking Protocols
Common Systems Integrated Information Infrastructure Reference Model (III-RM), ESB Patterns Enterprise Integration Platforms, Commercial IAM Systems, Message Brokers
Industry BIAN Banking Architecture Model, eTOM Telecommunication Framework Core Banking Systems, Telecommunications Billing Software
Organization-Specific Acme Corp Target Data Architecture 2028, Global Supply Chain Blueprint Deployed Acme Order Fulfillment System v4.2 on AWS
The TOGAF Architecture Repository
While the Enterprise Continuum provides the conceptual classification scheme, the Architecture Repository is the logical and physical container used to store, manage, and govern all architectural assets produced during ADM execution.
TOGAF defines eight classes of architectural information held within the Architecture Repository. TOGAF 9.1 listed only six — the Architecture Requirements Repository and the Solutions Landscape were added in TOGAF 9.2 — and TOGAF 9.x used the older names Standards Information Base and Governance Log for the classes now called the Standards Library and Governance Repository . The Reference Library is the class most often dropped by mistake: +-----------------------------------------------------------------------------------------+
- | ARCHITECTURE REPOSITORY |
- | |
- | +---------------------------+ +---------------------------+ +---------------------+ |
- | | Architecture Metamodel | | Architecture Capability | | Architecture | |
- | | (Architecture Method, | | (Skills, Organization, | | Landscape | |
- | | Enterprise Metamodel) | | Architecture Charter) | | (Strategic, Segment,| |
- | | | | | | Capability Levels) | |
- | +---------------------------+ +---------------------------+ +---------------------+ |
- | |
- | +---------------------------+ +---------------------------+ +---------------------+ |
- | | Standards Library | | Reference Library | |Governance Repository| |
- | | (Standards to Comply With)| | (Patterns, Templates, | | (Decision Log, | |
- | | | | TOGAF Library Material) | | Assessments) | |
- | +---------------------------+ +---------------------------+ +---------------------+ |
- | |
- | +---------------------------------------+ +----------------------------------------+ |
- | | Architecture Requirements Repository | | Solutions Landscape | |
- | | (Agreed requirements by level) | | (Planned or deployed SBBs) | |
- | +---------------------------------------+ +----------------------------------------+ |
- +-----------------------------------------------------------------------------------------+
- The Eight Classes of Repository Content
Architecture Metamodel: Holds the organization's tailored architecture method and its version of the Enterprise Metamodel: the entity types (e.g., Business Service, Application Component, Data Entity) and relationships used to keep architectural deliverables consistent.
Architecture Capability: Defines the organizational structures, roles, responsibilities, governance processes, skills, and tools that support the execution of enterprise architecture within the organization.
Architecture Landscape: Stores architectural views of the assets the enterprise uses or plans at specific points in time. TOGAF divides it by granularity into Strategic, Segment, and Capability Architectures (see Landscape Partitioning below); at each level it can hold:
Baseline Architecture: Current operational state.
Transition Architectures: Incremental stepping stones.
Target Architecture: Approved future state vision.
Standards Library: Contains explicit standards, specifications, and product lifecycles that all target architectures and solution implementations must comply with: legal and regulatory obligations, industry standards, and organizational standards (e.g., approved database versions, mandatory encryption standards). TOGAF 9 called this class the Standards Information Base (SIB).
Reference Library: Holds guidelines, templates, patterns, reference models, and other reusable reference material that accelerates the creation of new architectures. This is where an enterprise keeps its local copy of relevant TOGAF Library material — Series Guides, including the TRM and III-RM guides now marked Historical — alongside its own in-house patterns.
Governance Repository: Contains records of architectural governance activity across the enterprise: a Decision Log (product selections, standards deviations such as approved dispensations, change request evaluations), compliance assessments, capability assessments, a calendar of reviews, the project portfolio, and performance measurement. TOGAF 9 called this class the Governance Log.
Architecture Requirements Repository: Holds all functional, non-functional, business, and technical requirements agreed upon across ADM cycles, tracking requirement status from initial discovery through realization.
Solutions Landscape: Presents the Solution Building Blocks, planned or deployed, that support the Architecture Landscape — that is, the solutions that realize the architecture, as distinct from the architectural descriptions held in the Architecture Landscape.
Exam trap: the Reference Library and the Standards Library are easy to confuse. The Standards Library holds standards you must comply with; the Reference Library holds material you may reuse. A rejected-but-instructive pattern belongs in the Reference Library, never in the Standards Library.
Landscape Partitioning
In large enterprises, creating a single monolithic enterprise architecture is impossible due to organizational size, diverse business units, and rapid change. Landscape Partitioning is the technique of breaking down the enterprise architecture landscape into smaller, manageable, and self-contained architectural partitions.
Partitioning Levels in TOGAF
TOGAF categorizes landscape partitions across three primary operational levels:
Strategic Architectures:
Scope: Enterprise-wide or multi-division.
Purpose: Provide high-level framework and long-term directional guidance for executive decision-making.
Time Horizon: Long-term (typically 3 to 10 years).
Detail Level: Low detail, high abstraction.
Segment Architectures:
Scope: Major line of business, operating division, or cross-cutting functional domain (e.g., Global Supply Chain, Retail Banking).
Purpose: Direct program-level investments and align multiple projects within a business domain.
Time Horizon: Medium-term (typically 1 to 3 years).
Detail Level: Medium detail.
Capability Architectures:
Scope: Specific business capability or targeted IT service increment (e.g., Customer Identity Verification, Real-Time Payment Gateway).
Purpose: Guide individual projects or agile delivery iterations to realize immediate business outcomes.
Time Horizon: Short-term (typically 3 to 12 months).
Detail Level: High detail, highly specific.
Principles for Effective Partitioning
Clear Ownership: Assign dedicated lead architects and governance authorities to each partition.
Defined Boundaries: Ensure partitions are mutually exclusive and collectively exhaustive where possible to eliminate overlap.
Alignment to Metamodel: Maintain adherence to the central Architecture Metamodel so artifacts across different partitions can be integrated seamlessly.
Manage Cross-Partition Dependencies: Explicitly document dependencies between Capability Architectures and their parent Segment and Strategic Architectures.