What Is the BACCM (Business Analysis Core Concept Model)?
The BACCM is a six-concept framework defined by IIBA in the BABOK Guide v3 that describes what business analysis fundamentally works with: Change, Need, Solution, Stakeholder, Value, and Context. No single concept ranks above the others — each is defined in relation to the other five.
IIBA created BACCM to give business analysts a shared vocabulary that holds up across industries, methodologies, and project types. It’s tested directly on IIBA’s own certification exams — CBAP, CCBA, and ECBA — since IIBA designs those exams around it.
What Are the Six BACCM Core Concepts?
Each BACCM concept is fundamental to business analysis work and cannot be fully understood in isolation from the other five — they form one interconnected system rather than a sequential checklist.
| Concept | Definition |
| Change | An act of transformation in response to a need, intended to improve enterprise performance |
| Need | A problem or opportunity to be addressed |
| Solution | A specific way of satisfying one or more needs in a context |
| Stakeholder | A group or individual with a relationship to the change, the need, or the solution |
| Value | The worth, importance, or usefulness of something to a stakeholder within a context |
| Context | The circumstances that influence, are influenced by, and provide understanding of the change |
How Does BACCM Relate to the PMI-PBA Certification?
BACCM is not directly tested on the PMI-PBA exam. PMI-PBA uses its own five-domain Examination Content Outline — Needs Assessment, Planning, Analysis, Traceability and Monitoring, and Evaluation — which covers conceptually similar ground using different terminology and structure.
This distinction matters for anyone studying business analysis across both credential paths. IIBA’s BACCM and PMI-PBA’s domain structure both orbit the same underlying ideas — understanding stakeholder needs, defining value, evaluating solutions in context — but they’re not interchangeable frameworks, and a PMI-PBA candidate who studies BACCM as exam content will be preparing for the wrong test. Where BACCM genuinely helps a PMI-PBA candidate is as a mental model: it’s a fast way to sanity-check whether an analysis is missing a dimension (have you actually defined the value to the stakeholder, or just the solution?), even though PMI won’t ask about BACCM by name.
What Are the Most-Used Business Analysis Elicitation Techniques?
Elicitation techniques are the methods a business analyst uses to gather requirements from stakeholders, with the right choice depending on stakeholder count, geographic distribution, and domain familiarity.
- Interviews — one-on-one conversations that surface detailed, individual perspectives, best for complex or sensitive requirements.
- Requirements Workshops — structured group sessions that gather multiple stakeholder perspectives in a single sitting, but lose effectiveness with too many or too few participants.
- Brainstorming — group idea generation used to surface a wide range of options before narrowing to themes for further analysis.
- Document Analysis — reviewing existing documentation (policies, system specs, reports) to extract requirements without new stakeholder time.
- Observation — watching how work actually happens, useful for capturing undocumented current-state processes.
- Prototyping — building a working or visual model early to get concrete stakeholder feedback rather than abstract requirement statements.
- Survey/Questionnaire — collecting input at scale from a large or geographically dispersed stakeholder group.
- Focus Groups — moderated discussions with a representative stakeholder sample to validate assumptions.
- Interface Analysis — examining touchpoints between systems or between a system and its users to identify integration requirements.
What Are the Most-Used Requirements Analysis & Prioritization Techniques?
MoSCoW prioritization, use case modeling, and business process modeling are the techniques business analysts rely on most to turn elicited requirements into structured, prioritized, actionable specifications.
- MoSCoW — categorizes requirements as Must Have, Should Have, Could Have, or Won’t Have This Time, using criteria like business value, risk, and implementation difficulty to resolve conflicts.
- Use Case Modeling — documents functional requirements as interactions between an actor and a system, giving stakeholders and developers a shared, testable reference point.
- Business Process Modeling (BPMN) — diagrams current-state and future-state workflows to expose gaps, redundancies, and handoff points a narrative requirement would miss.
- SWOT Analysis — evaluates strengths, weaknesses, opportunities, and threats, typically applied earlier in strategy analysis rather than at the requirements level.
- Gap Analysis — compares current-state capability against future-state need to define exactly what a solution must close.
What Tools Do Business Analysts Use Daily?
Business analysts document requirements in Confluence or Word, map processes in Visio or Lucidchart, manage backlogs in Jira or Azure DevOps, and validate data-driven requirements using SQL and Excel.
| Category | Common Tools | Used For |
| Requirements documentation | Confluence, Microsoft Word | Requirements specs, business rules, meeting notes |
| Process mapping | Visio, Lucidchart | BPMN diagrams, current/future-state workflows |
| Backlog & requirements management | Jira, Azure DevOps | Tracking requirements through delivery |
| Data analysis | SQL, Excel | Validating requirements against real system data |
| Wireframing & prototyping | Figma, Balsamiq | Low-fidelity mockups for early stakeholder feedback |
BACCM vs PMI-PBA’s Five Performance Domains
BACCM’s six concepts and PMI-PBA’s five domains describe overlapping territory through different structures — BACCM organizes business analysis by what it works with, while PMI-PBA organizes it by the sequence of work performed.
| BACCM Concept | Closest PMI-PBA Domain Equivalent |
| Need | Needs Assessment |
| Stakeholder, Context | Planning |
| Change, Solution | Analysis |
| Value | Evaluation |
| (cross-cutting) | Traceability and Monitoring |
The mapping is conceptual, not official — PMI does not publish a cross-reference between the two frameworks, and this table exists to help candidates studying both bodies of knowledge see where the ideas connect, not to substitute for either framework’s own documentation.
Business Analysis Techniques FAQs
Is BACCM tested on the PMI-PBA exam?
No. BACCM is an IIBA/BABOK concept tested on CBAP, CCBA, and ECBA. PMI-PBA uses its own Examination Content Outline organized around five domains that cover similar ground with different terminology.
Do I need to learn BABOK to pass the PMI-PBA exam?
No, but understanding core BABOK concepts like BACCM builds the same underlying judgment PMI-PBA tests for, since both frameworks are built on similar business analysis fundamentals even though PMI-PBA doesn’t test BABOK terminology directly. PMTI’s PMI-PBA vs CBAP guide breaks down exactly where the two frameworks diverge.
What’s the difference between an elicitation technique and an analysis technique?
Elicitation techniques (interviews, workshops, observation) gather raw requirements from stakeholders. Analysis techniques (MoSCoW, use case modeling, BPMN) take those raw requirements and structure, prioritize, or validate them — elicitation comes first, analysis comes after.
