Study guide

8.2 Business Scenarios

TOGAF Enterprise Architecture Foundation OGEA-101

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Enterprise Architecture & the TOGAF Standard

1.1 The Enterprise, the Purpose of EA & Its Benefits 1.2 Why the TOGAF Standard: Framework, Documentation Set & Certification 1.3 The Four Architecture Domains & Architecture Abstraction

2 Chapter 2: Enterprise Continuum, Architecture Repository, Content Framework & Capability

2.1 The Enterprise Continuum 2.2 The Architecture Repository 2.3 The TOGAF Content Framework & Enterprise Metamodel 2.4 Architecture Capability

3 Chapter 3: Key TOGAF Terminology

3.1 Terms for Architecture Domains, Levels, States & Capability 3.2 Terms for Work Products, Models, Requirements & Change

4 Chapter 4: ADM Fundamentals, Preliminary Phase & Phase A

4.1 The ADM Cycle, Its Phases & Information Flow 4.2 Draft vs. Approved Deliverables & the Iterative ADM 4.3 Governing EA, Scoping the Architecture & Alternatives 4.4 The Preliminary Phase 4.5 Phase A: Architecture Vision

5 Chapter 5: Architecture Definition — Phases B, C & D

5.1 Phase B: Business Architecture 5.2 Phase C: Information Systems Architectures — Data & Application 5.3 Phase D: Technology Architecture

6 Chapter 6: Opportunities, Migration Planning & Implementation Governance (Phases E, F & G)

6.1 Phase E: Opportunities & Solutions 6.2 Phase F: Migration Planning 6.3 Phase G: Implementation Governance

7 Chapter 7: Phase H, Requirements Management & Agile Delivery

7.1 Phase H: Architecture Change Management 7.2 Requirements Management 7.3 Supporting Agile Software Development with the ADM

8 Chapter 8: ADM Techniques I — Guidelines, Principles, Business Scenarios & Gap Analysis

8.1 ADM Guidelines & Techniques and Architecture Principles 8.2 Business Scenarios 8.3 Gap Analysis

9 Chapter 9: ADM Techniques II — Interoperability, Transformation Readiness & Risk

9.1 Interoperability 9.2 Business Transformation Readiness Assessment 9.3 Risk Management

10 Chapter 10: Applying the ADM

10.1 Guidance for Applying TOGAF, Iteration & Concurrent Phases 10.2 The Architecture Landscape: Strategic, Segment & Capability Levels 10.3 Architecture Partitioning 10.4 The Four Purposes of Architecture 10.5 Applying the TOGAF Standard in the Digital Enterprise

11 Chapter 11: Architecture Governance

11.1 Architecture Governance: Concept & Benefits 11.2 The Architecture Board 11.3 Architecture Contracts 11.4 Architecture Compliance

12 Chapter 12: Architecture Content

12.1 Stakeholders, Concerns, Views & Viewpoints 12.2 Building Blocks: ABBs & SBBs 12.3 ADM Deliverables I: Preliminary Phase and Architecture Vision 12.4 ADM Deliverables II: From Architecture Definition to Change

8.2 Business Scenarios

Key Takeaways Explain This Topic AI

A business scenario describes a business process or application, the business and technology environment, the people and computing components (actors), and the desired outcome.

In TOGAF, SMART stands for Specific, Measurable, Actionable, Realistic, and Time-bound.

Creating a business scenario includes ranking the problem, documenting the environment, setting SMART objectives, identifying human and computer actors, and checking fitness-for-purpose.

Business scenarios are developed iteratively through gathering, analyzing, and reviewing information with the business.

Business scenarios are used in Phase A to articulate the Architecture Vision and in Phase B and Requirements Management to detail requirements.

Last updated: September 2026

8.2 Business Scenarios

The Foundation syllabus asks you to briefly explain business scenarios . A business scenario is a technique for discovering and documenting business requirements, and for articulating an Architecture Vision that responds to them. In the 10th Edition it is described in the TOGAF Series Guide: Business Scenarios .

Why Business Scenarios Matter

A key factor in the success of any architecture is the extent to which it is linked to business requirements and demonstrably supports the enterprise in achieving its business objectives. Business scenarios help identify and understand business needs and thereby derive the business requirements the architecture must address. They are an important technique that may be used prior to, and as a key input to, the development of the Business Architecture .

A business scenario describes:

  • A business process, application, or set of applications that can be enabled by the architecture
  • The business and technology environment
  • The people and computing components — called actors — who execute the scenario
  • The desired outcome of proper execution

A good business scenario is also SMART :

  • Letter TOGAF meaning
  • S pecific Defines what needs to be done in the business
  • M easurable Has clear metrics for success

A ctionable Clearly segments the problem and provides the basis for determining elements and plans for the solution

  • R ealistic The problem can be solved within the bounds of physical reality, time, and cost constraints
  • T ime-bound Gives a clear statement of when the solution opportunity expires

The glossary's definition of an Objective uses the same wording: an organizational aim declared in a Specific, Measurable, Actionable, Realistic, and Time-bound way.

Creating a Business Scenario

TOGAF describes the technique as a set of activities:

  • Identify, document, and rank the problem driving the scenario
  • Identify the business and technical environment of the scenario and document it in scenario models

Identify and document desired objectives — the results of handling the problem successfully — and make them SMART

  • Identify the human actors (participants) and their place in the business model
  • Identify the computer actors (computing elements) and their place in the technology model

Identify and document roles, responsibilities, and measures of success per actor ; document the required scripts per actor and the results of handling the situation

Check for fitness-for-purpose and refine only if necessary

Developing a business scenario is iterative : information is gathered , then analyzed , then reviewed with the business, and the cycle repeats until the scenario is good enough. A business scenario typically contains business scenario models (for example, business process, information flow, and actor interaction models) and descriptive text .

Where Business Scenarios Are Used in the ADM

Where Use

Phase A: Architecture Vision Discover and document business requirements and articulate an Architecture Vision that responds to them; the Architecture Vision output can include a business scenario

Phase B: Business Architecture Provide detail on business requirements as input to Business Architecture development

Other phases and Requirements Management Identify and document requirements at more detailed levels; step 1 of Requirements Management identifies requirements using business scenarios or an analogous technique

Business scenarios also reveal early the nature and security considerations of information and service exchanges , which later drive interoperability requirements.

Business Scenarios Versus Use Cases

A business scenario works at the level of a business problem : the environment, human and computer actors, their roles and responsibilities, and SMART objectives for the business. A software use case or user story describes interactions with a particular system. Business scenarios come first, so the architecture is driven by business need rather than by a proposed technology solution.

Worked Enterprise Scenario: Omnichannel Retail Banking Loan Origination

To see how the Business Scenarios technique functions in practice, examine this enterprise case study from the financial services sector:

1. Context & Business Problem

A regional commercial bank is hemorrhaging retail loan customers to agile digital fintech lenders. The bank's current loan origination process requires an average of 14 business days from application intake to loan approval, resulting in a 45% application abandonment rate . Customers who start applications online are forced to visit physical branches with paper documentation, leading to widespread dissatisfaction and lost revenue.

2. Environment & Constraints

Regulatory Mandates : Strict adherence to Fair Credit Reporting Act (FCRA), Anti-Money Laundering (AML), Know Your Customer (KYC), and Equal Credit Opportunity Act (ECOA) regulations.

Technical Constraints : Core banking customer accounts reside on a legacy 1980s mainframe system accessible only via batch queues and terminal emulation interfaces.

Channels : Mobile application, public web portal, and 240 physical branch offices.

3. Actors & Roles

Retail Applicant (Customer) : Wants rapid loan pre-qualification on mobile without branch visits.

Branch Lending Officer : Spends 60% of work hours manually re-keying paper documents into internal systems.

Credit Risk Underwriter : Requires aggregated credit scores, debt-to-income (DTI) calculations, and fraud indicators to approve non-standard loans.

Automated Underwriting Engine : Software service responsible for algorithmic credit decisioning.

Core Banking Mainframe : Authoritative system of record for account balances and customer master data.

4. Process & Action Analysis

Intake : Customer submits loan application via mobile app; system auto-fills identity data using biometric verification.

Verification : Automated integration calls external credit bureaus (Equifax/Experian) and internal fraud detection services.

Decisioning : Automated Underwriting Engine applies credit risk policy algorithms:

Tier 1 (Low Risk) : Instant approval without human intervention.

Tier 2 (Moderate Risk) : Routed to Credit Underwriter with pre-calculated DTI and risk highlights.

Tier 3 (High Risk) : Automated rejection with FCRA-compliant adverse action documentation.

Fulfillment : Approved applicants execute electronic digital signatures (e-Sign) and funds are disbursed via the core banking API.

5. Desired Business Outcomes

Reduce end-to-end loan approval turnaround from 14 days to under 10 minutes for 80% of applicants.

Reduce application abandonment rate from 45% to below 15% within 12 months of deployment.

Lower per-loan origination operational cost by 40% .

6. Derived SMART Architecture Requirements

ARS ID Requirement Statement (SMART) ADM Domain Mapping

REQ-B-01 The business process shall provide automated identity verification and instant credit pre-qualification across mobile and web channels within 30 seconds for 95% of retail applicants by Q2 2027. Phase B (Business Architecture)

REQ-C-01 The customer master data service shall synchronize applicant records between the digital mobile channel and legacy core banking mainframe using an event-driven integration mesh with zero data loss. Phase C (Data & Application Architecture)

REQ-C-02 The credit decisioning API shall interface securely with external credit rating bureaus, processing encrypted JSON payloads with an end-to-end response time under 3 seconds. Phase C (Application Architecture)

REQ-D-01 The loan origination platform shall be hosted in a multi-availability-zone containerized cloud environment providing 99.99% service availability during peak commercial hours. Phase D (Technology Architecture)

Common Exam Pitfalls

Misremembering SMART. In TOGAF the "A" is Actionable and the "R" is Realistic .

Forgetting computer actors. Actors include both people and computing components.

Treating business scenarios as technology designs. They document business requirements and desired outcomes first.

Placing business scenarios only in Phase B. They are used especially in Phase A to articulate the Architecture Vision, and can support other phases and Requirements Management.

Loading diagram... The Business Scenario Technique