Gap Analysis in Phases B, C, and D

Gap Analysis in TOGAF 10 Foundation: Phases B, C, and D

Understanding Gap Analysis in TOGAF Architecture Development Method (ADM)

Gap Analysis is a critical component of the TOGAF 10 Foundation framework that involves identifying and documenting the differences between the current state (Baseline Architecture) and the desired future state (Target Architecture) across different architecture domains.

Why Gap Analysis is Important

Gap analysis serves several essential purposes in architecture development:

• Identifies Transition Requirements: It reveals what needs to change, be built, modified, or decommissioned to move from the baseline to the target architecture.
• Enables Prioritization: Gap analysis helps prioritize initiatives and projects based on their importance and dependencies.
• Supports Decision Making: It provides data-driven insights to inform architectural decisions and resource allocation.
• Manages Risk: Identifying gaps early allows organizations to anticipate challenges and plan mitigation strategies.
• Facilitates Communication: Gap analysis creates a common understanding among stakeholders about what architectural changes are necessary.
• Supports Business Alignment: It ensures that the architecture changes align with business strategy and objectives.

What is Gap Analysis?

Gap analysis is the systematic comparison and documentation of:

• Baseline Architecture: The current state of the architecture (as-is)
• Target Architecture: The desired future state of the architecture (to-be)
• Gaps: The specific differences, missing components, and required changes between baseline and target

Gaps can be categorized as:

• Positive Gaps: Capabilities or components in the target that are not in the baseline (new additions)
• Negative Gaps: Capabilities or components in the baseline that are not in the target (items to be removed or deprecated)
• Modified Gaps: Existing capabilities that need to be changed or enhanced

Gap Analysis in Phase B: Business Architecture

Purpose: Identify gaps between the current and target business architecture, including organizational structure, capabilities, processes, and functions.

Key Activities:

• Develop a comprehensive baseline business architecture describing the current state
• Define the target business architecture based on business strategy and vision
• Compare baseline and target to identify business capability gaps
• Document organizational capability gaps, process improvements needed, and functional changes required
• Analyze how business processes, functions, and roles need to evolve
• Identify dependencies and sequencing requirements

Outputs:

• Business Gap Analysis report
• List of business capabilities that need to be created, modified, or retired
• Business transformation roadmap
• Prioritized list of business initiatives

Gap Analysis in Phase C: Information Systems Architecture

Purpose: Identify gaps between current and target information systems, encompassing both data and application architectures.

Data Architecture Gaps (Phase C1):

• Compare baseline and target data models, data structures, and data management approaches
• Identify missing data entities, attributes, or relationships
• Assess data quality, governance, and integration requirements
• Document data migration and transformation needs
• Analyze data architecture changes required to support target business capabilities

Application Architecture Gaps (Phase C2):

• Compare baseline and target application portfolios
• Identify applications to be built, replaced, modified, or retired
• Assess application integration and interoperability requirements
• Analyze capability gaps where no applications currently exist
• Evaluate application performance, scalability, and technical debt issues
• Determine new application requirements and modifications to existing systems

Outputs:

• Data Architecture Gap Analysis
• Application Architecture Gap Analysis
• Application development and maintenance roadmap
• Data management requirements
• Prioritized list of application initiatives

Gap Analysis in Phase D: Technology Architecture

Purpose: Identify gaps between current and target technology infrastructure, including hardware, software, networks, and platforms.

Key Activities:

• Document baseline technology architecture (current infrastructure, platforms, tools)
• Define target technology architecture aligned with business and information systems requirements
• Compare baseline and target to identify technology gaps
• Assess infrastructure, platform, and tooling changes needed
• Identify technology upgrades, replacements, and new implementations required
• Analyze performance, capacity, security, and reliability gaps
• Document technology obsolescence and end-of-life issues

Outputs:

• Technology Architecture Gap Analysis report
• List of infrastructure components to be created, upgraded, or retired
• Technology roadmap and implementation plan
• Infrastructure modernization initiatives

How Gap Analysis Works Across Phases B, C, and D

Step 1: Establish Baselines

• Document the current state architecture in detail for each domain
• Involve subject matter experts to ensure accuracy and completeness
• Capture all existing capabilities, components, and systems

Step 2: Define Target Architectures

• Based on business strategy and requirements, define what the future state should be
• Ensure target architecture aligns with business drivers and vision
• Involve stakeholders in target definition to gain consensus

Step 3: Identify and Categorize Gaps

• Systematically compare baseline and target architectures
• Document each gap with clear descriptions and implications
• Categorize gaps by type (additions, deletions, modifications)
• Assess the impact and criticality of each gap

Step 4: Analyze Relationships and Dependencies

• Understand how gaps in one domain affect others
• Identify interdependencies between business, data, application, and technology gaps
• Determine sequencing and priority based on dependencies

Step 5: Develop Transition Strategies

• For each gap, determine how to bridge from baseline to target
• Create work packages and initiatives to address gaps
• Estimate effort, cost, and resources required
• Define timeline and sequencing for implementation

Step 6: Communicate and Validate

• Present gap analysis findings to stakeholders
• Obtain validation and buy-in from business and technical teams
• Refine gaps based on stakeholder feedback
• Document assumptions and constraints

Exam Tips: Answering Questions on Gap Analysis in Phases B, C, and D

Tip 1: Understand the Definition

Know that gap analysis is the comparison of baseline and target architectures to identify what needs to change. Be prepared to explain it in simple terms as the difference between where we are and where we want to be.

Tip 2: Remember the Purpose

Recognize that gap analysis identifies transition activities, business initiatives, development projects, and infrastructure changes. When asked why gap analysis is important, emphasize:

• Identifying required changes and initiatives
• Prioritizing work based on business value
• Understanding dependencies and sequencing
• Managing risk and complexity

Tip 3: Know Phase-Specific Applications

• Phase B: Gap analysis focuses on business capabilities, processes, functions, and organizational structure. Look for questions about business transformation.
• Phase C: Gap analysis addresses data models, applications, and information systems. Expect questions about application portfolio management and data architecture.
• Phase D: Gap analysis examines technology infrastructure, platforms, and tools. Watch for questions about technology obsolescence and infrastructure changes.

Tip 4: Distinguish Positive and Negative Gaps

Be clear about the types of gaps:

• Positive gaps = new capabilities needed (additions to baseline)
• Negative gaps = capabilities to remove or retire (deletions from baseline)
• Modifications = changes to existing capabilities

Exam questions might ask you to identify which type of gap a particular scenario represents.

Tip 5: Link Gap Analysis to Deliverables

Remember the outputs of gap analysis in each phase:

• Phase B: Business Gap Analysis, Business Transformation Roadmap
• Phase C: Data and Application Gap Analysis, Application Portfolio recommendations
• Phase D: Technology Gap Analysis, Technology Roadmap

If a question asks what document contains the results of gap analysis, think about which phase you're in.

Tip 6: Understand Dependencies and Sequencing

Gap analysis reveals not just what needs to change, but the order and dependencies. Be ready to explain how gaps in one architecture domain may constrain or enable gaps in another domain. For example, a business gap requiring new capabilities may drive application and technology gaps.

Tip 7: Connect to Business Drivers

Remember that gap analysis is not abstract—it's driven by business strategy and objectives. Questions may ask why a particular gap exists or why a target architecture looks a certain way. The answer relates back to business drivers and strategic goals.

Tip 8: Practice Identifying Gaps in Scenarios

Exam questions often present scenarios with descriptions of baseline and target architectures. Practice identifying gaps by asking yourself:

• What exists in the target that doesn't exist in the baseline?
• What exists in the baseline that doesn't exist in the target?
• What needs to be changed in existing components?
• What are the dependencies and sequencing considerations?

Tip 9: Use Clear Language

When answering gap analysis questions, use precise terminology:

• Say baseline architecture for current state, not as-is alone
• Say target architecture for desired state, not to-be alone
• Refer to gaps rather than differences in formal contexts
• Use capability when discussing business, data, application, and technology capabilities

Tip 10: Remember the Iterative Nature

Gap analysis may be refined as you progress through the ADM phases. Early gap analyses may be high-level and revised as more detail emerges. Be prepared for questions about how gap analysis is refined or enhanced in later phases.

Tip 11: Connect Gap Analysis to Transition Planning

Understand that gap analysis directly informs the transition planning in Phase E (Opportunities and Solutions) and Phase F (Migration Planning). If asked about the output of gap analysis, recognize it leads to architecture initiatives and work packages.

Tip 12: Practice with Examples

Review typical business scenarios and practice identifying:

• Business capability gaps (Phase B)
• Data and application gaps (Phase C)
• Technology infrastructure gaps (Phase D)

For example: If a company's target architecture requires a customer data warehouse that doesn't exist in the baseline, that's a positive application and data architecture gap that requires a new system development initiative.

Common Exam Question Types on Gap Analysis

Type 1: Definition Questions

Example: What is the primary purpose of gap analysis in TOGAF ADM?

Answer Strategy: Focus on identifying the differences between baseline and target architectures, determining what needs to change, and enabling prioritization of architectural initiatives.

Type 2: Phase-Specific Questions

Example: Which of the following is typically identified during gap analysis in Phase C?

Answer Strategy: Match the gap type to the phase. Phase C gaps are about data and applications, so look for answers involving systems, data models, and application portfolios.

Type 3: Scenario-Based Questions

Example: A company currently has three separate customer databases but wants to consolidate into one unified data warehouse. What type of gap is this?

Answer Strategy: This is a modification gap (changes to existing data architecture) combined with a positive gap (new unified system). Be prepared to explain the implications and transition activities.

Type 4: Output/Deliverable Questions

Example: What is the primary output of gap analysis in Phase D?

Answer Strategy: The Technology Gap Analysis report and Technology Roadmap are the main outputs, identifying infrastructure components to be created, upgraded, or retired.

Summary

Gap analysis in TOGAF Phases B, C, and D is a systematic, structured approach to identifying what must change for an organization to achieve its target architecture. It is the bridge between understanding the current state and planning the transition to the future state. For exam success, understand its purpose in each phase, recognize the types of gaps, know the key outputs, and practice applying gap analysis concepts to realistic scenarios.