The TOGAF Architecture Repository: Organizing Architecture Assets
After you've mapped your architecture entities using the Content Metamodel, you need a place to store them. This is where the Architecture Repository comes in.
In the world of Enterprise Architecture, information is your most valuable asset. But information that is scattered across different spreadsheets, emails, and outdated diagrams is useless. The TOGAF Architecture Repository is the central vault that organizes all your architecture-related data, standards, and governance records.
The Six Classes of the Architecture Repository
TOGAF defines six distinct classes that make up the repository. Each class has a specific purpose and holds different types of information.
1. Architecture Metamodel
Think of the Architecture Metamodel as the instructions for the rest of the repository. It defines what data you collect and how that data is structured. If you're using the standard TOGAF Content Metamodel, this is where it lives.
2. Architecture Capability
The Architecture Capability class contains information about the architecture team itself. This includes the team's charter, roles and responsibilities, skills and training records, and the governance structures they use to make decisions.
3. Architecture Landscape
The Architecture Landscape is the most active part of the repository. It contains the actual diagrams and documentation for your enterprise at different levels of detail.
- Strategic Architecture: High-level, enterprise-wide views.
- Segment Architecture: Detailed views of specific business units or programs.
- Capability Architecture: Granular designs for specific projects or solutions.
4. Reference Library
Architects don't need to reinvent the wheel. The Reference Library contains reusable design patterns, industry templates, and best-practice models that the architecture team can draw from when starting a new project.
5. Standards Information Base (SIB)
The Standards Information Base (SIB) is the rulebook. It contains the list of all approved standards the enterprise must follow. This includes technology standards (e.g., "All databases must be PostgreSQL"), security standards, and business standards.
6. Governance Log
The Governance Log is the historical record. It contains the outputs of all architecture governance activity, including:
- Minutes from the Architecture Board meetings.
- Compliance assessments.
- Approved architecture waivers (where a project was allowed to deviate from standards).
- Status reports on implementation projects.
Why a Central Repository is Vital for EA Success
A well-maintained Architecture Repository provides several critical benefits:
1. Single Source of Truth
No more arguments about which "v3_final_final.pdf" diagram is the current one. The repository ensures everyone is working from the same baseline.
2. Reusability
By storing reusable patterns in the Reference Library, you speed up new projects and ensure a consistent "look and feel" across the enterprise.
3. Impact Assessment
When something changes, you can use the repository to trace the impact. If a technology standard in the SIB is updated, you can instantly see which systems in the Architecture Landscape are now non-compliant.
4. Continuous Improvement
The Governance Log allows the architecture team to learn from past mistakes. By reviewing previous waivers and project outcomes, you can refine your standards and metamodels over time.
Summary
The TOGAF Architecture Repository is much more than a file server. It is a structured information environment that supports the entire architecture lifecycle. From the standards in the SIB to the detailed designs in the Landscape, the repository gives the architecture team the data they need to provide strategic value to the organization.
In our next post, we will look at the specific items generated during the ADM: TOGAF Artifacts and Deliverables — The Complete Architect’s Checklist.
This post is part of the TOGAF 9.2 Masterclass series. Don't forget to check out our previous post on The TOGAF Content Metamodel.