WELCOME
Certified Business Analysis
Designs
Develop
Concept
Professional
Direct
Need
Study Guides
BY:
PM Tutor
COURSE STRUCTURE
BA Key Analysis &
Introduction
Concept Monitoring
Module 1
Module 2 Module 3
Designs
Develop
Concept
Direct
Need
Elicitation & Requirement Strategy
Collaboration Lifecycle Analysis
Module 4 Module 5 Module 6
COURSE STRUCTURE
Requirements Solution
Analysis Evaluation
Module 7 Module 8
Designs
Develop
Concept
Direct
Need
Underlying
Techniques Perspectives
Competencies
Module 10 Module 11
Module 9
COURSE OBJECTIVE
At the end of this course, you will
understand what business analysis is all
about, why it is essential to the success of
Designs
Develop
Concept
any project and how to perform it on your
Direct
Need
projects...
Certified Business Analysis Professional
BA Key Concept
Designs
Develop
Concept
Direct
Need
Module 2
MODULE OBJECTIVE
Business Analysis Core Concept Model™
Key Terms
Designs
Develop
Concept
Direct
Need
Requirements Classification Schema
Stakeholders
Requirements and Designs
The Business Analysis Core Concept Model™ (BACCM)
It 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
The six core concepts in the BACCM are: Change, Need, Solution,
Develop
Concept
Terms
Direct
Stakeholder, Value, and Context.
Each core concept is an idea fundamental to the practice of business analysis, and all the
concepts are equal and necessary. Each core concept is defined by the other five core
concepts and cannot be fully understood until all the concepts are understood. No single
concept holds greater importance or significance over any other concept. These concepts are
instrumental to understanding the type of information elicited, analyzed, or managed in
business analysis tasks.
The Business Analysis Core Concept Model™ (BACCM)
The BACCM can be used to:
• describe the profession and domain of business analysis,
• communicate about business analysis with a common terminology,
Develop
Concept
Terms
Direct
• evaluate the relationships of key concepts in business analysis,
• perform better business analysis by holistically evaluating the relationships
among these six concepts, and
• evaluate the impact of these concepts and relationships at any point during a
work effort in order to establish both a foundation and a path forward.
The Business Analysis Core Concept Model™ (BACCM)
Develop
Concept
Terms
Direct
The Business Analysis Core Concept Model™ (BACCM)
Develop
Concept
Terms
Direct
The Business Analysis Core Concept Model™ (BACCM)
While planning or performing a task or technique, business analysts can consider
how each core concept is addressed by asking questions such as:
• What are the kinds of changes we are doing?
• What are the needs we are trying to satisfy?
Develop
Concept
Terms
Direct
• What are the solutions we are creating or changing?
• Who are the stakeholders involved?
• What do stakeholders consider to be of value?
• What are the contexts that we and the solution are in?
If any of the core concepts experience a change, it should cause us to re-evaluate
these core concepts and their relationships to value delivery.
The Business Analysis Core Concept Model™ (BACCM)
Develop
Concept
Terms
Direct
Key Terms
Business Analysis
The BABOK® Guide describes and defines business analysis as the practice of enabling change
in an enterprise by defining needs and recommending solutions that deliver value to
stakeholders.
Business Analysis Information
Business analysis information refers to the broad and diverse sets of information that
business analysts analyze, transform, and report. It is information of any kind—at any level of
Schema
Concept
detail—that is used as an input to, or is an output of, business analysis work. Examples of
Terms
Direct
business analysis information include elicitation results, requirements, designs, solution
options, solution scope, and change strategy. It is essential to expand the object of many
business analysis activities from 'requirements' to 'information' to ensure that all inputs and
outputs of business analysis are subject to the tasks and activities.
Risk
Risk is the effect of uncertainty on the value of a change, a solution, or the enterprise.
Business analysts collaborate with other stakeholders to identify, assess, and prioritize risks,
and to deal with those risks by altering the likelihood of the conditions or events that lead to
the uncertainty.
Key Terms
Design
A design is a usable representation of a solution. Design focuses on understanding how
value might be realized by a solution if it is built. The nature of the representation may
be a document (or set of documents) and can vary widely depending on the
circumstances.
Schema
Concept
Terms
Direct
Enterprise
An enterprise is a system of one or more organizations and the solutions they use to
pursue a shared set of common goals. These solutions (also referred to as organizational
capabilities) can be processes, tools or information. For the purpose of business analysis,
enterprise boundaries can be defined relative to the change and need not be constrained
by the boundaries of a legal entity, organization, or organizational unit.
An enterprise may include any number of business, government, or any other type of
organization.
Key Terms
Organization
An autonomous group of people under the management of a single individual or board,
that works towards common goals and objectives. Organizations often have a clearly
defined boundary and operate on a continuous basis, as opposed to an initiative or project
team, which may be disbanded once its objectives are achieved.
Schema
Concept
Plan
Terms
Direct
A plan is a proposal for doing or achieving something. Plans describe a set of events, the
dependencies among the events, the expected sequence, the schedule, the results or
outcomes, the materials and resources needed, and the stakeholders involved.
Requirement
A requirement is a usable representation of a need. Requirements focus on understanding
what kind of value could be delivered if a requirement is fulfilled.
The nature of the representation may be a document (or set of documents), but can vary
widely depending on the circumstances.
Requirements Classification Schema
• Business requirements: 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.
• Stakeholder requirements: describe the needs of stakeholders that must be met in order
to achieve the business requirements. They may serve as a bridge between business and
Stakeholder
solution requirements.
Schema
Concept
Terms
• Solution requirements: describe the capabilities and qualities of a solution that meets
the stakeholder requirements. They provide the appropriate level of detail to allow for the
development and implementation of the solution. Solution requirements can be divided
into two sub-categories:
• functional requirements: describe the capabilities that a solution must have in terms
of the behavior and information that the solution will manage, and
• non-functional requirements or quality of service requirements: do not relate
directly to the behavior of functionality of the solution, but rather describe conditions
under which a solution must remain effective or qualities that a solution must have.
Requirements Classification Schema
• Transition requirements: describe the capabilities that the
solution must have and the conditions the solution must meet
to facilitate transition from the current state to the future state,
but which are not needed once the change is complete.
Stakeholder
Schema
Concept
Terms
They are differentiated from other requirements types
because they are of a temporary nature. Transition requirements
address topics such as data conversion, training, and business
continuity.
Stakeholders
For the purpose of the BABOK® Guide, the generic list of stakeholders includes
the following roles:
Stakeholder
• business analyst, •project manager,
Designs
Schema
Concept
Terms
•customer, •regulator,
• domain subject matter expert, • sponsor,
• end user, • supplier, and
• implementation subject matter expert, •tester.
• operational support,
Requirements and Designs
Requirements are focused on the need; designs are focused on the solution.
The distinction between requirements and designs is not always clear. The same techniques are
used to elicit, model, and analyze both. A requirement leads to a design which in turn may drive
the discovery and analysis of more requirements.
Stakeholder
The shift in focus is often subtle.
Designs
Schema
Concept
The classification as a requirement or a design may become less significant as the business
Terms
analyst's work progresses to a greater understanding of and eventual fulfillment of the need
A requirement (or set of requirements) may be used to define a design.
That design may then be used to elicit additional requirements that are used to define more
detailed designs.
The business analyst may hand off requirements and designs to other stakeholders who may
further elaborate on the designs. Whether it is the business analyst or some other role that
completes the designs, the business analyst often reviews the final designs to ensure that they
align with the requirements.
Requirements and Designs
Concept
Stakeholder
Terms
Schema
Designs
Requirements and Designs cycle
Concept
Stakeholder
Terms
Schema
Designs
Check
Knowledge
Introduction
Q &A
Integrate
Monitor
Direct
Develop
Manage
Charter
Knowledge Check
1. What knowledge area contains the next MOST logical steps after the
business analyst has built a business case and gained management
approval for a project?
Integrate
Introduction
A. Solution Assessment and Validation
Develop
Monitor
Manage
Charter
Q &A
B. Business Analysis Planning and Monitoring
Direct
C. Requirements Management and Communication
D. Requirements Analysis
B. Business Analysis Planning and Monitoring
Knowledge Check
2. The system users have stated their needs for revised online order entry system
capabilities. Her team needs the ability to perform online, remote order entry
when they are traveling worldwide. What class or type of requirements best
describe this need?
Integrate
Introduction
Develop
Monitor
Manage
A. Functional requirements
Charter
Q &A
Direct
B. Business requirements
C. User requirements
D. Transition requirements
A. Functional requirements
Knowledge Check
3. The business analysis team has put together the elicitation results documenting
their understanding of the user needs. What types of requirements have they
developed at this point in time?
A. Maintained and reusable
Integrate
Introduction
Develop
Monitor
Manage
B. Communicated and confirmed
Charter
Q &A
Direct
C. Validated and confirmed
D. Stated and unconfirmed
D. Stated and unconfirmed
Knowledge Check
4. Identifying key roles and selecting requirements activities is done as part
of which knowledge area?
A. Requirements Analysis
Integrate
Introduction
Develop
B. Requirements Development
Monitor
Manage
Charter
Q &A
Direct
C. Business Analysis Planning and Monitoring
D. Requirements Elicitation
C. Business Analysis Planning and Monitoring
Knowledge Check
5. Requirements gathering activities are also known as requirements:
A. Planning
B. Development
Integrate
Introduction
Develop
Monitor
Manage
Charter
C. Analysis
Q &A
Direct
D. Elicitation
D. Elicitation
Knowledge Check
6. What represents the information and preconditions necessary for a
business analysis task to begin?
A. Activity
Integrate
Introduction
B. Input
Develop
Monitor
Manage
Charter
Q &A
Direct
C. Output
D. Technique
B. Input
Knowledge Check
7. You are a business analyst measuring alternatives against objectives and
identifying tradeoffs to determine which possible solution is best. You are most
likely engaged in what activity?
A. Problem solving
Integrate
Introduction
B. Systems thinking
Develop
Monitor
Manage
Charter
Q &A
Direct
C. Creative thinking
D. Decision making
A. Problem solving
You
Thank
Introduction
Q &A
Integrate
Monitor
Direct
Develop
Manage
Charter
