Information mapping is beneficial in identifying and highlighting the information requirements and flows that are not currently addressed by the existing business architecture. This helps in ensuring that all necessary information needed for business operations is captured, and that the architecture can support the business in decision-making and process execution.

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.

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 enterprisearchitectures4. The Solutions Continuum shows the relationships among foundational solutions, common system solutions, industry solutions, and enterprise solutions4.