Phase E: Opportunities and Solutions

The Phase E, is where we come down to the ground level and start talking about implementation. The phases before this, look for the glorious "should be". This phase is where we start looking into how. This part of the TOGAF standard describes the process of identifying delivery vehicles (projects, programs, or portfolios) that can deliver the Target Architecture of previous phases.


The objective of this phase is to create an complete architecture roadmap. This is based on the gap analysis and candidate architecture roadmap components from Phases B, C, and D. Here, we determine whether an incremental approach is required. If the gap to cover is big enough to demand an incremental approach, we identify the Transition Architectures that will deliver continuous business value.

In this phase, we define the SBBs and ABBs required to realize the Target Architecture.


In order to achieve the above objectives, we need to follow these steps

  • Determine and confirm key corporate change attributes - the exact measurable attributes that need to change.
  • Determine the business constraints that we need to work along, for implementation of the defined architecture
  • Review and consolidate the results of gap analysis performed in the Phases B, C and D
  • Review and consolidate the requirements across related business functions and their interoperability
  • Refine and validate the dependencies
  • Confirm the readiness and risk for business transformation
  • Formulate the Implementation and Migration Strategy
  • Identify and group major work packages
  • Identify Transition Architectures
  • Create Architecture Roadmap & Implementation and Migration Plan


As one would expect, the Phase E requires all that was created in the previous phases, along with the relevant inputs from the enterprise.

  • Product Information
  • Request for Architecture Work (From Preliminary Phase)
  • Capability Assessment (From Phase A)
  • Communications Plan (From Phase A)
  • Planning Methodologies
  • Organizational Model for Enterprise Architecture (Preliminary Phase)
  • Governance Models and Frameworks
  • Tailored Architecture Framework (Preliminary Phase, Phase A)
  • Statement of Architecture Work (Phase A)
  • Architecture Vision (Phase A)
  • Architecture Repository (From enterprise, enriched by the previous phases)
  • Draft Architecture Definition Document (updated in Phases B, C, D)
  • Draft Architecture Requirements Specification (updated in Phases B, C, D)
  • Change Requests for existing programs and projects
  • Candidate Architecture Roadmap components (from Phases B, C, D)


The Phase E looks into what can be done and how. It updates and refines the outputs of the previous phases, with the considerations for practical implementation. The output of this phase is an input to the following phases that go about the details of implementation.

  • Statement of Architecture Work, updated if necessary
  • Architecture Vision, updated if necessary
  • Draft Architecture Definition Document, including Transition Architectures, number and scope, if any
  • Draft Architecture Requirements Specification
  • Capability Assessment, including Business Capability and IT Capability
  • Architecture Roadmap, including:
    • Work package portfolio
    • Identification of Transition Architectures, if any
    • Implementation recommendations
  • Implementation and Migration Plan (outline), including Implementation and Migration Strategy