7.1 Define Design Options (Task 7.5)

7.1 Define Design Options (Task 7.5)

Quick Summary: BABOK® Guide v3 Task 7.5 (Define Design Options) is the bridge between validated business requirements and concrete solution architecture. It identifies multiple distinct solution approaches (Buy, Build, Outsource, Enhance, Hybrid), decomposes them into solution components (software, business processes, organizational roles, data architecture), and allocates requirements to determine the most effective path toward achieving business objectives.

---

Purpose and Definition of Task 7.5

The purpose of Define Design Options is to define the solution approach, identify opportunities to improve the business, allocate requirements across solution components, and represent design options that achieve the desired future state. While requirements define what stakeholders need to accomplish business goals, design options articulate how those capabilities can be operationalized and structured.

In BABOK v3, a Design Option is not merely a technical software blueprint or a graphical user interface mockup. It is a comprehensive, multi-dimensional description of a potential solution that encompasses technological systems, operational workflows, organizational reporting structures, and information assets. Business analysts formulate multiple candidate design options so decision-makers have viable, contrasting alternatives to evaluate.

+-----------------------------------------------------------------------------------+
|                             BABOK Task 7.5 Structure                              |
+-----------------------------------------------------------------------------------+
|  INPUTS:                                                                          |
|  * Change Strategy (Task 6.4)                                                     |
|  * Requirements (Validated and Prioritized - Tasks 5.3 & 7.3)                     |
|  * Requirements Architecture (Task 7.4)                                           |
|                                                                                   |
|  ELEMENTS:                                                                        |
|  1. Define Solution Approaches (Buy, Build, Outsource, Enhance, Hybrid)           |
|  2. Identify Improvement Opportunities (Automation, Elimination, Efficiency)      |
|  3. Requirements Allocation (Distributing requirements across components)         |
|  4. Describe Design Options (Components, constraints, dependencies)               |
|                                                                                   |
|  OUTPUTS:                                                                         |
|  * Design Options (Specified, Allocated, and Ready for Value Analysis)            |
+-----------------------------------------------------------------------------------+

---

The Five Primary Solution Approaches

When formulating design options, business analysts investigate five foundational Solution Approaches, each presenting distinct strategic benefits, financial commitments, and operational risks:

---

Requirements Allocation Across Solution Components

Requirements Allocation is the process of assigning validated requirements to specific components of a design option. An effective business solution rarely relies exclusively on automated software; instead, requirements are distributed across four interdependent solution components:

   ┌─────────────────────────────────────────────────────────────────────────────┐
   │ 1. SOFTWARE & TECHNOLOGY APPLICATIONS                                       │
   │ Custom code, SaaS platforms, API gateways, database engines, mobile apps.  │
   ├─────────────────────────────────────────────────────────────────────────────┤
   │ 2. BUSINESS PROCESSES & PROCEDURAL WORKFLOWS                                │
   │ Manual operational checks, standard operating procedures (SOPs), escalation.│
   ├─────────────────────────────────────────────────────────────────────────────┤
   │ 3. ORGANIZATIONAL ROLES & PEOPLE STRUCTURES                                 │
   │ Specialized governance committees, customer support tiers, compliance leads.│
   ├─────────────────────────────────────────────────────────────────────────────┤
   │ 4. DATA ARCHITECTURE & INFORMATION ASSETS                                   │
   │ Master data models, data warehousing schemas, real-time message streams.   │
   └─────────────────────────────────────────────────────────────────────────────┘

Strategic Allocation Scenarios

• Automated vs. Manual Allocation: A requirement for "Detect fraudulent transactions over $10,000" could be allocated to an automated machine learning software model (high development cost, sub-second response) or allocated to an organizational role—such as a Senior Fraud Analyst reviewing daily batch reports (low technical cost, 24-hour latency).
• Maximizing Operational Feasibility: Allocating requirements must reflect the enterprise's technical capabilities, budget boundaries, and organizational change readiness.

---

Identifying Improvement Opportunities

During Task 7.5, the business analyst actively uncovers opportunities to streamline enterprise performance:

• Process Automation: Replacing repetitive, manual data entry with robotic process automation (RPA) or API integrations.
• Waste Elimination (Lean BA): Removing redundant approval handoffs, duplicated verification steps, and unnecessary reporting cycles.
• Information Access Optimization: Providing real-time dashboard analytics to frontline staff rather than weekly static spreadsheets.
• Business Capability Enhancement: Upgrading underlying organizational skills, tooling, and partner networks to unlock new revenue streams.

---

Technical Dependencies and Vendor Assessment

When evaluating external vendor packages (COTS/SaaS), business analysts conduct rigorous Vendor Assessments to ensure long-term architectural and strategic viability:

1. Functional Fit Analysis: Evaluating the percentage of requirements satisfied "out-of-the-box" versus requirements requiring custom configuration or code modifications.
2. Technical Architecture Compatibility: Verifying API capabilities (REST/GraphQL), database protocols, SSO/SAML identity integrations, and cloud hosting topologies (AWS, Azure, GCP).
3. Vendor Viability & Stability: Reviewing vendor financial health, market reputation, product roadmap commitment, customer churn rates, and regulatory compliance certifications (SOC 2, ISO 27001, HIPAA, GDPR).
4. Total Licensing & Support Costs: Uncovering hidden expenses such as implementation consulting fees, data egress charges, API call volume tiers, and annual maintenance escalation clauses.

---

Enterprise Scenario: Retail Banking Wealth Management Transformation

A Tier-1 retail bank seeks to launch an automated robo-advisory investment platform for 2 million consumer banking customers. The lead business analyst defines three distinct design options:

• Design Option A (Buy COTS / SaaS): License an established wealth-management SaaS platform from a global FinTech vendor. Fast deployment (4 months), low initial build cost ($800K), but requires ongoing recurring seat licenses ($12/user/year) and forces the bank to adopt the vendor's rigid onboarding workflow.
• Design Option B (Build Custom Microservices): Develop a fully proprietary robo-advising algorithmic platform in-house. High initial CapEx ($4.2M) and long development time (18 months), but yields 100% intellectual property ownership, seamless native integration with core banking systems, and zero per-user subscription fees.
• Design Option C (Hybrid Composite): License the vendor's calculation engine via headless REST APIs, build a custom branded mobile UI front-end in-house, and allocate customer dispute handling to an outsourced Tier-2 customer operations center. Balances time-to-market (7 months) with brand differentiation and flexible support costs.

---

Key BABOK v3 Techniques for Task 7.5

• Benchmarking and Market Analysis: Investigates existing market solutions, competitor capabilities, and industry software trends to understand current technological possibilities.
• Business Capability Analysis: Identifies core capabilities required to support each design option and evaluates organizational maturity gaps.
• Decision Analysis: Employs structured decision trees, weighted criteria models, and multi-factor matrices to score candidate design options.
• Vendor Assessment: Systematically evaluates third-party software and service providers against technical, financial, and contractual standards.
• Functional Decomposition: Decomposes candidate design options into granular sub-systems and allocating modules.

[!TIP] CCBA Exam Tip: Remember that Requirements Allocation is not restricted to IT software components. When a scenario mentions reassigning a compliance check to a human supervisory role or updating an operational standard operating procedure (SOP), this is a legitimate requirements allocation to an organizational/process component under Task 7.5.

[!WARNING] CCBA Exam Trap: Do not confuse Change Strategy (Task 6.4) with Design Options (Task 7.5). The Change Strategy establishes the high-level roadmap, release releases, and enterprise transition approach. Task 7.5 specifies the concrete solution architectures, technological approaches (Buy/Build/Outsource), and requirement allocations that bring that strategy to life.