TOGAF 10 Foundation: Architecture Repository Guide

Architecture Repository in TOGAF 10 Foundation

Why the Architecture Repository is Important

The Architecture Repository is a critical component of enterprise architecture management. It serves as the central knowledge base for all architecture artifacts, standards, and best practices within an organization. Understanding its importance helps enterprises:

• Maintain consistency across architecture projects and initiatives
• Enable effective reuse of architecture components and patterns
• Facilitate knowledge sharing and collaboration among architecture teams
• Provide a single source of truth for architecture information
• Support governance and compliance requirements
• Enable continuous improvement through lessons learned

What is the Architecture Repository?

The Architecture Repository is a structured collection of architecture information and artifacts organized for easy access, retrieval, and reuse. According to TOGAF 10, it consists of several key components:

Core Components of the Architecture Repository

• Architecture Metamodel: Defines the structure and relationships of architecture artifacts
• Architecture Standards and Guidelines: Documented best practices and standards for the organization
• Reference Models: Pre-built architecture patterns and models that can be adapted for specific needs
• Architecture Building Blocks (ABBs): Reusable architecture components at a high level
• Solution Building Blocks (SBBs): Specific implementations of ABBs for particular solutions
• Governance Models and Frameworks: Standards for decision-making and oversight
• Architecture Landscape: Current and target state descriptions of the architecture
• Lessons Learned: Documentation of successes and failures from past projects

How the Architecture Repository Works

Functional Structure

The Architecture Repository operates through a layered approach:

1. Repository Foundation
The base layer includes the architecture metamodel that defines how all other elements relate to and organize within the repository. This metamodel ensures consistency and enables meaningful relationships between artifacts.

2. Architecture Landscape
Contains descriptions of the current state (Baseline) and future state (Target) of the enterprise architecture, organized by business capabilities and domains.

3. Standards, Reference Models, and Patterns
Provides pre-approved solutions that architects can leverage, including technology standards, architectural patterns, and reference implementations.

4. Building Blocks
ABBs and SBBs are organized and indexed to support rapid discovery and reuse across projects.

5. Governance and Compliance
Maintains records of governance decisions, compliance requirements, and approval workflows.

How Information Flows Through the Repository

• Creation: New architecture artifacts are created following established standards and metamodel guidelines
• Classification: Artifacts are classified and tagged according to the metamodel for easy retrieval
• Storage: Information is stored in a centralized, organized manner with version control
• Retrieval: Architects search and retrieve relevant artifacts and patterns for their projects
• Reuse: Existing solutions are adapted and reused to accelerate architecture development
• Maintenance: Regular updates ensure that repository content remains current and relevant
• Governance: Change control processes manage updates and ensure quality

Key Artifacts in the Architecture Repository

Architecture Building Blocks (ABBs)

ABBs are logical components that represent high-level business and technology capabilities. They are:

• Technology and vendor agnostic
• Reusable across multiple solutions
• Focused on capabilities rather than implementations
• Organized in catalogs and matrices for easy reference

Solution Building Blocks (SBBs)

SBBs are concrete implementations of ABBs. They:

• Reference specific technologies, products, or services
• Include configuration and implementation details
• Support specific projects and solutions
• Are more constrained than ABBs

Reference Models

Pre-built architecture models that provide patterns for common scenarios. Examples include:

• Technology Reference Models showing standard technology choices
• Business Process Models documenting standard processes
• Information Models defining data standards

How to Answer Questions Regarding Architecture Repository in an Exam

Typical Question Formats

Exam questions about the Architecture Repository typically fall into these categories:

1. Definition and Purpose Questions

Example: What is the primary purpose of the Architecture Repository?

How to Answer: The Architecture Repository is a structured collection of architecture information and artifacts that serves as a central knowledge base for enterprise architecture. It enables consistency, reuse, and governance across architecture initiatives. Key points to emphasize include knowledge management, standardization, and support for reuse of architecture components.

2. Component Identification Questions

Example: Which of the following is a component of the Architecture Repository?

How to Answer: Look for answers that mention: Architecture Metamodel, Reference Models, Building Blocks (ABBs and SBBs), Architecture Landscape, Standards and Guidelines, Governance Models, and Lessons Learned. Eliminate answers that refer to implementation details or specific vendor products.

3. Relationship and Function Questions

Example: How do Solution Building Blocks relate to the Architecture Repository?

How to Answer: Explain that SBBs are concrete implementations stored in the repository. They reference ABBs and provide specific vendor/technology solutions. Emphasize that they enable reuse and accelerate solution development by providing pre-approved implementations.

4. Scenario-Based Questions

Example: An architect needs to quickly develop a solution for a common business scenario. Where should they look first in the Architecture Repository?

How to Answer: Direct the architect to Reference Models and Solution Building Blocks that address the scenario. These provide pre-built, pre-approved solutions that can be adapted, accelerating the architecture development process.

Exam Tips: Answering Questions on Architecture Repository

Tip 1: Remember the Purpose vs. Implementation Distinction

The Architecture Repository itself is about knowledge management and governance, not about specific technology implementations. When answering, focus on how it supports organizational goals like consistency, reuse, and standards compliance—not on specific tools or products.

Tip 2: Understand the Hierarchy: ABBs and SBBs

This is a frequently tested concept. Remember:

• ABBs (Architecture Building Blocks): Logical, reusable, technology-independent
• SBBs (Solution Building Blocks): Concrete, implementation-specific, reference ABBs

If a question asks about logical components, answer ABB. If it asks about specific implementations, answer SBB.

Tip 3: Connect Repository Components to Business Value

Always think about how repository components support business outcomes. For instance, Reference Models enable faster solution development, SBBs reduce implementation risk, and Lessons Learned prevent repeated mistakes. Exam questions often test whether you understand the business benefit, not just the technical definition.

Tip 4: Focus on Reuse and Governance

Two core themes in Architecture Repository questions are:

• Reuse: How the repository enables architects to leverage existing solutions
• Governance: How the repository supports compliance, standards, and approval workflows

When unsure about an answer, consider whether it relates to one of these themes.

Tip 5: Know the Content Organization

The Architecture Repository organizes content in layers. Exam questions sometimes test understanding of what belongs at each layer:

• Foundation Layer: Architecture Metamodel
• Reference Content: Standards, Guidelines, Reference Models
• Repository Content: ABBs, SBBs, Governance Models
• Contextual Content: Architecture Landscape, Lessons Learned

Tip 6: Distinguish Repository from TOGAF ADM

The Architecture Repository supports the TOGAF Architecture Development Method (ADM) but is not the same thing. The repository stores outputs and artifacts from ADM phases, while the ADM is the process for developing architecture. If a question asks about storing or retrieving architecture information, think Repository. If it asks about the process of developing architecture, think ADM.

Tip 7: Understand Metadata and Classification

The Architecture Metamodel defines how artifacts are classified, tagged, and related. Questions about consistency, search capabilities, or artifact relationships are often testing your understanding of metamodel importance. Emphasize that the metamodel enables meaningful organization and retrieval.

Tip 8: Practice Scenario Application

When facing scenario questions, mentally walk through repository use:

1. Architect needs solution → Check Reference Models
2. Needs implementation → Look at relevant SBBs
3. Needs to ensure standards compliance → Review Standards and Guidelines
4. Wants to avoid past mistakes → Consult Lessons Learned

Tip 9: Remember That Repository is Living and Evolving

The Architecture Repository is not static. Content is continuously updated, new artifacts are added, and lessons are captured. If a question asks about maintaining relevance or continuous improvement, think about the repository's role in capturing and disseminating organizational learning.

Tip 10: Key Terms to Remember

Master these terms for exam success:

• Architecture Metamodel: The structural definition
• Reference Models: Pre-built patterns
• Architecture Building Blocks: Logical, reusable components
• Solution Building Blocks: Concrete implementations
• Architecture Landscape: Current and target state
• Governance Models: Decision and oversight frameworks
• Lessons Learned: Organizational memory and improvements

Common Exam Question Patterns and Answers

Pattern 1: "What would you store in the Architecture Repository?"

Correct Answer Elements: Standards, guidelines, reference models, ABBs, SBBs, architectural patterns, business processes, technology standards, governance policies, and lessons learned. Incorrect Elements: Specific project details unrelated to reuse, vendor marketing materials, implementation code.

Pattern 2: "When should an architect consult the Architecture Repository?"

Correct Answer: At the beginning of a new project to identify reusable components, reference models, and established standards. Also during project execution to ensure compliance and during lessons learned to capture and share knowledge.

Pattern 3: "How does the Architecture Repository support governance?"

Correct Answer: It maintains approved standards, reference models, and governance policies. It provides a mechanism for enforcing architectural decisions, tracking compliance, and ensuring consistency across initiatives.

Pattern 4: "What is the relationship between the Architecture Repository and the TOGAF ADM?"

Correct Answer: The ADM is the process for developing architecture, while the repository is where artifacts from ADM phases are stored and maintained. The repository provides input to ADM phases and captures outputs from them.

Final Preparation Checklist

Before your exam, ensure you can:

• Define the Architecture Repository and its primary purpose
• List and describe all major components (Metamodel, ABBs, SBBs, Reference Models, Standards, Governance, Landscape, Lessons Learned)
• Explain the difference between ABBs and SBBs with clear examples
• Describe how the repository supports reuse and governance
• Connect repository concepts to business value and organizational benefits
• Identify appropriate repository artifacts for given scenarios
• Distinguish between the repository and other TOGAF concepts like the ADM
• Understand metadata classification and search capabilities
• Recognize the repository's role in continuous improvement
• Apply repository concepts to multiple-choice questions and scenarios

Summary

The Architecture Repository is a cornerstone of enterprise architecture practice within TOGAF. It provides the organizational infrastructure for managing architectural knowledge, supporting reuse, enforcing standards, and capturing lessons learned. Success on exam questions about the repository requires understanding not just what it contains, but why each component is important and how it supports organizational architecture governance and delivery. Focus on reuse, governance, consistency, and organizational learning as you prepare, and you will confidently answer even complex scenario-based questions on this topic.