Study guide
13.4 The Enterprise Continuum and the TOGAF 10 Architecture Repository
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
13.4 The Enterprise Continuum and the TOGAF 10 Architecture Repository
Key Takeaways Explain This Topic AI
TOGAF describes the Enterprise Continuum as a view of the Architecture Repository showing evolution from generic to specific, abstract to concrete, and logical to physical.
The Architecture Continuum and Solutions Continuum each run from Foundation through Common Systems and Industry to Organization-Specific.
The TOGAF 10 Architecture Repository's eight classes are the Architecture Metamodel, Architecture Capability, Architecture Landscape, Standards Library, Reference Library, Governance Repository, Architecture Requirements Repository, and Solutions Landscape.
The Architecture Landscape is divided into Strategic, Segment, and Capability Architectures; Capability Architectures describe capability increments used to group work packages.
Reference architectures, reference models, a viewpoint library, and templates belong in the Reference Library, while the Governance Repository holds the decision log, compliance assessments, and related records.
Last updated: November 2026
13.4 The Enterprise Continuum and the TOGAF 10 Architecture Repository
The Enterprise Continuum and the Architecture Repository appear in the Level 1 "Concepts" and "Architecture Content" areas. The Level 2 outcomes ask you to know how a repository can be structured using the TOGAF repository, what to expect in a well-run Architecture Repository, and how architecture levels organize the Architecture Landscape. This section uses the TOGAF Standard, 10th Edition names. TOGAF 9.1 material describes only six repository classes, and TOGAF 9.x material uses the older names Standards Information Base and Governance Log .
The Enterprise Continuum
TOGAF describes the Enterprise Continuum as a view of the Architecture Repository that shows the evolution of related architectures from generic to specific, from abstract to concrete, and from logical to physical . It is a way of classifying architecture and solution assets so architects can find and reuse them, and it gives a common language for discussing them.
It has two related continua:
- Architecture Continuum Solutions Continuum
- Foundation Architectures Foundation Solutions
- Common Systems Architectures Common Systems Solutions
- Industry Architectures Industry Solutions
- Organization-Specific Architectures Organization-Specific Solutions
Moving left to right (from Foundation to Organization-Specific), architectures address enterprise needs in decreasing abstraction . Architects typically find more reusable elements toward the Foundation end. When an element is missing, the requirement is passed back toward the generic end so that it can be incorporated there for future reuse. The Architecture Continuum also serves as a classification scheme for the Reference Library . The Solutions Continuum classifies the solutions that realize architectures. Within each level of the Architecture Landscape, the Architecture Continuum divides architectures by abstraction.
The Architecture Repository
TOGAF explains that a mature Architecture Capability produces a huge volume of output. Managing and reusing it requires a formal taxonomy of architectural assets plus processes and tools for storing them. The Architecture Repository is one part of the wider Enterprise Repository , which also links to detailed design, deployment, and service management repositories.
The Eight Classes of Information
Repository area What it holds
Architecture Metamodel The organizationally tailored application of the framework, including the method for architecture development and the metamodel for architecture content
Architecture Capability The parameters, structures, and processes that support governance of the Architecture Repository
Architecture Landscape An architectural representation of assets in use, or planned, at particular points in time
Standards Library The standards with which new architectures must comply: industry standards, selected products and services from suppliers, or shared services already deployed
Reference Library Guidelines, templates, patterns, and other reference material that accelerate the creation of new architectures
Governance Repository A record of governance activity across the enterprise
Architecture Requirements Repository A view of all authorized architecture requirements agreed with the Architecture Board
Solutions Landscape An architectural representation of the Solution Building Blocks that support the Architecture Landscape and have been planned or deployed
Inside the Key Areas
Architecture Landscape. The landscape is divided into three levels of granularity:
Strategic Architectures show a long-term summary view of the entire enterprise and support direction setting at an executive level.
Segment Architectures give more detailed operating models for areas within the enterprise and are used at program or portfolio level.
Capability Architectures show in more detail how the enterprise can support a particular unit of capability: current capability, target capability, and capability increments , so that work packages and projects can be grouped into portfolios and programs.
Reference Library. Materials come from standards bodies, product and service vendors, industry communities and forums, standard templates, and enterprise best practice. It should contain reference architectures, reference models, a viewpoint library, and templates . TOGAF notes that reference architecture and reference model have the same relationship as architecture and model, and that either can be generic or organization-specific. Its examples include the IT4IT Reference Architecture and the TM Forum eTOM and SID.
Standards Library. Standards are classed as legal and regulatory obligations, industry standards, and organizational standards . They move through a lifecycle: Proposed, Provisional (Trial), Standard (Active), Phasing-Out (Deprecated), and Retired (Obsolete). They are classified by the building blocks of the Enterprise Metamodel and by domain: business, data, applications, and technology standards (Section 7.2).
Governance Repository. It holds a decision log (product selections, justifications for major architectural features, standards deviations, standards lifecycle changes, Change Request evaluations, and reuse assessments), compliance assessments , capability assessments , a calendar of in-flight projects and reviews, the project portfolio under governance, and performance measurement for the architecture function.
Architecture Requirements Repository. It is used by all ADM phases and managed by Requirements Management . Requirements are held at strategic, segment, and capability levels, and once their business outcomes are reflected in the Solutions Landscape they are archived for audit.
Solutions Landscape. It holds the SBBs (products or services) that support the specified ABBs, categorized by the Enterprise Continuum or as Strategic, Segment, or Capability SBBs. It does not include the information and data that the solutions themselves produce.
TOGAF also mentions external repositories : external reference models, external standards (ISO, IEEE, government), and Architecture Board approvals. Board minutes are often held in documentation archives outside the Architecture Repository for legal or regulatory reasons.
Continuum Versus Repository
The Enterprise Continuum is a classification view : it organizes assets from generic to specific, abstract to concrete, and logical to physical.
The Architecture Repository is the store that holds the assets, organized into the eight classes above.
The Reference Library uses the Architecture Continuum as its classification scheme, and the Architecture Landscape uses levels plus the Architecture Continuum. That is why the two concepts are often taught together.
Common Exam Traps
Using TOGAF 9 names. In the 10th Edition the store of standards is the Standards Library, and governance records live in the Governance Repository.
Putting industry reference models in the Architecture Landscape. Generic or industry reference material belongs in the Reference Library; the Landscape holds the enterprise's own architectures at points in time.
Forgetting the Solutions Landscape and Requirements Repository. The 10th Edition repository has eight classes, not six.
Confusing the Architecture Capability area with the Architecture Metamodel area. The Capability area holds the parameters, structures, and processes that govern the repository; the Metamodel area holds the tailored method and content metamodel.