Part 2.
Key business analysis concepts
Business Analysis Core Concept
Model™ (BACCM™)
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.
— BABOK® Guide
Change
The act of transformation in Changes
response to a need.
Change works to improve the
performance of an enterprise.
These improvements are
deliberate and controlled
through business analysis
activities.
Need Cause
A problem or opportunity to be Changes
addressed.
Needs
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 Cause
A specific way of satisfying one Changes
or more needs in a context. Satisfy
Needs Solutions
A solution satisfies a need by
resolving a problem faced by
stakeholders or enabling
stakeholders to take advantage
of an opportunity.
Stakeholder Cause
A group or individual with a Changes
relationship to the change, the Satisfy
need, or the solution. Needs Solutions
Interested
Stakeholders are often defined in in
terms of interest in, impact on,
and influence over the change.
Stakeholders
Value Cause
The worth, importance, or Changes
usefulness of something to a Satisfy
stakeholder. Needs Solutions
Value can be seen as potential or
Delivered
realized returns, gains, and via
improvements. Value can be
tangible or intangible.
Stakeholders
Interested
in
Value
Context
The circumstances that Changes
influence, are influenced by, and
provide understanding of the Needs Solutions
change.
Changes occur within a context.
Stakeholders Context
Value
Combination of internal and external issues that can have an effect on
an organization’s approach to developing and achieving its objectives.
The concept of context of the organization is equally applicable to
not-for-profit or public service organizations as it is to those seeking
profits.
Synonyms: “business environment”, “organizational environment” or
“ecosystem of an organization”.
— ISO 9000:2015 Quality management systems — Fundamentals and
vocabulary
These concepts build
a mental framework
around business
analysis.
A framework that
works regardless of
the industry, domain,
job title or
technology.
References to
the BABOK® ❖ 2.1 The Business Analysis Core
Guide Concept Model™
Technique: concept model
A concept model is used to organize the business vocabulary needed to
consistently and thoroughly communicate the knowledge of a domain.
— BABOK® Guide
How do you build a concept model?
1/ Build a glossary (noun based terms)
2/ Understand connections (verb concepts)
3/ Explore other connections (categorisation,
classification, whole-part relationships, roles)
4/ Visualise
Usage considerations
Strengths Limitations
● Business friendly way to communicate with ● May set wrong expectations on how easy it
stakeholders is to build technical integrations based on
● Is independent of data design biases business semantics
● Is useful for knowledge rich processes ● Requires specialised skills to think
● Puts complex concepts into a cohesive form abstractly and non procedurally
● May be a non-familiar exercise for
stakeholders
● Requires tools that allow for real time
updates and use of terminology
References to
the BABOK®
❖
Guide
10.11 Concept Modelling
Requirements and design
Four levels of requirements
Business statements of goals, objectives, and outcomes that
describe why a change has been initiated.
Stakeholders the needs of stakeholders that must be met in order to
achieve the business requirements.
Solution the capabilities and qualities of a solution that meets
the stakeholder requirements.
Transition describe the capabilities that the solution must have to
facilitate transition from the current to the future state
Business statements of goals, objectives, and outcomes that
describe why a change has been initiated
They can apply to the whole of an enterprise, a business area, or a specific
initiative.
Examples:
● increase average order value by 15%
● Increase loyalty
● decrease operational cost by 10%
Stakeholders the needs of stakeholders that must be met in order to
achieve the business requirements
They may serve as a bridge between business and solution requirements.
Examples:
● As a marketing manager I want to update the product descriptions so that
they match the marketing tone of voice
● As a returning customer I want to see my previous orders to remember
what did I order last time
● As a customer who is ready to buy I want to use a “buy now pay later” option
to ease the financial burden of the purchase
Solution the capabilities and qualities of a solution that meets
the stakeholder requirements
Functional: describe the capabilities that a solution must have in terms of the
behaviour and information that the solution will manage
Examples:
● Given the user is on checkout page
When the user clicks on a “buy now pay later” option
Then a third-party checkout interface is opened in a new window to finish the purchase
● Given the user started a “buy now pay later” section from checkout
When the “buy now pay later” session is finished
Then a confirmation message is displayed with the result of transaction
Solution the capabilities and qualities of a solution that meets
the stakeholder requirements
Non-Functional (Quality of service): do not relate directly to the behaviour of
functionality of the solution, but rather describe conditions under which a
solution must remain effective or qualities that a solution must have
Examples:
● Accessibility ● Documentation
● Security ● Audit
● Availability ● Hours of support/SLA
● Maintainability ● etc.
● Business Continuity
Transition describe the capabilities that the solution must have to
facilitate transition from the current to the future
state
They are differentiated from other requirements types because they are of a
temporary nature.
Examples:
● Data migration
● Training
● Business continuity during transition
● Redirects
● Comms/Change management
A path to solution
Need Requirement Design Solution
A path to solution
Need Requirement Design Solution
I hate As a registered member
forgetting I want to securely log in
passwords without typing my
password
So I don’t need to
remember it
References to
the BABOK® ❖
❖
2.2 Key Terms
2.3 Requirements Classification
Guide ❖
Schema
2.5 Requirements and Designs
Advanced Business
Analysis
Igor Arkhipov, CBAP
