Skip to main content

TOGAF Architecture Repository

 

Introduction

The Architecture Repository in TOGAF is a structured framework that stores all the artifacts, guidelines, and references required for enterprise architecture management. It is a centralized repository used throughout the enterprise to govern architecture development and ensure consistency and compliance across projects.


Purpose of the Architecture Repository

  • Centralized Storage: Provides a unified location for all architecture-related resources.
  • Governance: Ensures alignment with organizational goals, standards, and policies.
  • Reuse and Consistency: Facilitates reuse of artifacts and enforces consistent application of architectural principles.
  • Traceability: Links architecture work to business outcomes, enabling accountability.

Key Components of the Architecture Repository

The Architecture Repository is divided into six main areas:

  1. Architecture Metamodel:

    • Defines the structure of architecture descriptions, ensuring consistency.
    • Includes definitions of artifacts, relationships, and viewpoints.
  2. Architecture Capability:

    • Captures the resources needed to operate and manage the architecture function, such as policies, governance models, and roles.
    • Includes:
      • Governance Frameworks: Processes for compliance and decision-making.
      • Skills Database: Information about the capabilities of enterprise architecture personnel.
  3. Architecture Landscape:

    • Represents the current, target, and transitional states of the enterprise architecture.
    • Organized into:
      • Strategic Architecture: Long-term visions and roadmaps.
      • Segment Architecture: Focus on specific business areas or capabilities.
      • Capability Architecture: Details of projects and initiatives supporting capabilities.
  4. Reference Library:

    • A collection of reusable resources, such as templates, standards, and patterns.
    • Examples:
      • Technology standards (e.g., HTTP, RESTful APIs).
      • Industry models (e.g., TOGAF templates, BPMN models).
  5. Standards Information Base (SIB):

    • Repository of industry standards and regulatory requirements.
    • Ensures compliance with legal and technical obligations.
    • Examples:
      • GDPR for data protection.
      • ISO/IEC standards for IT systems.
  6. Governance Log:

    • Records decisions, approvals, and compliance checks for architecture work.
    • Provides traceability and auditability.

Architecture Repository and the ADM Cycle

The Architecture Repository is closely integrated with TOGAF’s Architecture Development Method (ADM). It supports each ADM phase by providing relevant resources and capturing outputs.

  1. Preliminary Phase:

    • Establishes and populates the repository with initial standards, principles, and reference materials.
  2. Phases A-F (Architecture Vision, Business/Data/Application/Technology Architecture, Opportunities and Solutions):

    • Uses the repository to draw reference models and templates.
    • Updates the repository with new artifacts, building blocks, and plans.
  3. Phases G-H (Implementation Governance, Architecture Change):

    • Tracks progress and ensures governance compliance using the Governance Log.
    • Stores as-built architecture in the Architecture Landscape.
  4. Requirements Management:

    • Links requirements to architecture artifacts in the repository, enabling traceability.