en_US

Comprehensive Guide to Architecture Deliverables in TOGAF

Introduction

In the realm of enterprise architecture, the concept of architecture deliverables plays a crucial role in ensuring that architectural efforts are well-documented, reviewed, and aligned with organizational goals. The TOGAF (The Open Group Architecture Framework) provides a structured approach to managing these deliverables, ensuring consistency and clarity in architectural work products. This article will delve into the key aspects of architecture deliverables within the TOGAF framework, their significance, and provide practical examples to illustrate their application.

Understanding Architecture Deliverables

Definition

Architecture deliverables are formally specified work products that are contractually agreed upon, reviewed, and signed off by stakeholders. They represent the tangible outputs of architecture projects and are typically archived upon completion or transitioned into an Architecture Repository as a reference model, standard, or snapshot of the Architecture Landscape at a point in time.

Key Characteristics

  1. Formal Specification: Architecture deliverables are contractually specified and undergo a formal review and approval process. This ensures that they meet the required standards and align with stakeholder expectations.
  2. Project Output: They are the tangible outputs of architecture projects, providing a record of the architectural decisions, designs, and implementations.
  3. Archival or Transition: Upon completion, deliverables can be archived or transitioned into the Architecture Repository, where they serve as a reference for future projects.
  4. Multiple Artifacts: A single deliverable may contain multiple artifacts, such as catalogs, matrices, and diagrams, which describe various aspects of the architecture.

Types of Artifacts

Artifacts are architectural work products that describe specific aspects of the architecture. They are generally classified into three categories:

  1. Catalogs: Lists of things, such as a catalog of applications, services, or data entities.
  2. Matrices: Tables that show relationships between things, such as a capability matrix or a dependency matrix.
  3. Diagrams: Visual representations of things, such as process flow diagrams, data flow diagrams, or use-case diagrams.

Building Blocks

Building blocks are reusable components of enterprise capability that can be combined with other building blocks to deliver architectures and solutions. They can be defined at various levels of detail and can relate to either “architectures” or “solutions.”

  1. Architecture Building Blocks (ABBs): Describe required capability and shape the specification of Solution Building Blocks (SBBs). For example, a customer services capability may be required within an enterprise, supported by multiple SBBs such as processes, data, and application software.
  2. Solution Building Blocks (SBBs): Represent components that will be used to implement the required capability. For example, a network is a building block that can be described through complementary artifacts and then put to use to realize solutions for the enterprise.

The Role of Architecture Deliverables in TOGAF

Structural Model

The TOGAF Architecture Content Framework provides a structural model for architectural content, allowing the major work products that an architect creates to be consistently defined, structured, and presented. This framework is designed to be used as a stand-alone framework for architecture within an enterprise, but it can also be mapped to other content frameworks, such as the Zachman Framework.

Relationship with the Architecture Repository

The Architecture Repository acts as a holding area for all architecture-related projects within an enterprise. It is a key component of the Enterprise Repository, which provides the capability to link architectural assets to components of the Detailed Design, Deployment, and Service Management Repositories. The relationships between deliverables, artifacts, and building blocks are illustrated in the following diagram:

 

Example: Architecture Definition Document

An Architecture Definition Document is a deliverable that documents an Architecture Description. This document contains a number of complementary artifacts that are architecture views of the building blocks relevant to the architecture. For example, a process flow diagram (an artifact) may be created to describe the target call handling process (a building block). This artifact may also describe other building blocks, such as the actors involved in the process (e.g., a Customer Services Representative). The relationships between deliverables, artifacts, and building blocks are illustrated in the following diagram:

Practical Example

Scenario: Implementing a Customer Relationship Management (CRM) System

Project Overview: A project is initiated to implement a new CRM system to enhance customer service and streamline sales processes.

Architecture Deliverables:

  1. Architecture Definition Document: This deliverable documents the overall architecture of the CRM system. It includes several artifacts that describe various aspects of the architecture.
    • Process Flow Diagram: A diagram that illustrates the target call handling process, including the steps involved and the actors (e.g., Customer Services Representative).
    • Use-Case Diagram: A diagram that describes the interactions between the CRM system and its users, highlighting the key use cases and actors.
    • Data Flow Diagram: A diagram that shows the flow of data within the CRM system, including the data entities and their relationships.
  2. Catalogs:
    • Application Catalog: A list of applications that are part of the CRM system, including their descriptions and functionalities.
    • Data Catalog: A list of data entities that are managed by the CRM system, including their attributes and relationships.
  3. Matrices:
    • Capability Matrix: A table that shows the capabilities of the CRM system and their relationships with business objectives.
    • Dependency Matrix: A table that illustrates the dependencies between different components of the CRM system.
  4. Building Blocks:
    • Customer Services Capability: An Architecture Building Block (ABB) that describes the required capability for customer services.
    • CRM Application: A Solution Building Block (SBB) that represents the application software used to implement the customer services capability.

Transition to the Architecture Repository

Upon completion of the project, the Architecture Definition Document and its constituent artifacts are formally reviewed, approved, and signed off by stakeholders. They are then transitioned into the Architecture Repository, where they serve as a reference for future projects. The building blocks, such as the Customer Services Capability and the CRM Application, are also stored in the repository and can be reused in other projects.

Roadmap to TOGAF ADM Deliverables

The TOGAF Architecture Development Method (ADM) is a comprehensive approach to developing and managing enterprise architecture. Each phase of the ADM produces specific deliverables that are crucial for the successful implementation of the architecture. This guide will describe the key deliverables required in each phase of the TOGAF ADM.

Preliminary Phase

Deliverables:

  1. Tailored Architecture Framework: A customized version of the TOGAF framework tailored to the specific needs of the organization.
  2. Organizational Model for Enterprise Architecture: A model that defines the roles, responsibilities, and structure of the enterprise architecture function within the organization.
  3. Architecture Principles: A set of principles that guide the architecture development process, ensuring alignment with business objectives and strategic goals.
  4. Business Principles, Goals, and Drivers: The foundational business principles, goals, and drivers that inform the architecture development process.
  5. Request for Architecture Work: A formal request to initiate an architecture project, outlining the scope, objectives, and expected outcomes.

Phase A: Architecture Vision

Deliverables:

  1. Statement of Architecture Work: A detailed description of the architecture work to be performed, including the scope, objectives, and deliverables.
  2. Architecture Vision: A high-level description of the target architecture, outlining the business value and key capabilities to be delivered.
  3. Communications Plan: A plan for communicating the architecture vision and progress to stakeholders.
  4. Capability Assessment: An assessment of the organization’s current capabilities and the gaps that need to be addressed.
  5. Architecture Definition Document: A document that describes the architecture vision, including the business scenario, stakeholders, and architecture principles.

Phase B: Business Architecture

Deliverables:

  1. Architecture Definition Document: An updated document that includes the business architecture, describing the business strategy, governance, organization, and key business processes.
  2. Architecture Requirements Specification: A detailed specification of the business requirements that the architecture must address.
  3. Architecture Roadmap: A high-level plan outlining the steps and milestones for developing the business architecture.
  4. Architecture Building Blocks: Reusable components of business capability that can be combined to deliver the business architecture.

Phase C: Information Systems Architectures

Deliverables:

  1. Architecture Definition Document: An updated document that includes the information systems architectures, describing the data and application architectures.
  2. Architecture Requirements Specification: A detailed specification of the information systems requirements that the architecture must address.
  3. Architecture Roadmap: A high-level plan outlining the steps and milestones for developing the information systems architectures.
  4. Architecture Building Blocks: Reusable components of information systems capability that can be combined to deliver the information systems architectures.

Phase D: Technology Architecture

Deliverables:

  1. Architecture Definition Document: An updated document that includes the technology architecture, describing the hardware, software, and network infrastructure.
  2. Architecture Requirements Specification: A detailed specification of the technology requirements that the architecture must address.
  3. Architecture Roadmap: A high-level plan outlining the steps and milestones for developing the technology architecture.
  4. Architecture Building Blocks: Reusable components of technology capability that can be combined to deliver the technology architecture.

Phase E: Opportunities and Solutions

Deliverables:

  1. Architecture Definition Document: An updated document that includes the opportunities and solutions identified during the architecture development process.
  2. Architecture Building Blocks: Reusable components of capability that can be combined to deliver the identified opportunities and solutions.
  3. Architecture Roadmap: A high-level plan outlining the steps and milestones for implementing the identified opportunities and solutions.
  4. Solution Building Blocks: Components that will be used to implement the required capability.
  5. Implementation and Migration Plan: A detailed plan for implementing and migrating to the new architecture.
  6. Transition Architecture: A description of the architecture that will support the transition from the baseline to the target architecture.
  7. Implementation Governance Model: A model that defines the governance structure and processes for implementing the architecture.

Phase F: Migration Planning

Deliverables:

  1. Architecture Roadmap: An updated roadmap that includes the detailed migration plan.
  2. Implementation and Migration Plan: A detailed plan for implementing and migrating to the new architecture.
  3. Transition Architecture: An updated description of the architecture that will support the transition from the baseline to the target architecture.
  4. Implementation Governance Model: An updated model that defines the governance structure and processes for implementing the architecture.

Phase G: Implementation Governance

Deliverables:

  1. Implementation Governance Model: A model that defines the governance structure and processes for implementing the architecture.
  2. Architecture Contracts: Agreements between the architecture function and other parts of the organization, defining the scope and deliverables of the architecture development.
  3. Change Request: A formal request for changes to the architecture, outlining the scope, objectives, and expected outcomes.
  4. Compliance Assessment: An assessment of the architecture’s compliance with standards, regulations, and business objectives.

Phase H: Architecture Change Management

Deliverables:

  1. Implementation Governance Model: An updated model that defines the governance structure and processes for managing changes to the architecture.
  2. Architecture Contracts: Updated agreements between the architecture function and other parts of the organization, defining the scope and deliverables of the architecture development.
  3. Change Request: Updated formal requests for changes to the architecture, outlining the scope, objectives, and expected outcomes.
  4. Compliance Assessment: Updated assessments of the architecture’s compliance with standards, regulations, and business objectives.
  5. Request for Architecture Work: Updated formal requests to initiate architecture projects, outlining the scope, objectives, and expected outcomes.
  6. Requirements Impact Assessment: An assessment of the impact of changes to the architecture requirements.
  7. ADM Architecture Requirements Management: A process for managing the architecture requirements throughout the ADM lifecycle.
  8. Architecture Requirements Specification: An updated specification of the architecture requirements that the architecture must address.

Conclusion

Architecture deliverables are essential components of the TOGAF framework, providing a structured approach to documenting, reviewing, and managing architectural work products. They ensure consistency, clarity, and alignment with organizational goals, and serve as a valuable reference for future projects. By understanding the key characteristics, types, and practical applications of architecture deliverables, organizations can effectively leverage the TOGAF framework to enhance their enterprise architecture capabilities.

This comprehensive guide has provided an in-depth overview of architecture deliverables within the TOGAF framework, their significance, and practical examples to illustrate their application. By following this guide, organizations can ensure that their architectural efforts are well-documented, reviewed, and aligned with strategic objectives.

The TOGAF ADM provides a structured approach to developing and managing enterprise architecture, with each phase producing specific deliverables that are crucial for the successful implementation of the architecture. By understanding the key deliverables required in each phase, organizations can ensure that their architectural efforts are well-documented, reviewed, and aligned with strategic objectives. This comprehensive guide has provided an overview of the TOGAF ADM deliverables, their significance, and their role in the architecture development process.

Reference List for ArchiMate and TOGAF

  1. TOGAF® Tool for Enterprise Architecture – ArchiMetric
    • Description: This resource provides an overview of TOGAF ADM and how Visual Paradigm supports the development of TOGAF deliverables using ArchiMate diagrams.
    • URL: TOGAF® Tool for Enterprise Architecture
  2. Navigating the Evolution: A Comprehensive Guide to ArchiMate 2.1 to 3.2 – ArchiMetric
  3. Mastering Enterprise Architecture with Visual Paradigm’s TOGAF Tool – ArchiMetric
  4. What is ArchiMate? – Visual Paradigm
    • Description: A step-by-step learning guide on ArchiMate, its integration with TOGAF, and how it complements existing methods like UML and BPMN.
    • URL: What is ArchiMate?
  5. Using BPMN to Supplement TOGAF ADM EA Development Together with ArchiMate – ArchiMetric
  6. Understanding Abstraction in the ArchiMate Language – ArchiMetric
  7. An Overview of ArchiMate – the Enterprise Architecture Modeling Language – Cybermedian
    • Description: This overview discusses ArchiMate’s integration with TOGAF and other frameworks, and the benefits of using Visual Paradigm for ArchiMate modeling.
    • URL: An Overview of ArchiMate
  8. Deal with Enterprise Complexity with Visual Paradigm Just-in-Time Process – ArchiMetric
  9. Visual Paradigm TOGAF – Everything about TOGAF, Enterprise Architecture, ArchiMate, and more
    • Description: This guide provides an in-depth look at ArchiMate 3, TOGAF, and enterprise architecture, and how Visual Paradigm supports these frameworks.
    • URL: Visual Paradigm TOGAF
  10. Free Online ArchiMate Tool + Examples – Cybermedian
    • Description: This resource offers free online ArchiMate tools and examples, highlighting the integration of ArchiMate with TOGAF and the support provided by Visual Paradigm.
    • URL: Free Online ArchiMate Tool + Examples

These references provide a comprehensive overview of ArchiMate and TOGAF, their integration, and the tools available on Visual Paradigm to support enterprise architecture modeling.

Leave a Reply