Study guide
1.3 Enterprise Architecture in Practice: Context, Scope, and Architecture Domains
TOGAF Enterprise Architecture Practitioner OGEA-103
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Mechanics & Foundation Overview
1.1 OGEA-103 Exam Structure, Gradient Scoring & Open-Book Strategy 1.2 The TOGAF Standard 10th Edition Structure & Core Concepts 1.3 Enterprise Architecture in Practice: Context, Scope, and Architecture Domains 1.4 The Context for Enterprise Architecture: Purpose, Capability, Security, and the Digital Enterprise
2 Chapter 2: Preliminary Phase & Establishing the EA Capability
2.1 Preliminary Phase Objectives, Inputs, and Activities 2.2 Scope of the Enterprise and Defining the Architecture Footprint 2.3 Establishing Architecture Governance, Frameworks, and Tools
3 Chapter 3: Architecture Vision & Stakeholder Management (Phase A)
3.1 Phase A Objectives, Request for Architecture Work, and Scope Definition 3.2 Stakeholder Management: Identification, Classification, the Power/Interest Grid, and the Stakeholder Map 3.3 Business Scenarios Technique for Problem Definition and Requirements Elicitation 3.4 Architecture Vision, Communications Plan, and Statement of Architecture Work Approval
4 Chapter 4: Business Architecture (Phase B)
4.1 Phase B Objectives, Steps, and Business Modeling Approaches 4.2 Business Capabilities, Capability Mapping, and Assessment 4.3 Value Streams, Value Stream Mapping, and Capability Cross-Mapping 4.4 Business Architecture Artifacts, Gap Analysis, and Architecture Definition Document Updates
5 Chapter 5: Information Systems Architectures — Data Architecture (Phase C)
5.1 Phase C Data Architecture Objectives, Approach, and Data Principles 5.2 Conceptual, Logical, and Physical Data Models and Data Management 5.3 Data Entity/Business Function Matrix, Data Architecture Gap Analysis, and Interoperability Requirements
6 Chapter 6: Information Systems Architectures — Application Architecture (Phase C)
6.1 Phase C Application Architecture Objectives, Approach, and Baseline vs. Target First 6.2 Application Portfolio Rationalization, Component Modeling, and Application Integration 6.3 Application/Organization Matrix, Application Gap Analysis, and Boundary Definitions
7 Chapter 7: Technology Architecture (Phase D)
7.1 Phase D Objectives, Cloud & Modern Platforms, and Technology Principles 7.2 Technology Standards, the Standards Library, Platform Services, and Infrastructure Modeling 7.3 Technology Gap Analysis, Non-Functional Requirements, and Reference Models
8 Chapter 8: Opportunities and Solutions (Phase E)
8.1 Phase E Objectives, Consolidated Gap Analysis, and Work Package Formulation 8.2 Architecture Building Blocks (ABBs) to Solution Building Blocks (SBBs) Transition 8.3 Transition Architectures, Incremental Delivery, and Dependency Analysis 8.4 Architecture Roadmap Development and Trade-Off Analysis 8.5 Business Transformation Readiness Assessment and Risk Management
9 Chapter 9: Migration Planning (Phase F)
9.1 Phase F Objectives, Stakeholder Collaboration, and Governance Alignment 9.2 Business Value Assessment, Cost-Benefit Analysis, and Risk/Feasibility Scoring 9.3 Implementation and Migration Plan Deliverable, Resource Allocation, and Transition Roadmaps
10 Chapter 10: Implementation Governance (Phase G)
10.1 Phase G Objectives, Implementation Governance Structure, and Project Architecture Hand-off 10.2 Architecture Contracts: Purpose, Types, Timing, and Stakeholder Commitments 10.3 Architecture Compliance Reviews: Conformance Levels, Process, Timing, and Checklists
11 Chapter 11: Architecture Change Management (Phase H) & Requirements Management
11.1 Phase H Objectives, Drivers of Architecture Change, and Value Monitoring 11.2 Change Classification: Simplification, Incremental, and Re-Architecting Changes 11.3 Ongoing Governance, Retirement of Solutions, and Maintenance vs. New ADM Cycle 11.4 Requirements Management: Central Role, Traceability, Mid-Phase Discovery, and Scope Conflict
12 Chapter 12: Architecture Governance, Boards, and Dispensations
12.1 Architecture Governance Framework, Organizational Roles, and RACI Matrix 12.2 Architecture Board Structure, Federation, Responsibilities, and Meeting Operations 12.3 Compliance Assessment, Dispensation Process, Expiration, and Remediation Tracking 12.4 Architecture Principles, the Decision Log, and Resolving Principle Conflicts
13 Chapter 13: Architecture Content Framework & Architecture Repository
13.1 The TOGAF Content Framework and Enterprise Metamodel 13.2 Deliverables, Artifacts (Catalogs, Matrices, Diagrams), and Building Blocks (ABBs vs SBBs) 13.3 Architectural Views, Viewpoints, Stakeholder Concerns, and ISO/IEC/IEEE 42010 13.4 The Enterprise Continuum and the TOGAF 10 Architecture Repository
14 Chapter 14: EA Capability, Tailoring, and Iteration
14.1 Tailoring the ADM: Enterprise Context, Process Weight, and Agile Integration 14.2 ADM Iteration Cycles, Levels, and Classes of Architecture Engagement 14.3 Architecture Maturity Models, Capability Assessment, and EA Performance Measures 14.4 Supporting the ADM Work: The TOGAF Library, Series Guides, Patterns, and Security
1.3 Enterprise Architecture in Practice: Context, Scope, and Architecture Domains
Key Takeaways Explain This Topic AI
Enterprise Architecture encompasses four primary domains—Business, Data, Application, and Technology (BDAT)—that link business strategy to technical execution.
Business Architecture is the foundational domain that establishes governance, organizational structures, business capabilities, and value streams to steer all downstream technology choices.
Information Systems Architectures divide into Data Architecture (structuring logical and physical assets and flows) and Application Architecture (defining component boundaries and interfaces).
Scoping an enterprise architecture engagement requires defining boundaries across four specific dimensions: enterprise breadth, architecture depth, time horizon, and domain coverage.
Enterprise architecture operating models balance centralized architecture governance with federated delivery teams to maintain enterprise-wide coherence without stifling domain agility.
Last updated: October 2026
1.3 Enterprise Architecture in Practice: Context, Scope, and Architecture Domains
Enterprise Architecture (EA) is a strategic management discipline that translates business strategy into effective technical execution. Its primary objective is to optimize an organization's fragmented legacy of manual and automated processes into an integrated, change-responsive environment. To manage complexity across diverse organizational ecosystems, TOGAF structures architectural practice across four interconnected domains— Business, Data, Application, and Technology (BDAT) —while requiring architects to define boundaries across four essential scoping dimensions.
The Four Architecture Domains (BDAT)
The TOGAF Standard divides enterprise architecture into four foundational domains. These domains do not function as isolated silos; they represent integrated layers of organizational capability:
1. Business Architecture (Phase B)
Business Architecture is the anchor domain that guides all downstream technology decisions. It defines business strategy, governance, organizational structures, business capabilities, value streams, and critical business processes. In the TOGAF ADM, Business Architecture is developed first (Phase B) because technical systems cannot be meaningfully specified without first understanding the business outcomes they must deliver.
Key Business Architecture artifacts include:
Business Capability Maps : Hierarchical catalogs of what an enterprise does to create value, independent of how or by whom it is executed.
Value Stream Maps : End-to-end representations of how an organization delivers value to customers, from initial trigger to value realization.
Organization Maps : Models defining business units, functional roles, and partner relationships.
2. Data Architecture (Phase C)
Data Architecture describes the structure of an organization's logical and physical data assets and data management resources. It governs how information is organized, stored, secured, and shared across systems. In modern data-driven enterprises, Data Architecture establishes master data models, metadata schemas, and data governance policies.
Key Data Architecture artifacts include:
- Conceptual, Logical, and Physical Data Models
- Data Entity / Business Function Matrices
- Data Dissemination and Data Lifecycle Diagrams
- 3. Application Architecture (Phase C)
Application Architecture provides a blueprint for individual applications, their interactions, and their alignment with core business processes. Rather than designing internal software code, it defines application boundaries, logical services, integration APIs, and application portfolio rationalization.
Key Application Architecture artifacts include:
- Application Portfolio Catalogs
- Application / Function Matrices
- Application Communication and Interface Diagrams
- 4. Technology Architecture (Phase D)
Technology Architecture defines the infrastructure platforms and technologies required to support business, data, and application services. It encompasses cloud infrastructure (IaaS/PaaS), on-premises compute, storage networks, operating environments, virtualization layers, and telecommunications networks.
Key Technology Architecture artifacts include:
- Technology Standards Catalogs
- Platform Decomposition Diagrams
- Network and Environments Diagrams
- Interplay and Bidirectional Alignment
While the ADM follows a sequential progression from Business (Phase B) to Technology (Phase D), enterprise architecture operates bidirectionally in practice:
Top-Down Strategic Realization : Executive business vision drives capability requirements, which dictate application services and data models, which in turn define infrastructure specifications.
Bottom-Up Technological Enablement : Innovations in infrastructure (such as edge computing, machine learning platforms, or serverless models) create opportunities to invent new business capabilities and business models that executives previously could not conceive.
Defining Enterprise Context and Organizational Boundaries
A critical task in the Preliminary Phase and Phase A is establishing the precise boundaries of the enterprise undergoing architecture work. Organizations often attempt to model the entire corporation at once—a pitfall known as "boiling the ocean." The TOGAF Standard clarifies that an enterprise can be scoped down to an operating unit, a shared service department, or a supply chain network, provided it has:
- Common strategic business goals
- Clear administrative and budgetary authority to execute architecture decisions
- Defined interfaces with external systems and organizations
- The Four Dimensions of Architecture Scoping
To ensure initiatives remain achievable and aligned with stakeholder commitments, TOGAF defines four dimensions of architecture scope , agreed in Phase A and recorded in the Statement of Architecture Work:
Scoping Dimension Focus and Boundary Questions Practical Example
1. Enterprise Breadth Which business units, geographical regions, subsidiaries, or partner networks are included? "Retail banking operations in North America, excluding commercial lending and wealth management."
2. Architecture Depth What level of detail is required? Strategic architecture (executive roadmaps), Segment architecture (domain programs), or Capability architecture (project delivery)? "Segment-level architecture for customer onboarding, without defining physical microservice code schemas."
3. Time Horizon What temporal period is being planned across baseline (Year 0), transition states (Years 1-2), and target vision (Years 3-5)? "A 36-month transformation featuring a 12-month hybrid cloud transition state and a 36-month target serverless state."
4. Architecture Domains Which of the BDAT domains are actively under design or revision during this ADM cycle? "Phases B (Business) and C (Data) are in full scope to ensure regulatory compliance; Technology infrastructure remains unchanged."
Architecture Operating Models & Team Structures
Organizations structure their enterprise architecture practices using different operating models based on size and governance maturity:
Centralized Model : A single enterprise architecture office defines all standards, creates all architectures, and reviews all projects. While this ensures high consistency and reduces duplicative spending, it often creates bottlenecks that delay agile teams.
Decentralized (Siloed) Model : Independent architects report exclusively to business unit managers. This provides high responsiveness to local business needs, but leads to duplicated software, fragmented data silos, and technical debt.
Federated Model : Combines the strengths of both models. TOGAF notes that large enterprises such as governments and conglomerates typically use federated architectures, integrated through common principles for interoperability and conformance. A central Enterprise Architecture Office establishes overarching principles, core standards, repository structures, and governance rules. Embedded domain architects work directly within business units and agile teams, designing solutions within enterprise guardrails.
Governance Oversight: The Architecture Board
Architecture practices require governance to ensure adherence to standards. The Architecture Board is a cross-functional governing body comprising business leaders, technology executives, and lead architects. Key responsibilities include:
- Reviewing and approving Architecture Contracts
- Conducting Architecture Compliance Reviews at major delivery milestones
- Adjudicating principle conflicts between business units
Granting formal, time-limited Architecture Dispensations when projects cannot comply with standards due to exceptional business constraints
Architecture Anti-Patterns in Practice
Ivory Tower Architecture : Producing elaborate conceptual models that ignore the practical constraints of software development and operations teams.
Boiling the Ocean : Attempting to document 100% of baseline systems before making strategic decisions. Baseline modeling should only proceed to the depth needed to identify gaps and guide target state decisions.
Bypassing Business Architecture : Jumping directly from a technology mandate (such as cloud migration) into Phase D infrastructure design without first evaluating business capabilities, value streams, or organizational readiness.