The Business Analysis Core Concept Model™ (BACCM™) is a conceptual framework for business analysis.
It encompasses what business analysis is and what it means to those performing business analysis tasks regardless of perspective, industry, methodology, or level in the organization.
It is composed of six terms that have a common meaning to all business analysts and helps them discuss both business analysis and its relationships with common terminology.
Each of these terms is considered to be a core concept.

Also shows how each is related to the other concepts. All come from BABOK.
| Core Concept | Description |
|---|---|
| Change | Act of transformation in response to a need |
| Need | A problem or opportunity to be addressed. |
Needs can cause changes by motivating stakeholders to act
Changes can also cause needs by eroding or enhancing the value delivered by existing solutions. | | Solution | A specific way of satisfying one or more needs in a context.
By resolving a problem faced by the stakeholders, or enabling stakeholders to take advantage of an opportunity. | | 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.
Increase in value: Can be potential or realized returns, gains, and improvements.
Decrease in value: In the form of losses, risks, and costs. | | Context | The circumstances that influence, are influenced by, and provide understanding of the change. |
The key is to view BACCM as an ongoing framework rather than a one-time analysis tool. It's meant to be revisited and reapplied throughout the project to ensure all aspects are being considered as the project evolves.
BACCM is not a rigid methodology but a framework to ensure you're considering all crucial aspects of business analysis.
By continuously applying BACCM, you ensure that your business analysis activities remain comprehensive and aligned with the project's evolving nature.
Here's how BACCM can be applied at different project stages: