Governance Repository Knowledge-Based Study

Study notes

1. Introduction to the Governance Repository

   In the TOGAF Standard, 10th Edition, the Architecture Repository serves as the foundational information model holding all architectural assets across an enterprise. One of its vital structural components is the Governance Repository.

   The primary purpose of the Governance Repository is to store and maintain records of architecture governance activities across the organization. While areas such as the Architecture Landscape describe the enterprise as it is or will be, the Governance Repository provides auditability, accountability, and traceability for architectural decisions, dispensations, and organizational oversight throughout the ADM lifecycle.

   Key Information Stored in the Governance Repository

   The Governance Repository maintains evidentiary and operational records essential for managing architecture conformance and oversight. Key items typically held within this repository include:

   • Decision Logs: Documented formal decisions made by architecture boards, executive steering committees, or designated governing bodies regarding architectural direction and trade-offs.
   • Compliance Assessments: Formal reviews evaluating how effectively implementation projects adhere to defined enterprise architectures and standards.
   • Dispensation Requests and Records: Granted exceptions or temporary dispensations allowing projects to deviate from standard architecture criteria, complete with expiry dates and remediation plans.
   • Capability Assessments: Baselines and evaluations of organizational capability maturity required to execute architectures.
   • Governance Board Records: Agendas, minutes, and charter documentation reflecting the recurring activities of Architecture Boards.
   • Service-Level Agreements (SLAs) and Contracts: Internal or external operational agreements governing architecture services and ongoing conformance monitoring.

   Differentiating the Governance Repository from Other Repository Areas

   Understanding the boundaries between the Governance Repository and adjacent components of the Architecture Repository is essential for architectural governance:

   • Governance Repository vs. Standards Information Base (SIB): The SIB defines the actual standards, specifications, and guidelines that must be met. In contrast, the Governance Repository stores the results of measuring alignment against those standards, such as compliance assessments and approved dispensations.
   • Governance Repository vs. Architecture Landscape: The Architecture Landscape holds descriptions of deployed systems, applications, and business capabilities at varying levels of abstraction (Strategic, Segment, and Capability), whereas the Governance Repository records the management decisions and governance trail associated with those assets.
   • Governance Repository vs. Architecture Requirements Repository: The Requirements Repository stores agreed architecture requirements driving ADM iterations, while the Governance Repository captures validation that those requirements were governed properly during delivery.