Overview Knowledge-Based Study

Study notes

1. Purpose and Concept

   In the TOGAF Standard, 10th Edition, the Architecture Repository serves as the central information holding area for all architectural assets, outputs, and governance records within an enterprise. Rather than existing as a single monolithic database, it represents a conceptual model and structural framework for categorizing, storing, managing, and retrieving both internal architectural work products and external reference resources.

   The primary objectives of the Architecture Repository include:

   • Promoting reusability of architectural artifacts, building blocks, and reference models across various initiatives.
   • Ensuring consistent governance, traceability, and compliance tracking throughout the Architecture Development Method (ADM) cycle.
   • Providing stakeholders with clear visibility into the current baseline, transition states, and target architecture landscape.

   The Architecture Repository is typically integrated into the broader Enterprise Repository, which also manages non-architectural assets such as the operational configuration management database (CMDB), requirements systems, and software repositories.

   Major Structural Areas

   The TOGAF Standard categorizes the contents of the Architecture Repository into six core structural components, each fulfilling a distinct role:

   • Architecture Metamodel: Defines the organizationally tailored framework elements, entity types, relationships, and constraints used to construct architecture models.
   • Architecture Capability: Stores the parameters, policies, processes, skills, and governance structures that define and enable the architectural practice itself.
   • Architecture Landscape: Contains architectural representations of the enterprise in use or planned at specific points in time, typically organized into Strategic, Segment, and Capability architectures.
   • Standards Information Base (SIB): Captures the explicit standards, industry specifications, and regulatory constraints with which new architectures and solution implementations must comply.
   • Reference Library: Holds reusable reference models, patterns, architectural templates, guidelines, and best practice materials drawn from both internal experience and recognized industry bodies.
   • Governance Log: Maintains an audit trail of governance actions, compliance assessments, dispensations, architecture board decisions, and operational SLA reviews.

   Levels of Granularity and Abstraction

   The Architecture Landscape component organizes active architectural assets into three distinct levels of granularity to balance breadth and depth:

   1. Strategic Architecture: Provides a high-level summary overview of the entire enterprise, establishing strategic direction, long-range roadmaps, and executive-level alignment across business capabilities.
   2. Segment Architecture: Focuses on a specific program, operating division, or major cross-functional business domain, translating strategic guidance into detailed domain frameworks.
   3. Capability Architecture: Delivers actionable, focused architectural definitions targeting a specific business capability, operational slice, or implementation increment.

   Maintaining these three discrete tiers enables architecture practitioners to avoid unnecessary detail at strategic levels while ensuring sufficient precision during solution delivery.

   Distinguishing Repository Components

   A common misconception in enterprise architecture is confusing the Standards Information Base (SIB) with the Reference Library, or confusing the Architecture Capability with the Governance Log.

   • The Reference Library contains aspirational and accelerators (patterns, guidelines, exemplar models) that teams can leverage optionally or adaptively.
   • The Standards Information Base sets mandatory or agreed compliance rules (approved technologies, interface protocols, legal regulations).
   • The Architecture Capability defines how the architecture team operates (roles, methods, organizational structures), whereas the Governance Log records the historical record of decisions and approvals.

   Knowledge Check Question

   An enterprise architecture team wants to examine previous formal approvals and dispensations granted for non-compliant software platforms over the past fiscal year. Which component of the Architecture Repository should they inspect?

   • A. Reference Library
   • B. Standards Information Base
   • C. Governance Log
   • D. Architecture Capability

   Correct Answer: C
   Explanation: The Governance Log is explicitly designated within the TOGAF Standard to record governance activity, audit records, decisions, agreed dispensations, and compliance assessments. The Standards Information Base lists the standards themselves, the Reference Library contains reusable templates and patterns, and the Architecture Capability defines the operating model of the architecture practice.