TOGAF Phases

This is just a summary for a quick check but the details should be checked at The TOGAF® Standard, Version 9.2 (opengroup.org) 

Requirements management process

• The management of architecture requirements throughout the ADM cycle

Preliminary Phase

• Establish the Organizational Model for enterprise architecture

Defining "where, what, why, who, and how we do architecture" in the enterprise concerned. The main aspects are as follows:

• Defining the enterprise.

• Identifying key drivers and elements in the organizational context.

• Defining the requirements for architecture work. select and implement tools to support the Architecture Capability

• Defining the Architecture Principles that will inform any architecture work.

• Defining the framework to be used.

• Defining the relationships between management frameworks.

• Evaluating the Enterprise Architecture maturity.

• Output: Request for Architecture Work

A. Architecture Vision

• Business Scenarios does recommend for use in developing an Architecture Vision document

• Establish the Architecture Project

• Identify Stakeholders, Concerns, and Business Requirements

• Confirm and Elaborate Business Goals, Business Drivers, and Constraints

• Evaluate Capabilities

• Assess Readiness for Business Transformation

• Define Scope

• Confirm and Elaborate Architecture Principles, including Business Principles

• Develop Architecture Vision

• Define the Target Architecture Value Propositions and KPIs

• Identify the Business Transformation Risks and Mitigation Activities

• Develop Statement of Architecture Work; Secure Approval

Phases B, C, and D (BDAT)

• Select Reference Models, Viewpoints, and Tools.

• Develop Baseline Business/Data/Application/Technology Architecture Description.

• Develop Target Business/Data/Application/Technology Architecture Description.

• Perform Gap Analysis.

• Define Candidate Roadmap Components.

• Resolve Impacts Across the Architecture Landscape.

• Conduct Formal Stakeholder Review.

• Finalize the Business/Data/Application/Technology Architecture.

• Create the Architecture Definition Document (Draft). It acts as a deliverable container for artifacts created during a project.

Phase E: Opportunities and Solutions

• Building blocks become implementation-specific.

• Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value.

• Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D

• Phase E is the initial step on the creation of the Implementation and Migration Plan which is completed in Phase F. It provides the basis of a well considered Implementation and Migration Plan that is integrated into the enterprise's portfolio in Phase F.

• Output: Architecture Definition Document(Final)

Phase F: Migration Planning

• Coordinate the Implementation and Migration Plan with other frameworks

• Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan.

• Ensure that the Implementation and Migration Plan is co-ordinated with the enterprise’s approach to managing and implementing change in the enterprise’s overall change portfolio.

• Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders.

• The output is - Impact Analysis (see Impact Analysis) - detailed Implementation Plan and Migration Plan (including Architecture Implementation Contract, if appropriate)

Phase G: Implementation Governance

• To verify that the method is being applied correctly.

• To ensure that implementation projects conform with the Target Architecture.

• ensure conformance with the defined architecture by the implementation projects.

• Output: Architecture Contract, Change Requests

Phase H: Architecture change management

• Ensure that the architecture lifecycle is maintained

• Ensure that the Architecture Governance Framework is executed

• Ensure that the Enterprise Architecture Capability meets current requirements

• Process are below

  • a "simplification change" to an architecture is often driven by a requirement to reduce investment

  • an "incremental change" is driven by a requirement to derive additional value from existing investment

  • a "re-architecting change" is driven by a "requirement to increase investment in order to create new value for exploitation

  • ensure that the architecture achieves its original target business value