TOGAF ADM Architecture Deliverables

Introduction

The Architecture Deliverables in the TOGAF ADM (Architecture Development Method) are formal work products or documents that are typically consumed or produced during the different phases of the ADM cycle. These deliverables serve as artifacts that capture and communicate the outputs of various activities in the architecture development process. Below is a brief overview of some of the key deliverables mentioned in the provided information:

Architecture Building Blocks:

• Output from: Phases F and H
• Input to: Phases A, B, C, D, E

Architecture Contract:

• This is not tied to a specific phase but is a contractual agreement related to architecture.

Architecture Definition Document:

• Output from: Phases B, C, D, E, F
• Input to: Phases C, D, E, F, G, H

Architecture Principles:

• Preliminary Output/Input: Preliminary
• Output from/Input to: Phases A, B, C, D

Architecture Repository:

Preliminary Output/Input: Preliminary

Input to: Phases A, B, C, D, E, F, G, H

Requirements Management (Architecture Requirements Specification):

• Output from: Phases B, C, D, E, F
• Input to: Phases C, D

Architecture Roadmap:

• Output from: Phases B, C, D, E, F
• Input to: Phases B, C, D, E, F

Architecture Vision:

• Output from: Phases A, E
• Input to: Phases B, C, D, E, F, G, H

Business Principles, Business Goals, and Business Drivers:

• Preliminary Output/Input: Preliminary, Phases A, B
• Input to: Phases A, B

Capability Assessment:

• Output from: Phases A, E
• Input to: Phases B, C, D, E, F

Change Request:

• Output from: Phases F, G, H

Communications Plan:

• Output from: Phase A
• Input to: Phases B, C, D, E, F

Compliance Assessment:

• Output from: Phase G
• Input to: Phase H

Implementation and Migration Plan:

• Output from: Phases E, F
• Input to: Phase F

Implementation Governance Model:

• Output from: Phase F
• Input to: Phases G, H

Organizational Model for Enterprise Architecture:

• Preliminary Output/Input: Preliminary
• Input to: Phases A, B, C, D, E, F, G, H

Request for Architecture Work:

• Preliminary Output/Input: Preliminary, Phases F, H
• Input to: Phases A, G

Requirements Impact Assessment:

• Output from/Input to: Requirements Management

Solution Building Blocks:

• Output from: Phase G
• Input to: Phases A, B, C, D, E, F, G

Statement of Architecture Work:

• Output from/Input to: Phases A, B, C, D, E, F, G, H

Tailored Architecture Framework:

• Preliminary Output/Input: Preliminary, Phase A
• Input to: Phases A, B, C, D, E, F, G, H

These deliverables play a crucial role in documenting and communicating various aspects of the architecture development process and contribute to the success of the enterprise architecture initiative.

Fit the Architecture Deliverables into Development Phases

To complete a TOGAF ADM (Architecture Development Method) EA (Enterprise Architecture) project using the information provided, you can follow these steps:

Understand the Phases:

• Familiarize yourself with the different phases of the TOGAF ADM cycle, including Preliminary, A, B, C, D, E, F, G, and H.

Identify Project Inputs:

• Determine the inputs required for your specific project, considering factors such as business goals, drivers, and organizational context.

Use the Architecture Building Blocks:

• Leverage Architecture Building Blocks as outputs from Phases F and H. Ensure that these are used as inputs in subsequent phases (A, B, C, D, E) to build and refine the architecture.

Create and Manage Architecture Contracts:

• Establish and manage Architecture Contracts, understanding that these are not tied to specific phases but involve contractual agreements related to architecture work.

Develop the Architecture Definition Document:

• Use the Architecture Definition Document as an output from Phases B, C, D, E, F. Ensure that it captures and communicates the essential aspects of the architecture.

Define and Apply Architecture Principles:

• Develop and apply Architecture Principles throughout the Preliminary and early phases (A, B, C, D). Use them as guiding concepts for decision-making.

Establish and Manage the Architecture Repository:

• Begin building the Architecture Repository in the Preliminary phase and continue updating it as needed throughout the ADM cycle.

Manage Requirements:

• Manage architecture requirements by creating and updating the Architecture Requirements Specification in Phases B, C, D, E, F.

Create an Architecture Roadmap:

• Develop an Architecture Roadmap as an output from Phases B, C, D, E, F. This will provide a strategic plan for implementing the architecture.

Define and Communicate the Architecture Vision:

• Develop and communicate the Architecture Vision in Phases A, E, providing a clear picture of the desired future state.

Assess Business Principles, Goals, and Drivers:

• Assess and align with business principles, goals, and drivers in Preliminary and Phases A, B.

Conduct Capability Assessments:

• Conduct Capability Assessments in Phases A, E to understand the organization’s capabilities and align them with the architecture.

Handle Change Requests:

• Manage Change Requests as they arise in Phases F, G, H, ensuring that changes are evaluated and implemented effectively.

Develop a Communications Plan:

• Create a Communications Plan in Phase A to ensure effective communication throughout the project.

Assess Compliance:

• Assess compliance in Phase G to ensure that the architecture aligns with relevant standards and regulations.

Create Implementation and Migration Plans:

• Develop Implementation and Migration Plans in Phases E, F to guide the execution of the architecture.

Establish an Implementation Governance Model:

• Develop an Implementation Governance Model in Phase F to ensure effective oversight of the implementation.

Define the Organizational Model for Enterprise Architecture:

• Define the Organizational Model for Enterprise Architecture in the Preliminary phase and update it as needed throughout the project.

Submit Requests for Architecture Work:

• Submit Requests for Architecture Work in Preliminary, F, H to initiate and define architecture projects.

Perform Requirements Impact Assessment:

• Perform Requirements Impact Assessments as part of Requirements Management to understand the impact of changes.

Define Solution Building Blocks:

• Define Solution Building Blocks in Phase G to specify the building blocks needed to implement the architecture.

Create a Statement of Architecture Work:

• Develop a Statement of Architecture Work in Phases A, B, C, D, E, F, G, H to document the scope and objectives of the architecture project.

Tailor the Architecture Framework:

• Tailor the Architecture Framework in Preliminary and Phase A to align with the specific needs of the organization.

By following these steps and utilizing the identified deliverables in each phase, you can effectively navigate through the TOGAF ADM cycle and complete your Enterprise Architecture project. Keep in mind that the specific approach may vary based on the unique characteristics and requirements of your organization.

Deliverables and High-Level Timeline Across Development Phases

Let’s consider an example scenario for an Enterprise Architecture (EA) project, and structure the TOGAF deliverables into a development timeline across the TOGAF ADM phases. Below is a simplified table format:

Phase	Activities and Deliverables	Timeline
Preliminary	– Conduct initial stakeholder analysis and engagement.	Weeks 1-2
	– Define business principles, goals, and drivers.
	– Develop and document the tailored architecture framework.
	– Establish the Architecture Repository.
A. Vision	– Develop an Architecture Vision.	Weeks 3-4
	– Identify and engage key stakeholders.
	– Define and document the Request for Architecture Work.
B. Business	– Conduct capability assessment.	Weeks 5-6
	– Refine business principles and goals.
	– Develop Business Architecture components.
	– Create and update the Architecture Repository.
C. Information	– Develop Information Systems Architecture.	Weeks 7-8
	– Manage requirements and create Architecture Requirements Specification.
	– Develop the Architecture Definition Document.
	– Assess compliance with standards and regulations.
D. Technology	– Develop Technology Architecture.	Weeks 9-10
	– Refine and update the Architecture Repository.
	– Perform Requirements Impact Assessment.
E. Transition	– Develop Implementation and Migration Plan.	Weeks 11-12
	– Create Solution Building Blocks.
	– Finalize Architecture Definition Document.
F. Implementation	– Implement governance model.	Weeks 13-14
	– Address Change Requests.
	– Update the Architecture Repository.
	– Develop Implementation Governance Model.
G. Governance	– Evaluate compliance and perform compliance assessment.	Weeks 15-16
	– Develop Solution Building Blocks.
	– Update the Architecture Repository.
	– Handle Change Requests.
H. Optimization	– Evaluate and optimize the architecture.	Weeks 17-18
	– Review and update the Architecture Repository.
	– Finalize documentation, including Architecture Contracts.

This table provides a structured development timeline for the EA project, indicating the key activities and deliverables in each TOGAF ADM phase. The timeline is presented in a weekly format for illustration purposes, and the actual durations may vary based on the complexity and scope of the project. It’s essential to adapt the timeline and activities to the specific needs and constraints of the organization.

Summary

The TOGAF ADM (Architecture Development Method) is a structured approach for developing and managing enterprise architecture. The key deliverables, activities, and phases in a TOGAF EA project are as follows:

Preliminary Phase:

• Conduct stakeholder analysis and engagement.
• Define business principles, goals, and drivers.
• Develop a tailored architecture framework.
• Establish the Architecture Repository.

Phase A: Vision:

• Develop the Architecture Vision.
• Identify and engage key stakeholders.
• Define and document the Request for Architecture Work.

Phase B: Business Architecture:

• Conduct capability assessment.
• Refine business principles and goals.
• Develop Business Architecture components.
• Create and update the Architecture Repository.

Phase C: Information Systems Architecture:

• Develop Information Systems Architecture.
• Manage requirements and create Architecture Requirements Specification.
• Develop the Architecture Definition Document.
• Assess compliance with standards and regulations.

Phase D: Technology Architecture:

• Develop Technology Architecture.
• Refine and update the Architecture Repository.
• Perform Requirements Impact Assessment.

Phase E: Transition Planning:

• Develop Implementation and Migration Plan.
• Create Solution Building Blocks.
• Finalize Architecture Definition Document.

Phase F: Implementation Governance:

• Implement governance model.
• Address Change Requests.
• Update the Architecture Repository.
• Develop Implementation Governance Model.

Phase G: Architecture Change Management:

• Evaluate compliance and perform compliance assessment.
• Develop Solution Building Blocks.
• Update the Architecture Repository.
• Handle Change Requests.

Phase H: Architecture Optimization:

• Evaluate and optimize the architecture.
• Review and update the Architecture Repository.
• Finalize documentation, including Architecture Contracts.

Throughout the project, various deliverables are produced, such as Architecture Building Blocks, Architecture Contracts, Architecture Definition Document, Architecture Principles, Architecture Repository, and more. These deliverables serve as formal work products and provide a structured way to capture and communicate the outputs of different activities in the architecture development process.

The timeline for the project is dynamic and can vary based on the organization’s needs, project scope, and complexity. The structured approach of TOGAF ADM ensures that the enterprise architecture is developed systematically, aligning with business goals and adapting to changes effectively.