Study guide
7.3 Assess Solution Limitations
CBAP Certified Business Analysis Professional Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & BACCM Framework
1.1 CBAP Exam Structure, Eligibility & Study Plan 1.2 The Business Analysis Core Concept Model (BACCM) 1.3 Key Concepts, Terms & Requirements Classification 1.4 Business Analysis Governance & Stakeholder Engagement Principles
2 Chapter 2: Business Analysis Planning and Monitoring
2.1 Plan Business Analysis Approach 2.2 Plan Stakeholder Engagement 2.3 Plan Business Analysis Governance 2.4 Plan Business Analysis Information Management 2.5 Identify Business Analysis Performance Improvements
3 Chapter 3: Elicitation and Collaboration
3.1 Prepare for Elicitation 3.2 Conduct Elicitation 3.3 Confirm Elicitation Results 3.4 Communicate Business Analysis Information 3.5 Manage Stakeholder Collaboration
4 Chapter 4: Requirements Life Cycle Management
4.1 Trace Requirements 4.2 Maintain Requirements 4.3 Prioritize Requirements 4.4 Assess Requirements Changes 4.5 Approve Requirements
5 Chapter 5: Strategy Analysis
5.1 Analyze Current State 5.2 Define Future State 5.3 Assess Risks 5.4 Define Change Strategy 5.5 Business Case Development & Financial Analysis
6 Chapter 6: Requirements Analysis and Design Definition
6.1 Specify and Model Requirements 6.2 Verify Requirements 6.3 Validate Requirements 6.4 Define Requirements Architecture 6.5 Define Design Options 6.6 Analyze Potential Value and Recommend Solution 6.7 Data Modeling & Process Modeling Techniques 6.8 Use Cases, User Stories & Acceptance Criteria Definition 6.9 Non-Functional Requirements & Solution Constraints
7 Chapter 7: Solution Evaluation
7.1 Measure Solution Performance 7.2 Analyze Performance Measures 7.3 Assess Solution Limitations 7.4 Assess Enterprise Limitations 7.5 Recommend Actions to Increase Solution Value
8 Chapter 8: Underlying Competencies, Techniques & Perspectives
8.1 Analytical Thinking, Problem Solving & Business Knowledge 8.2 Behavioral Characteristics & Interaction Skills 8.3 Core BABOK Techniques Master Review 8.4 Business Analysis Perspectives
7.3 Assess Solution Limitations
Key Takeaways Explain This Topic AI
Task 28 (Assess Solution Limitations) investigates internal factors within the solution component itself that prevent full value realization.
Solution limitations encompass software defects, business logic errors, technical debt, database bottlenecks, and usability/UX barriers.
A critical CBAP concept is the boundary distinction: solution limitations reside strictly internal to the solution, whereas enterprise limitations reside in the external organization.
Root cause analysis techniques—including 5 Whys, Ishikawa (Fishbone) Diagrams, and Pareto Analysis—isolate fundamental technical defects rather than surface symptoms.
Usability and Human-Computer Interaction (HCI) flaws are solution limitations that directly impair end-user adoption and operational throughput.
Last updated: August 2026
- 7.3 Assess Solution Limitations
- Purpose of Task 28
The primary objective of Task 28: Assess Solution Limitations is to identify factors internal to the solution component itself that restrict it from delivering its full expected value to the enterprise. When Task 27 reveals performance gaps or unrealized value, Task 28 investigates the solution artifact—examining software bugs, architectural flaws, technical debt, usability barriers, and data integrity constraints.
In the BABOK® Guide v3 framework, a solution limitation resides strictly within the boundary of the solution component itself. Distinguishing internal solution flaws from external enterprise environment constraints is a cornerstone of professional business analysis practice.
Inputs, Outputs, and BACCM Relationships
Assessing solution limitations requires evaluating performance analysis results directly against solution components.
BABOK Component Element Name Description & Strategic Context
Inputs Implemented Solution (external or internal) The active solution, operational software, or service architecture being investigated.
Inputs Solution Performance Analysis Evaluated metric variances and performance gaps identified during Task 27.
Outputs Solution Limitation Documented root causes, internal defects, usability flaws, and architectural restrictions.
Guidelines & Tools Risk Analysis Results, Solution Scope Risk context and functional boundaries governing internal solution performance.
Mapping to the Business Analysis Core Concept Model (BACCM)
Context: Evaluates how technical architecture and component interfaces interact with external systems.
Need: Identifies specific functional capabilities within the solution that fail to meet user requirements.
Solution: Focuses directly on inspecting internal code quality, database structures, UI design, and execution logic.
Stakeholder: Investigates how usability defects create user frustration, workarounds, or operational errors.
Value: Pinpoints exact solution defects that block the realization of projected business benefits.
Change: Determines whether technical modification of the solution component can eliminate performance barriers.
- Taxonomy of Internal Solution Limitations
- Solution limitations generally fall into four core categories: INTERNAL SOLUTION LIMITATION TAXONOMY
- ┌───────────────────────────┬───────────────────────────┬───────────────────────────┐
- │ FUNCTIONAL & LOGICAL DEFE.│ TECHNICAL DEBT & LATENCY │ USABILITY & UX BARRIERS │
- ├───────────────────────────┼───────────────────────────┼───────────────────────────┤
- │ • Software Bugs │ • Unoptimized DB Queries │ • Confusing UI Workflows │
- │ • Incorrect Calculation │ • Legacy Infrastructure │ • Excessive Click Depth │
- │ Business Logic │ • Scalability Bottlenecks │ • Poor Error Messages │
- │ • Missing Edge-Case Handling│ • Memory Leaks / Crashes │ • Accessibility Failures │
- └───────────────────────────┴───────────────────────────┴───────────────────────────┘
- 1. Functional Defects and Business Logic Errors
Coding Defects: Software bugs that produce incorrect outputs, system crashes, or data corruption under specific operational conditions.
Logic Gaps: Rules implemented in code that fail to handle complex edge cases or multi-variable business rules accurately.
2. Technical Debt and Architectural Bottlenecks
Database Latency: Unindexed database tables or inefficient query structures causing slow processing times under high transaction volumes.
Scalability Limits: Monolithic system architectures unable to handle concurrent user loads beyond expected thresholds.
Technical Debt: Quick-fix code patches or legacy framework dependencies that impede performance upgrades.
3. Usability and Human-Computer Interaction (HCI) Barriers
High Cognitive Load: User interfaces that require complex manual data re-entry or excessive navigational steps to complete a transaction.
Cryptic Error Handling: Failure messages that provide no clear recovery guidance, forcing end-users to abandon tasks or create manual workarounds.
4. Data Architecture and Integration Flaws
Data Synchronization Delays: Asynchronous batch updates creating data latency between integrated enterprise systems.
Data Incompleteness: Missing data fields in API payloads preventing downstream automated processing.
Root Cause Analysis Techniques
Business analysts apply structured root cause analysis techniques to investigate solution limitations:
Technique Operational Methodology Primary Application in Task 28
5 Whys Analysis Iteratively asking "Why?" five times to drill down from symptom to fundamental cause. Uncovering hidden technical or design causes behind operational failures.
Ishikawa (Fishbone) Diagram Categorizing potential defect sources across People, Process, Technology, Data, and Environment. Visualizing compound technical and functional factors causing solution defects.
Pareto Analysis (80/20 Rule) Graphing defect frequencies to isolate the 20% of solution causes driving 80% of performance gaps. Prioritizing technical fixes that deliver maximum value recovery.
Problem Tracking Managing documented solution issues, defect backlogs, and resolution statuses. Tracking identified solution bugs through diagnostic and remediation cycles.
Practical Example: Root Cause Analysis of a Core Banking Payment Solution
A financial institution's payment processing engine suffered a 12% transaction failure rate during peak morning hours.
5 Whys Application:
Why are transactions failing? System times out after 30 seconds.
Why is it timing out? The database lock wait time exceeds connection limits.
Why is the lock wait time excessive? Account balance validation queries perform full table scans.
Why are full table scans occurring? The transaction history table lacks index coverage on account IDs.
Why was indexing omitted? Database schema was migrated from a legacy platform without re-indexing scripts.
Identification of Limitation: The BA documented an internal technical solution limitation : missing database indexing and legacy query design causing thread locking under high concurrency.
CBAP Exam Strategy & Distractor Analysis
The Boundary Rule (Solution vs. Enterprise): If the defect is caused by software bugs, database slowdowns, or confusing user interface layout, it is a Solution Limitation (Task 28) . If the defect is caused by employees refusing to use the software due to poor management incentive structures or lack of training, it is an Enterprise Limitation (Task 29) .
Symptom vs. Cause: CBAP questions test whether you can distinguish between a symptom (e.g., "high call center volume") and a solution limitation root cause (e.g., "self-service web portal crashes on mobile browsers").
Pareto Efficiency: When asked how to prioritize multiple solution limitations, select Pareto Analysis to address the high-impact vital few.