Introduction

Phase C of the TOGAF Architecture Development Method (ADM) focuses on developing the Information Systems Architectures, which include both Data and Application Architectures. This phase ensures that the architectures support the Business Architecture and the Architecture Vision, addressing the business goals and strategic drivers identified in previous phases. The following guide explains the key deliverables required to be completed within this phase and provides steps to complete them.

Deliverables

1. Architecture Definition Document

Objective: Provide a detailed definition of the Information Systems Architectures, including baseline and target architectures for both Data and Application Architectures.

Description: The Architecture Definition Document is a comprehensive document that defines the Information Systems Architectures in detail. It includes descriptions of the baseline architecture (current state) and the target architecture (future state) for both Data and Application Architectures.

Steps to Complete:

  1. Define Baseline Architecture:
    • Gather Information: Collect data on the current data and application systems, including databases, applications, and their interactions.
    • Analyze Current State: Evaluate the gathered data to understand the current Information Systems Architectures.
    • Document Baseline: Create a detailed description of the baseline architecture for both Data and Application Architectures.
  2. Define Target Architecture:
    • Identify Goals: Determine the business goals and strategic drivers that the target architecture should support.
    • Develop Future State: Create a detailed description of the target architecture that aligns with the business goals and strategic drivers.
    • Document Target Architecture: Include the future state description in the Architecture Definition Document.
  3. Consolidate Information:
    • Combine Descriptions: Combine the baseline and target architecture descriptions into a single document.
    • Review and Validate: Ensure that the document is accurate and complete.
    • Get Approval: Present the Architecture Definition Document to stakeholders and obtain approval.
  4. Communicate Document: Share the Architecture Definition Document with the Enterprise Architecture team and other relevant stakeholders.

2. Architecture Requirements Specification

Objective: Specify the requirements for the Information Systems Architectures, including functional and non-functional requirements for both Data and Application Architectures.

Description: The Architecture Requirements Specification document outlines the detailed requirements for the Information Systems Architectures. It includes functional requirements (what the architecture should do) and non-functional requirements (how the architecture should perform).

Steps to Complete:

  1. Identify Requirements:
    • Engage Stakeholders: Work with stakeholders to understand their needs and expectations.
    • Document Functional Requirements: Specify what the Information Systems Architectures should do to support business goals.
    • Document Non-Functional Requirements: Specify how the Information Systems Architectures should perform, including performance, security, and scalability requirements.
  2. Consolidate Requirements:
    • Combine Requirements: Combine all identified requirements into a single document.
    • Review Requirements: Ensure that the requirements are complete, accurate, and aligned with business goals.
    • Prioritize Requirements: Assign priorities to the requirements based on their importance and impact.
  3. Document Specification:
    • Include All Requirements: Ensure that the document includes all functional and non-functional requirements.
    • Get Approval: Present the Architecture Requirements Specification to stakeholders and obtain approval.
  4. Communicate Specification: Share the Architecture Requirements Specification with the Enterprise Architecture team and other relevant stakeholders.

3. Architecture Roadmap

Objective: Develop a roadmap that outlines the steps to transition from the baseline to the target Information Systems Architectures.

Description: The Architecture Roadmap is a strategic plan that outlines the steps, milestones, and timelines for transitioning from the current state (baseline architecture) to the desired future state (target architecture) for both Data and Application Architectures.

Steps to Complete:

  1. Identify Transition Steps:
    • Define Milestones: Establish key milestones and deliverables for the transition.
    • Develop Timeline: Create a timeline for the transition, including start and end dates for each step.
  2. Develop Roadmap:
    • Include Dependencies: Identify and document any dependencies between the transition steps.
    • Assign Resources: Determine the resources required for each step and assign them accordingly.
  3. Document Roadmap:
    • Create Roadmap Document: Create a formal Architecture Roadmap document.
    • Review Roadmap: Ensure that the roadmap is complete, accurate, and aligned with business goals.
    • Get Approval: Present the Architecture Roadmap to stakeholders and obtain approval.
  4. Communicate Roadmap: Share the Architecture Roadmap with the Enterprise Architecture team and other relevant stakeholders.

4. Architecture Building Blocks

Objective: Define the reusable components (Building Blocks) that will be used to construct the Information Systems Architectures.

Description: Architecture Building Blocks (ABBs) are reusable components that can be used to construct the Information Systems Architectures. They include data models, application components, and integration services.

Steps to Complete:

  1. Identify Building Blocks:
    • Define Data Models: Identify the data models that are required to support the target architecture.
    • Define Application Components: Identify the application components that are required to support the target architecture.
    • Define Integration Services: Identify the integration services that are required to support the target architecture.
  2. Document Building Blocks:
    • Include All Components: Ensure that the document includes all identified data models, application components, and integration services.
    • Review Building Blocks: Ensure that the Building Blocks are complete, accurate, and aligned with business goals.
  3. Get Approval: Present the Architecture Building Blocks to stakeholders and obtain approval.
  4. Communicate Building Blocks: Share the Architecture Building Blocks with the Enterprise Architecture team and other relevant stakeholders.

Key Concepts

  • Architecture Definition Document: A detailed definition of the Information Systems Architectures, including baseline and target architectures for both Data and Application Architectures.
  • Architecture Requirements Specification: A document outlining the detailed requirements for the Information Systems Architectures.
  • Architecture Roadmap: A strategic plan outlining the steps, milestones, and timelines for transitioning from the baseline to the target architectures for both Data and Application Architectures.
  • Architecture Building Blocks: Reusable components used to construct the Information Systems Architectures, including data models, application components, and integration services.

Conclusion

Phase C of the TOGAF ADM is crucial for developing the Information Systems Architectures that support the Business Architecture and the Architecture Vision. By completing the key deliverables—Architecture Definition Document, Architecture Requirements Specification, Architecture Roadmap, and Architecture Building Blocks—organizations can ensure that their Information Systems Architectures are aligned with business goals and strategic drivers. This phase sets the foundation for successful architecture development and deployment, driving business value and transformation.

References

Leave a Reply

Your email address will not be published. Required fields are marked *