7.1 Business Architecture Domain: Functions, Processes & Value Streams
Key Takeaways
- Business Functions are stable, long-lived capability groupings organized by business purpose that remain invariant even during corporate reorganizations.
- Business Processes represent sequential, operational workflows that transform specific inputs into measurable business outputs through event-driven activities.
- Organization Units describe the structural arrangement of human resources, departments, and reporting chains, requiring explicit mapping to capabilities and processes to define operational accountability.
- Value Streams articulate end-to-end value delivery to key internal or external stakeholders, establishing strategic business context for capability and process modeling.
- The TOGAF Series Guide: Business Architecture provides standardized modeling frameworks including Capability Maps, Organization Maps, Product Maps, and Value Stream Maps to align business strategy with IT execution.
7.1 Business Architecture Domain: Functions, Processes & Value Streams
Business Architecture represents the foundational domain of the TOGAF Architecture Development Method (ADM), developed primarily within Phase B (Business Architecture). It describes the enterprise target state from the perspective of key business strategy, governance, organization, and core business processes. A thorough, well-structured Business Architecture is essential because information systems, software applications, data entities, and technical infrastructure exist solely to support and enable the business capabilities and value propositions of the enterprise.
Without a clear Business Architecture, IT transformations risk building highly efficient technical solutions that solve the wrong business problems. Business Architecture serves as the vital translation layer between high-level corporate strategy (defined in Phase A) and technical implementation (defined in Phases C and D).
Core Constructs of Business Architecture
To construct an accurate Business Architecture model, TOGAF architects must clearly distinguish between four fundamental domain constructs: Business Functions, Business Processes, Organization Units, and Value Streams. While these terms are sometimes used interchangeably in informal discussion, TOGAF assigns precise, distinct definitions to each.
| Construct | Primary Focus | Stability & Lifespan | Key Characteristic | Operational Example |
|---|---|---|---|---|
| Business Function | Strategic Capability / Purpose | High (Decades) | Logical grouping of capabilities based on business purpose; invariant across org restructures. | Financial Management, Human Resources, Supply Chain Logistics |
| Business Process | Operational Workflow / Execution | Medium (Years) | Event-driven sequence of activities converting inputs into measurable outputs. | Invoice Processing, Employee Onboarding, Order-to-Cash Workflow |
| Organization Unit | Structural Governance / Resource | Low to Medium (Months/Years) | Formal structural grouping of human resources, budgets, and management reporting hierarchy. | European Finance Division, Claims Handling Department |
| Value Stream | Stakeholder Value Delivery | High (Strategic Horizon) | End-to-end collection of value-adding activities delivering an outcome to a customer or stakeholder. | Concept-to-Market, Order-to-Fulfillment, Recruit-to-Retire |
1. Business Functions: Stable Enterprise Purpose
A Business Function delivers a major logical capability or family of capabilities required by an enterprise to execute its business model. Business functions are organized around a common business purpose, domain of knowledge, or skill set, regardless of how the enterprise is physically structured into departments or teams.
Key Properties of Business Functions
- Stability: Business functions represent core enterprise capabilities. For example, a commercial bank will always require a Risk Management function, a Commercial Lending function, and a Deposit Operations function, regardless of whether these functions are performed by centralized departments, regional branches, or automated software.
- Encapsulation: Functions group related sub-functions, processes, and business services under a unified functional umbrella.
- Independence from Structure: A business function is not an organization unit. An organizational restructuring may merge two departments, but the underlying business functions remain unchanged.
+---------------------------------------------------------------------------------+
| ENTERPRISE FUNCTIONS |
+------------------------------------+--------------------------------------------+
| FINANCIAL MANAGEMENT | SUPPLY CHAIN OPERATIONS |
| +------------------------------+ | +--------------------------------------+ |
| | Accounts Payable / Receivable| | | Procurement & Vendor Management | |
| +------------------------------+ | +--------------------------------------+ |
| | Treasury & Asset Management | | | Warehouse & Inventory Control | |
| +------------------------------+ | +--------------------------------------+ |
+------------------------------------+--------------------------------------------+
2. Business Processes: Operational Workflows
While a Business Function describes what an enterprise does, a Business Process describes how specific operational outcomes are achieved. A process is a structured, ordered sequence of activities or tasks executed by humans or automated systems, triggered by an explicit business event, and designed to produce a specific, measurable output for a customer or internal stakeholder.
Key Properties of Business Processes
- Event-Driven: Processes are initiated by triggers such as a customer submitting an online order, a system alert firing, or a fiscal quarter ending.
- Sequential and Rules-Based: Processes follow clear decision trees, routing paths, parallel branches, and escalation rules.
- Measurable: Processes are evaluated using key performance indicators (KPIs) such as cycle time, error rate, cost-per-transaction, and throughput.
- Dynamic Evolution: Unlike business functions, business processes are frequently re-engineered, optimized, or automated through technology upgrades.
3. Organization Units: Structural Accountability
An Organization Unit represents a self-contained unit of operational resources, human personnel, governance authority, and budgetary responsibility within an enterprise structure. Organization units define "who" executes work and holds operational accountability.
Mapping Organization Units to Architecture
Architects must explicitly map Organization Units to Business Capabilities and Business Processes. Over-relying on organization charts during architecture modeling is a frequent pitfall; organizational structures undergo frequent management changes, corporate re-organizations, and mergers. By mapping volatile Organization Units to stable Business Capabilities, architects establish a clear trace matrix showing which team currently owns and funds each capability.
4. Value Streams: End-to-End Stakeholder Value
A Value Stream is a high-level representation of the end-to-end flow of value-adding activities that create an explicit outcome for an internal or external stakeholder (such as a customer, partner, or employee).
Anatomy of a Value Stream
- Triggering Stakeholder & Value Proposition: Identifies who initiates or receives value (e.g., a retail consumer seeking a mortgage) and the ultimate value realized (e.g., "Acquired Home Ownership").
- Value Stream Stages: Sequential steps or milestones representing progressive value creation (e.g., Select Home -> Apply for Loan -> Underwrite Loan -> Approve & Fund -> Settle Account).
- Enabling Capabilities: Each value stream stage is supported by specific Business Capabilities. For instance, the Underwrite Loan stage relies on Credit Risk Analysis, Property Valuation, and Compliance Verification capabilities.
+---------------------------------------------------------------------------------+
| VALUE STREAM: ACQUIRE HOME MORTGAGE |
| Stakeholder: Retail Customer | Value Proposition: Verified Property Ownership |
+---------------+----------------+----------------+----------------+--------------+
| Stage 1: | Stage 2: | Stage 3: | Stage 4: | Stage 5: |
| Select Home | Apply for Loan | Underwrite | Approve & Fund | Settle |
+---------------+----------------+----------------+----------------+--------------+
| | | | |
v v v v v
[Capabilities: [Capabilities: [Capabilities: [Capabilities: [Capabilities:|
Property Search Applicant Data Credit Risk Fund Transfer Account |
Evaluation] Capture] Appraisal] Escrow Mgmt] Servicing] |
TOGAF Series Guide: Business Architecture Artifacts
The TOGAF Series Guide: Business Architecture provides detailed guidance on developing standardized business architecture artifacts during Phase B:
- Business Capability Map: A structured, hierarchical breakdown of the enterprise's total capability portfolio, categorized by strategic, core, and supporting capabilities.
- Organization Map: Visual representation of organizational units, locations, and relationships, establishing governance boundary context.
- Product Map: Catalog of enterprise products and services offered to external markets, linked to underlying capabilities and contracts.
- Value Stream Map: Visual depiction of end-to-end value streams, their stages, entry/exit criteria, and mapped supporting capabilities.
- Business Interaction Matrix: Matrix mapping interactions, information flows, and dependencies between business functions, processes, and external parties.
What is the primary operational distinction between a Business Function and a Business Process in TOGAF Business Architecture?
In Value Stream Mapping, how are Business Capabilities connected to Value Stream Stages?
Why does TOGAF recommend mapping Organization Units to Business Capabilities rather than relying solely on organization charts?