Phase B develops the Business Architecture — documenting the As-Is (Baseline) state, defining the To-Be (Target) state, and performing Gap Analysis to identify what must change. Business Architecture always comes first in BDAT: you cannot design the technology before you understand the business.
Phase B: Business Architecture is the first of the four architecture development phases (B, C, D). It establishes WHAT the business does today (Baseline) and what it needs to do in the future (Target), then identifies the gaps between them.
- ▸📋 Develop Baseline Business Architecture (As-Is current state)
- ▸🎯 Develop Target Business Architecture (To-Be future state)
- ▸🔍 Perform Gap Analysis — compare Baseline to Target, identify differences
- ▸🗂️ Produce Business Architecture work products (catalogues, matrices, diagrams)
- ▸🔗 Start the Architecture Definition Document (Business Architecture section)
- ▸🗺️ Update the Architecture Roadmap with candidate components from Gap Analysis
- ▸📌 Conduct formal stakeholder review before proceeding to Phase C
Explore the DUK DWMS Business Architecture Gap Analysis — click each Target element to see how it maps from the Baseline:
Gap Analysis is performed in Phases B, C, AND D — one Gap Analysis per architecture domain (Business, Data/Application, Technology). All three Gap Analyses feed into Phase E (Opportunities & Solutions) which identifies work packages to close each gap.
Phase B produces three categories of architecture work products: Catalogues (lists), Matrices (relationships), and Diagrams (visual representations). These together constitute the Business Architecture section of the Architecture Definition Document.
- ▸📋 Catalogues: Organization/Actor, Driver/Goal/Objective, Role, Business Service, Business Function, Location, Process, Event
- ▸⬛ Matrices: Strategy/Capability matrix, Business Interaction matrix, Actor/Role matrix
- ▸📊 Diagrams: Business Footprint, Functional Decomposition, Goal/Objective/Service, Business Use Case, Process Flow, Event diagram
- ▸⚠️ These are ARTIFACTS — they are contained within the Architecture Definition Document DELIVERABLE
- ▸🔑 The difference: Artifact = a work product; Deliverable = a formally signed-off package containing artifacts
The order B → C → D in the ADM is deliberate and non-negotiable. Each layer depends on the one above it:
Every TOGAF architecture phase works with two states: the current Baseline Architecture (what exists today) and the Target Architecture (what the future state should look like). The Gap Analysis bridges them.
- ▸📍 Baseline Architecture = As-Is = current state snapshot (what exists RIGHT NOW)
- ▸🎯 Target Architecture = To-Be = desired future state (what we want to achieve)
- ▸🔍 Gap Analysis = Target minus Baseline = what must be ADDED, CHANGED, or REMOVED
- ▸🔄 Gap types: New (exists in Target only), Eliminated (exists in Baseline only), Transform (changed), Retained (unchanged)
- ▸📌 Transition Architecture = intermediate stepping stones between Baseline and Target (produced in Phase E)
- ▸⚠️ Exam trap: "Transition Architecture" is NOT the same as "Target Architecture"