Comprehensive Guide to Phase C: Information Systems Architectures in TOGAF ADM

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 Statement of Architecture Work and stakeholder concerns. The Data and Application Architectures can be developed sequentially or concurrently, depending on the project’s requirements.

Data Architecture

Objectives and Steps

1. Develop the Target Data Architecture

Objective: Create a Target Data Architecture that enables the Business Architecture and the Architecture Vision, addressing the Statement of Architecture Work and stakeholder concerns.

Steps:

• Identify Candidate Architecture Roadmap Components: Based on the gaps between the Baseline and Target Data Architectures, identify components for the Architecture Roadmap.
• Follow Phase B Steps: Refer to the steps outlined in Phase B (Table 6) for detailed guidance on developing the Data Architecture.

Inputs and Outputs

Inputs

1. Architecture Reference Materials:
   • Use architecture reference materials to guide the development of the Data Architecture.
2. Request for Architecture Work:
   • The initial request that triggers the architecture development process.
3. Capability Assessment:
   • An evaluation of the organization’s current capabilities.
4. Communications Plan:
   • A plan for communicating the architecture vision and progress to stakeholders.
5. Organizational Model for Enterprise Architecture:
   • The organizational structure and roles involved in the Enterprise Architecture.
6. Tailored Architecture Framework:
   • The customized architecture framework used for the project.
7. Data Principles:
   • The guiding principles for the Data Architecture.
8. Statement of Architecture Work:
   • The approved document that outlines the scope, objectives, and deliverables of the architecture project.
9. Architecture Vision:
   • The comprehensive vision for the future state of the enterprise architecture.
10. Architecture Repository:
    • Existing architecture documentation, including framework descriptions, architecture descriptions, and baseline descriptions.
11. Draft Architecture Definition Document:
    • A preliminary document that may include baseline and/or target architectures of any architectural domain.
12. Draft Architecture Requirements Specification:
    • Includes gap analysis results and relevant technical requirements.
13. Business Architecture Components of an Architecture Roadmap:
    • Components of the Architecture Roadmap that outline the steps to transition from the Baseline to the Target Business Architecture.

Outputs

1. Refined and Updated Versions of the Architecture Vision Phase Deliverables:
   • Updated deliverables from the Architecture Vision phase, including the Statement of Architecture Work and validated or new data principles.
2. Draft Architecture Definition Document:
   • Includes:
     • Baseline Data Architecture
     • Target Data Architecture
     • Views corresponding to the selected viewpoints, addressing key stakeholder concerns
3. Draft Architecture Requirements Specification:
   • Includes:
     • Gap analysis results
     • Data interoperability requirements
     • Relevant technical requirements that will apply to this evolution of the architecture development cycle
     • Constraints on the Technology Architecture
     • Updated business requirements
     • Updated application requirements
4. Data Architecture Components of an Architecture Roadmap:
   • Components of the Architecture Roadmap that outline the steps to transition from the Baseline to the Target Data Architecture.

Application Architecture

Objectives and Steps

1. Develop the Target Application Architecture

Objective: Create a Target Application Architecture that enables the Business Architecture and the Architecture Vision, addressing the Statement of Architecture Work and stakeholder concerns.

Steps:

• Identify Candidate Architecture Roadmap Components: Based on the gaps between the Baseline and Target Application Architectures, identify components for the Architecture Roadmap.
• Follow Phase B Steps: Refer to the steps outlined in Phase B (Table 6) for detailed guidance on developing the Application Architecture.

Inputs and Outputs

Inputs

1. Architecture Reference Materials:
   • Use architecture reference materials to guide the development of the Application Architecture.
2. Request for Architecture Work:
   • The initial request that triggers the architecture development process.
3. Capability Assessment:
   • An evaluation of the organization’s current capabilities.
4. Communications Plan:
   • A plan for communicating the architecture vision and progress to stakeholders.
5. Organizational Model for Enterprise Architecture:
   • The organizational structure and roles involved in the Enterprise Architecture.
6. Tailored Architecture Framework:
   • The customized architecture framework used for the project.
7. Application Principles:
   • The guiding principles for the Application Architecture.
8. Statement of Architecture Work:
   • The approved document that outlines the scope, objectives, and deliverables of the architecture project.
9. Architecture Vision:
   • The comprehensive vision for the future state of the enterprise architecture.
10. Architecture Repository:
    • Existing architecture documentation, including framework descriptions, architecture descriptions, and baseline descriptions.
11. Draft Architecture Definition Document:
    • A preliminary document that may include baseline and/or target architectures of any architectural domain.
12. Draft Architecture Requirements Specification:
    • Includes gap analysis results and relevant technical requirements.
13. Business and Data Architecture Components of an Architecture Roadmap:
    • Components of the Architecture Roadmap that outline the steps to transition from the Baseline to the Target Business and Data Architectures.

Outputs

1. Refined and Updated Versions of the Architecture Vision Phase Deliverables:
   • Updated deliverables from the Architecture Vision phase, including the Statement of Architecture Work and validated or new application principles.
2. Draft Architecture Definition Document:
   • Includes:
     • Baseline Application Architecture
     • Target Application Architecture
     • Views corresponding to the selected viewpoints, addressing key stakeholder concerns
3. Draft Architecture Requirements Specification:
   • Includes:
     • Gap analysis results
     • Application interoperability requirements
     • Relevant technical requirements that will apply to this evolution of the architecture development cycle
     • Constraints on the Technology Architecture
     • Updated business requirements
     • Updated data requirements
4. Application Architecture Components of an Architecture Roadmap:
   • Components of the Architecture Roadmap that outline the steps to transition from the Baseline to the Target Application Architecture.

Key Concepts

• Data Architecture: The structure and management of an organization’s data resources and data management resources.
• Application Architecture: The behavior and interactions of applications within the enterprise architecture.
• Baseline Architecture: The current state of the architecture.
• Target Architecture: The desired future state of the architecture.
• Gap Analysis: The process of identifying the differences between the Baseline and Target Architectures.
• Architecture Roadmap: A plan that outlines the steps to transition from the Baseline to the Target Architecture.
• Stakeholder Review: The process of presenting the architecture to stakeholders for feedback and approval.

Conclusion

Phase C of the TOGAF ADM is essential for developing the Information Systems Architectures, including Data and Application Architectures. By following the outlined steps and utilizing the necessary inputs, organizations can create detailed architectures that support the Business Architecture and the Architecture Vision. The outputs of this phase provide a clear roadmap for transitioning from the current state to the desired future state, ensuring alignment with business objectives and strategic initiatives.

References

• Powerful TOGAF ADM Toolset 1.
• TOGAF ADM Software 2.
• Best TOGAF Software with Agile & UML – Visual Paradigm Enterprise 3.
• TOGAF ADM Software: Act and Generate ADM Deliverables 4.
• The Best TOGAF Software 5.
• TOGAF® Tool for Enterprise Architecture – ArchiMetric .
• Visual Paradigm TOGAF ADM Tool: Empowering Your Enterprise Architecture Teams – Visual Paradigm Guides .
• TOGAF ADM Tutorial .
• Step-by-Step Enterprise Architecture Tutorial with TOGAF .
• Streamline Your Enterprise Architecture with Visual Paradigm’s TOGAF ADM Tools – Visual Paradigm Guides .