The table describes the steps involved in Phase B (Business Architecture), Phase C (Information Systems Architectures), and Phase D (Technology Architecture) of the TOGAF ADM5. These phases are responsible for developing the target architectures for each domain and identifying the gaps between the baseline and target architectures. The table shows the outputs and outcomes of each phase, as well as the essential knowledge required for each phase.

The table describes the iterative cycle of defining requirements, identifying gaps, and creating solutions that occurs throughout the architecture development phases of the TOGAF ADM. This cycle is most prominent in:

Phase B (Business Architecture):

Develop the Business Architecture, identifying gaps between the baseline and desired business capabilities, processes, and information flows.

Define work packages to address these gaps and realize the target business architecture.

Phase C (Information Systems Architectures):

Develop the Data and Application Architectures to support the Business Architecture.

Identify gaps between the baseline and target information systems architectures.

Define work packages to address these gaps and realize the target data and application architectures.

Phase D (Technology Architecture):

Develop the Technology Architecture to support the Data and Application Architectures.

Identify gaps between the baseline and target technology architectures.

Define work packages to address these gaps and realize the target technology architecture.

Phase A (Architecture Vision) of the TOGAF ADM builds out initial organizational maps to understand high-level organizational needs and link them to architecture goals. This step provides foundational insight that informs subsequent phases, particularly for stakeholder alignment.

In the context of TOGAF and Business Architecture, the diagram depicts the relationship between a Value Stream, Value Stage, and Value.

Value Stream: Represents the end-to-end set of activities that create and deliver value to a stakeholder.

Value Stage: A distinct step or phase within the Value Stream.

Value: The benefit delivered to the stakeholder.

The relationship " X " indicates that a Value Stream is composed of multiple Value Stages.

Think of it like a journey (Value Stream) with multiple stops along the way (Value Stages). Each stage contributes to the overall value delivered at the end of the journey.

The diagram shows the Enterprise Continuum, which is a view of the Architecture Repository that provides methods for classifying architecture and solution artifacts as they evolve from generic Foundation Architectures to Organization-Specific Architectures4. The Enterprise Continuum comprises two complementary concepts: the Architecture Continuum and the Solutions Continuum. The Architecture Continuum shows the relationships among foundational frameworks, common system architectures, industry architectures, and enterprise architectures4. The Solutions Continuum shows the relationships among foundational solutions, common system solutions, industry solutions, and enterprise solutions4.