How do you use the Architecture Deliverables and the Architecture Contracts in TOGAF?

1 Architecture Deliverables

Architecture Deliverables are the outputs of the architecture work that document the architecture decisions, models, views, and specifications. They are organized into four categories: Baseline Architecture, Target Architecture, Transition Architecture, and Architecture Requirements. Each category has a set of deliverables that correspond to the phases of the Architecture Development Method (ADM), the core process of TOGAF. For example, the Architecture Vision document is a deliverable of the Preliminary Phase, while the Architecture Roadmap is a deliverable of the Transition Planning Phase. You can use the Architecture Deliverables to communicate the architecture to different stakeholders, validate the architecture against the business objectives, and guide the implementation and governance of the architecture.

2 Architecture Contracts

Architecture Contracts are formal agreements between the architecture team and the implementation team that define the scope, quality, and acceptance criteria of the architecture work. They are derived from the Architecture Requirements and the Architecture Roadmap, and they specify the roles, responsibilities, deliverables, and milestones of the implementation project. You can use the Architecture Contracts to ensure that the implementation team follows the architecture principles, standards, and guidelines, and that the architecture team monitors and reviews the implementation progress and outcomes. Architecture Contracts also help to manage the risks, issues, and changes that may arise during the implementation.

3 Architecture Content Framework

Architecture Content Framework is a TOGAF standard that defines the structure, content, and notation of the Architecture Deliverables and the Architecture Contracts. It consists of three components: the Architecture Content Metamodel, the Architecture Content Views, and the Architecture Content Correspondence. The Architecture Content Metamodel describes the types of architectural elements and their relationships, such as actors, functions, services, data, and applications. The Architecture Content Views define the ways of presenting the architecture information to different audiences, such as diagrams, matrices, catalogs, and reports. The Architecture Content Correspondence establishes the links and dependencies between different views and deliverables. You can use the Architecture Content Framework to ensure consistency, completeness, and accuracy of the architecture content, and to facilitate the reuse and integration of the architecture content across different domains and levels.

4 Architecture Deliverables and Architecture Contracts in Practice

To use the Architecture Deliverables and the Architecture Contracts effectively in TOGAF, you need to follow some best practices. First, you need to tailor the deliverables and the contracts to suit your specific context, scope, and objectives. You can use the TOGAF Content Metamodel Extensions to customize the metamodel for your industry, domain, or organization. You can also use the TOGAF Deliverable Templates to create your own deliverable documents based on the standard structure and content. Second, you need to involve the relevant stakeholders in the creation, review, and approval of the deliverables and the contracts. You can use the Stakeholder Map and the Communications Plan to identify and engage the stakeholders, and to ensure their feedback and buy-in. Third, you need to manage the lifecycle of the deliverables and the contracts throughout the ADM phases. You can use the Architecture Repository and the Change Management Process to store, update, and control the deliverables and the contracts, and to handle any changes that may affect them.

5 Benefits of Using Architecture Deliverables and Architecture Contracts

By utilizing the Architecture Deliverables and the Architecture Contracts in TOGAF, you can benefit in many ways. These include improving the quality and clarity of architecture work through a standard framework and format, enhancing alignment and collaboration between the architecture team and implementation team with clear expectations and agreements, increasing the value and impact of the architecture by demonstrating how it meets business needs and supports strategic goals, as well as reducing risks and costs by ensuring its feasibility, compliance, and governance.

6 Resources for Learning More

If you want to become more knowledgeable about how to use the Architecture Deliverables and the Architecture Contracts in TOGAF, there are many resources available. The TOGAF Standard Version 9.2 is the official source of information and guidance on TOGAF, which covers all aspects of the framework. The TOGAF Library provides a collection of reference materials and resources that support the TOGAF standard, including the Content Metamodel Extensions, the Deliverable Templates, and the Architecture Principles Catalog. Additionally, The Open Group Certification for TOGAF is a program that certifies your knowledge and skills in TOGAF. It offers two levels of certification: Foundation and Certified. You can prepare for the certification exams with online or classroom courses, or by self-study.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?