3.2 Business Architecture Scope, Strategy & Capability Mapping

3.2 Business Architecture Scope, Strategy & Capability Mapping

Executive Summary: Business Architecture forms the foundational domain of Enterprise Architecture in TOGAF. It structures business strategy, organizational models, and capability maps to ensure that subsequent Information Systems (Data and Applications) and Technology architectures directly support business objectives.

1. The Core Role of Business Architecture

In the TOGAF ADM, Business Architecture is developed in Phase B, but its strategic scoping begins in Phase A. It serves as the vital bridge between high-level corporate strategy and technical implementation.

Without a robust Business Architecture, IT transformations risk delivering technically sound systems that fail to address strategic business goals or operational realities.

Key Objectives of Business Architecture

• Articulate baseline and target operating models of the enterprise.
• Translate business strategy, goals, and drivers into actionable organizational models and capabilities.
• Define what the business does (Capabilities), who performs it (Organization), and how value is generated (Value Streams).
• Provide the structural context for Data Architecture, Application Architecture, and Technology Architecture.

---

2. Business Capability Mapping

Capability Mapping is one of the most important concepts introduced and emphasized in modern TOGAF standards (TOGAF Standard 10th Edition).

What is a Business Capability?

A Business Capability represents a particular ability or capacity that a business may possess or exchange to achieve a specific purpose or outcome.

The Fundamental Rule of Capability Mapping: A capability defines WHAT a business does, strictly separated from HOW it is achieved, WHO performs it, or WHERE / WHEN it is executed.

For example, "Customer Risk Assessment" is a business capability. It remains constant whether it is executed manually on paper by a loan officer in a local branch or automatically by an AI algorithm in the cloud.

Structure of a Business Capability Map

Capabilities are organized into a hierarchical, non-overlapping taxonomy, typically spanning 1 to 3 levels:

CUSTOMER MANAGEMENT (Level 1)
├── Customer Acquisition (Level 2)
│   ├── Campaign Execution (Level 3)
│   └── Lead Qualification (Level 3)
└── Customer Onboarding (Level 2)
    ├── Identity Verification (Level 3)
    └── Account Setup (Level 3)

Capability Heat Mapping

Architects use Heat Mapping on Capability Maps to visually communicate performance, maturity, or strategic gap analysis:

• Red / High Heat: Low maturity or severe performance gap in a strategically critical capability (requires urgent investment).
• Yellow / Medium Heat: Moderate performance gap or capability requiring minor enhancement.
• Green / Low Heat: High maturity capability operating effectively.

---

3. Organization Mapping

Organization Mapping describes the structural layout of the enterprise. It identifies organizational units, locations, relationships, and governance boundaries.

Elements of an Organization Map

• Organizational Units: Departments, business units, divisions, or external partner entities.
• Relationships: Reporting structures, collaborative partnerships, and governance linkages.
• Locations: Physical facilities, regional headquarters, or virtual operational hubs.

Organization Mapping vs Capability Mapping

While Organization Maps reflect who performs work within hierarchical reporting lines, Capability Maps reflect what the business is capable of doing. Organizational structures change frequently due to re-organizations or mergers, but Business Capability Maps remain highly stable over time.

---

4. Business Functions vs Business Processes

A frequent point of confusion on the TOGAF exam is the distinction between Business Functions, Business Capabilities, and Business Processes:

                       BUSINESS ARCHITECTURE ELEMENTS
 +-------------------------------------------------------------------------+
 | BUSINESS CAPABILITY: What we can do (e.g., Payment Processing)           |
 +-------------------------------------------------------------------------+
 | BUSINESS FUNCTION:   Group of skills/people (e.g., Accounts Payable Dept)  |
 +-------------------------------------------------------------------------+
 | BUSINESS PROCESS:    Step-by-step workflow (1. Receive invoice ->       |
 |                      2. Validate -> 3. Issue payment)                   |
 +-------------------------------------------------------------------------+

---

5. Linking Strategy & Goals to Architecture Domains

Business Architecture aligns the enterprise by creating explicit traceability from strategy down to technical implementation:

1. Strategic Goal: "Increase customer retention by 20% through digital channels."
2. Business Capability Impact: Enhance "Digital Self-Service Management" capability maturity from Level 2 to Level 4.
3. Value Stream Stage: Enable "Resolve Customer Query" stage in the "Customer Service" Value Stream.
4. Data Architecture Impact: Require real-time "Customer Interaction Data Entity".
5. Application Architecture Impact: Deploy a microservices-based Customer Portal Application.
6. Technology Architecture Impact: Scale Cloud Container Platform infrastructure.

---

Section Summary & Exam Focus

• Remember that a Business Capability defines WHAT a business does, independent of implementation, organization, or technology.
• Understand the 3 structural elements: Capability Maps (what), Organization Maps (who), and Value Streams / Processes (how).
• Know the differences between Capabilities, Functions, and Processes.