Study guide
1.2 The Business Analysis Core Concept Model (BACCM™)
CCBA Certification of Capability in Business Analysis Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & CCBA Exam Foundation
1.1 CCBA Exam Structure, Eligibility & IIBA Framework 1.2 The Business Analysis Core Concept Model (BACCM™) 1.3 Requirements Classification Schema & Architecture 1.4 CCBA Competency & Proficiency Levels (Level 2 — Skilled)
2 Chapter 2: Business Analysis Planning and Monitoring
2.1 Plan Business Analysis Approach (Task 3.1) 2.2 Plan Stakeholder Engagement (Task 3.2) 2.3 Plan Business Analysis Governance (Task 3.3) 2.4 Plan Business Analysis Information Management (Task 3.4) 2.5 Identify BA Performance Improvements (Task 3.5)
3 Chapter 3: Elicitation and Collaboration
3.1 Prepare for Elicitation (Task 4.1) 3.2 Conduct Elicitation (Task 4.2) 3.3 Confirm Elicitation Results (Task 4.3) 3.4 Communicate Business Analysis Information (Task 4.4) 3.5 Manage Stakeholder Collaboration (Task 4.5)
4 Chapter 4: Requirements Life Cycle Management
4.1 Trace Requirements (Task 5.1) 4.2 Maintain Requirements (Task 5.2) 4.3 Prioritize Requirements (Task 5.3) 4.4 Assess Requirements Changes (Task 5.4) 4.5 Approve Requirements (Task 5.5)
5 Chapter 5: Strategy Analysis
5.1 Analyze Current State (Task 6.1) 5.2 Define Future State (Task 6.2) 5.3 Assess Risks (Task 6.3) 5.4 Define Change Strategy (Task 6.4)
6 Chapter 6: Requirements Analysis and Design Definition — Modeling & Architecture
6.1 Specify and Model Requirements (Task 7.1) 6.2 Verify Requirements (Task 7.2) 6.3 Validate Requirements (Task 7.3) 6.4 Define Requirements Architecture (Task 7.4)
7 Chapter 7: Requirements Analysis and Design Definition — Design & Value
7.1 Define Design Options (Task 7.5) 7.2 Analyze Potential Value and Recommend Solution (Task 7.6) 7.3 Estimation Techniques & Solution Trade-Offs 7.4 Acceptance and Evaluation Criteria Definition
8 Chapter 8: Solution Evaluation
8.1 Measure Solution Performance (Task 8.1) 8.2 Analyze Performance Measures (Task 8.2) 8.3 Assess Solution Limitations (Task 8.3) 8.4 Assess Enterprise Limitations (Task 8.4) 8.5 Recommend Actions to Increase Solution Value (Task 8.5)
9 Chapter 9: Essential BABOK Techniques
9.1 Core Elicitation & Analysis Techniques 9.2 Process, Data & Non-Functional Requirements Modeling 9.3 Financial Analysis & Business Case Techniques 9.4 Prioritization & Scope Techniques 9.5 Root Cause & Decision Analysis Techniques
10 Chapter 10: Underlying Competencies & Perspectives
10.1 Analytical Thinking, Problem Solving & Systems Thinking 10.2 Behavioral Characteristics, Communication & Interaction Skills 10.3 Business Acumen, Solution Knowledge & BA Tooling 10.4 The Five BABOK Perspectives in Practice
11 Chapter 11: CCBA Exam Mastery & Scenario Strategy
11.1 Deconstructing CCBA Scenario Questions & BABOK Logic 11.2 Common Traps, Distractors & Subtle BABOK Distinctions 11.3 Comprehensive 8-Week Study Plan & Exam Day Strategy
1.2 The Business Analysis Core Concept Model (BACCM™)
Key Takeaways Explain This Topic AI
The Business Analysis Core Concept Model (BACCM™) is a conceptual framework defined in BABOK v3 consisting of six core concepts: Change, Need, Solution, Stakeholder, Value, and Context.
The six concepts have equal standing, are non-hierarchical, and function as an interconnected, dynamic system where altering any one concept directly impacts the other five.
Every one of the 30 tasks across all six Knowledge Areas in BABOK v3 directly addresses, transforms, or evaluates all six BACCM core concepts.
Value within the BACCM is defined as the worth, importance, or usefulness of something to a stakeholder within a specific context, and can be tangible, intangible, positive, or negative.
CCBA scenario questions use the BACCM as a primary lens to test whether the candidate can identify root problems, recognize environmental constraints, and preserve stakeholder value during organizational changes.
Last updated: August 2026
1.2 The Business Analysis Core Concept Model (BACCM™)
The Business Analysis Core Concept Model™ (BACCM™) is the conceptual foundation of the business analysis profession as defined in Chapter 2 of the BABOK® Guide v3 . It provides a common, domain-agnostic vocabulary that expresses the essence of business analysis regardless of industry, organizational structure, project methodology (Agile, Predictive, Hybrid), or technology stack.
For the CCBA examination, the BACCM is not merely a theoretical diagram to be memorized; it is the operational lens through which all 30 BABOK tasks are executed and evaluated . A business analyst who understands the BACCM can analyze any enterprise scenario, determine what is missing, identify misalignment, and formulate the correct corrective action.
1. The Six Core Concepts Defined
The BACCM comprises six core concepts that collectively define the domain of business analysis: ┌────────────────────────┐
- │ CHANGE │
- │ The act of transforma- │
- │ tion in response to │
- │ a need. │
- └───────────┬────────────┘
- │
- ┌─────────────────────────┼─────────────────────────┐
- │ │ │
- ┌───────────┴────────────┐ │ ┌────────────┴───────────┐
- │ NEED │ │ │ SOLUTION │
- │ A problem, opportunity │ │ │ A specific way of sat- │
- │ or constraint with po- │ │ │ isfying one or more │
- │ tential value. │ │ │ needs in a context. │
- └───────────┬────────────┘ │ └────────────┬───────────┘
- │ THE BACCM™ HEXAGON │
- │ (Equal, Dynamic Interdependence) │
- ┌───────────┴────────────┐ │ ┌────────────┴───────────┐
- │ CONTEXT │ │ │ STAKEHOLDER │
- │ The environment that │ │ │ An individual/group │
- │ influences, is influ- │ │ │ with a relationship to │
- │ enced by, or encloses. │ │ │ the change/need/sol. │
- └───────────┬────────────┘ │ └────────────┬───────────┘
- │ │ │
- └─────────────────────────┼─────────────────────────┘
- │
- ┌───────────┴────────────┐
- │ VALUE │
- │ The worth, importance, │
- │ or usefulness to a │
- │ stakeholder in context.│
- └────────────────────────┘
- 1. Change
Definition: The act of transformation in response to a need.
Characteristics: Change is deliberate, structured, and aimed at improving the performance of an enterprise. It encompasses both the transition process and the future state. Business analysis activities facilitate, direct, and stabilize this transformation.
2. Need
Definition: A problem or opportunity to be addressed.
Characteristics: Needs motivate organizations to act by triggering change. Needs can be high-level strategic imperatives (e.g., entering a new geographic market) or tactical operational bottlenecks (e.g., a manual reconciliation process causing billing delays). A need creates the potential for value.
3. Solution
Definition: A specific way of satisfying one or more needs in a context.
Characteristics: A solution resolves a problem or allows an enterprise to exploit an opportunity. It is not restricted to software or IT systems ; a solution may consist of organizational restructuring, process workflows, policy revisions, job role realignments, third-party software, data architecture, or training programs.
4. Stakeholder
Definition: A group or individual with a relationship to the change, the need, or the solution.
Characteristics: Stakeholders are grouped by their relationship to the initiative (e.g., sponsor, domain subject matter expert, end-user, regulator, supplier). They are analyzed in terms of their interest, influence, authority, attitude, and impact.
5. Value
Definition: The worth, importance, or usefulness of something to a stakeholder within a context.
Characteristics: Value is inherently subjective—what represents high value to a financial controller (e.g., cost reduction) may represent negative value to an end-user (e.g., increased data entry workload). Value can be:
Tangible: Measurable financial returns, revenue growth, defect reduction, operational cost savings.
Intangible: Brand equity, customer trust, employee morale, regulatory compliance safety.
Positive or Negative: Benefits realized vs. losses, costs, or friction incurred.
6. Context
Definition: The environment in which the change occurs, encompassing everything that is relevant to the change that is not part of the change itself.
Characteristics: Context influences, is influenced by, and provides the boundaries for the change. Context includes:
External factors: Competitors, government regulations, macroeconomic climate, demographic shifts, industry standards.
Internal factors: Organizational culture, existing IT infrastructure, corporate governance, organizational politics, sales channels, physical locations.
2. Dynamic Interrelationships Among the Six Concepts
The most critical principle of the BACCM is that all six core concepts are of equal standing, non-hierarchical, and co-dependent . If any single concept changes or is poorly understood, the remaining five concepts are fundamentally destabilized.
Pairwise Relationship Business Analysis Interaction & Enterprise Consequence
Change + Need The Change Strategy must directly resolve the Need . If the need changes, the scope and direction of the change must be adjusted.
Need + Value A Need defines the potential Value to be unlocked. If the value delivered does not exceed the cost of satisfying the need, the initiative should not proceed.
Solution + Context A Solution must be designed to operate effectively within the organizational and technological Context . A cloud-native solution cannot succeed in a context lacking high-speed connectivity.
Stakeholder + Value Value is defined strictly from the perspective of the Stakeholder . A solution that delivers high efficiency but destroys customer satisfaction fails the value test.
Context + Change The Context dictates the feasible pace, risk appetite, and constraints of the Change . A heavily regulated banking context requires predictive governance for change.
Solution + Need The Solution must satisfy the Need without introducing extraneous features (gold plating) that do not trace to a verified need.
Enterprise Example: The Cascading Impact of a Context Shift
Consider a global fintech firm processing credit card payments:
Context Shift: The European Union enacts a new data sovereignty and digital privacy regulation (External Context change).
Need Emerges: The enterprise has an immediate Need to prevent legal sanctions and ensure user financial data is stored within EU geographic boundaries.
Stakeholder Alignment: The Compliance Director, Chief Risk Officer, and Database Architects become primary Stakeholders with urgent interest and veto authority.
Solution Redesign: The existing Solution (a centralized North American data lake) is redesigned into localized regional microservices.
Change Execution: A Change initiative is launched to re-architect data pipelines and re-train DevOps personnel.
Value Realization: The Value generated is the avoidance of multi-million-euro regulatory penalties and preservation of customer trust in European markets.
3. How BABOK Tasks Express the BACCM
Every task in the BABOK® Guide v3 includes a formal BACCM Table illustrating how that specific task addresses each of the six concepts. The table below illustrates how the BACCM is applied across key tasks from different Knowledge Areas:
BABOK Task Core Concept How the Task Applies the Concept
Task 3.1: Plan BA Approach Change Determines the overall approach to manage the transformation (Predictive vs. Adaptive).
Context Analyzes organizational culture, regulatory limits, and project complexity to shape the BA approach.
Stakeholder Identifies who participates in shaping the business analysis process.
Task 4.2: Conduct Elicitation Need Discovers latent problems, unmet aspirations, and underlying constraints.
Stakeholder Actively collaborates with stakeholders to uncover tacit knowledge and requirements.
Value Captures stakeholder desires and metrics that define what success looks like.
Task 7.1: Specify & Model Requirements Solution Represents the detailed capabilities, rules, and behaviors the solution must possess.
Change Defines the future state components that must be built, purchased, or configured.
Value Ensures modeled requirements trace directly to quantifiable business outcomes.
Task 8.3: Assess Solution Limitations Solution Identifies defects, capacity bottlenecks, or functional gaps in an active solution.
Value Analyzes why the active solution is underperforming and failing to deliver full potential value.
Context Evaluates whether environmental changes (e.g., market growth) have outstripped the solution.
4. Applying BACCM to Deconstruct CCBA Scenario Questions
When tackling scenario-based CCBA exam questions, you can apply the BACCM 4-Step Analysis Framework to eliminate distractors and isolate the correct answer: ┌─────────────────────────────────────────────────────────────────────────────┐
- │ Step 1: Identify the PRIMARY TRIGGER │
- │ Did the Context shift? Did a Stakeholder object? Did the Need morph?│
- ├─────────────────────────────────────────────────────────────────────────────┤
- │ Step 2: Determine which Concept is MISALIGNED │
- │ Is the Solution failing to deliver Value? Is the Change off-scope? │
- ├─────────────────────────────────────────────────────────────────────────────┤
- │ Step 3: Map to the relevant BABOK KNOWLEDGE AREA and TASK │
- │ Are we in Strategy Analysis, RADD, RLCM, BAPM, or Solution Eval? │
- ├─────────────────────────────────────────────────────────────────────────────┤
- │ Step 4: Select the action that RESTORES EQUILIBRIUM across all 6 Concepts │
- │ Choose the standard BABOK task output, not a workplace shortcut. │
- └─────────────────────────────────────────────────────────────────────────────┘
- Common Exam Traps Involving the BACCM
The "Technology-Only Solution" Trap: Assuming that "Solution" refers exclusively to software. If a scenario asks for a solution to an operational delay, the correct answer might be a revised business policy or training program, not buying software.
The "Isolated Value" Trap: Believing value is universal. If a new automated tool saves money for IT (positive value) but doubles order entry time for nurses (negative value), the BA must assess net stakeholder value in context.
The "Context Ignorance" Trap: Recommending an agile prototyping technique when the organizational context has strict compliance constraints requiring signed audit baselines before development.