What is the term used to describe the cost of the solution after the solution has been implemented
in production by a vendor?
D
Explanation:
Total cost of ownership (TCO) is a financial estimate that helps consumers and enterprise managers
determine direct and indirect costs of a product or system. TCO goes beyond the initial purchase
price or implementation cost to consider the full cost of an asset over its useful life. It is a key
concept in the business analysis tasks of enterprise analysis and solution assessment and validation.
TCO can help evaluate the feasibility and viability of different solution options and compare them
with the business need and expected benefits. Reference:
IIBA BABOK Guide v3
, p. 30, 176, 264
CBAP 150 Practice Questions Flashcards
, Question 1
Production Costs: What They Are and How to Calculate Them - Investopedia
Cost of Solution vs. Cost of Problem · Jens Oliver Meiert
Enterprise analysis creates just five outputs.
Which one of the following is an output of the enterprise analysis tasks?
D
Explanation:
A solution approach is a description of the proposed method for delivering a solution that meets the
business need. It is one of the outputs of the enterprise analysis tasks, along with business need,
capability gaps, solution scope, and business case. A solution approach defines the type, nature, and
complexity of the solution, and provides a high-level view of how the solution will be implemented.
It also identifies the major components, features, and functions of the solution, as well as the key
stakeholders, risks, assumptions, and constraints. A solution approach helps to evaluate the
feasibility and viability of different solution options and compare them with the business need and
expected benefits. Reference:
IIBA BABOK Guide v3
, p. 30, 176, 264
An Overview of Enterprise Analysis - Modern Analyst
How Do You Know When You Are Doing Enterprise Analysis
All of the following stakeholders participate in the prioritization of requirements except for which
one?
A
Explanation:
Stakeholders are individuals or groups who have an interest in the outcome of a project and can
influence its success. Stakeholders can be classified into different categories based on their roles,
responsibilities, and perspectives. One common way to categorize stakeholders is by using the RACI
matrix, which stands for Responsible, Accountable, Consulted, and Informed. According to this
matrix, the following stakeholders participate in the prioritization of requirements:
Project team: Responsible for delivering the solution that meets the requirements. They are directly
involved in the prioritization process and provide input on the feasibility, effort, and risk of each
requirement.
Domain subject matter expert: Consulted for their expertise and knowledge of the business domain
and the needs of the end users. They provide input on the importance, value, and urgency of each
requirement.
Project manager: Accountable for the overall success of the project and the alignment of the
requirements with the project scope, schedule, and budget. They facilitate the prioritization process
and ensure that the stakeholders reach a consensus on the priority levels.
The implementation subject matter expert is not a stakeholder who participates in the prioritization
of requirements. They are Informed of the prioritized requirements and the rationale behind them,
but they do not provide input or influence the prioritization process. They are responsible for
implementing the solution according to the requirements and ensuring that it meets the quality
standards and specifications. Reference:
IIBA BABOK Guide v3
, p. 30, 176, 264
Five Requirements Prioritization Methods - Business Analyst Articles …
What Is Requirements Prioritization? Definition & Examples - airfocus
Business analysts : How to prioritize requirements - Adaptive US
[5 Popular Requirements Prioritisation Techniques]
You are the business analyst for your organization. Management has asked that you create a model
of the requirements so the stakeholders can better understand the requirements and the project as a
whole.
Which of the following statements best describes a model?
D
Explanation:
A model is a representation of a system or a process that helps stakeholders and customers visualize
the potential system. Models can use different forms, such as flowcharts, graphs, diagrams, or
prototypes, to show the structure, behavior, or functionality of the system. Models are useful for
communicating, analyzing, verifying, and validating the requirements.
Models are not slices of the project solution (A), although they may show some aspects of the
solution. Models are not meant to simplify the requirements for common stakeholders (B), but
rather to help all stakeholders understand the requirements better. Models are not statistics for the
return on investment, time saved, and other mathematics ©, although some models may use
quantitative data to support the requirements.
What plan will describe the stakeholder groups, communication needs, and the level of formality
that is appropriate for the requirements?
D
Explanation:
A business analysis communication plan is a document that describes how the business analyst will
communicate with the stakeholders, including the stakeholder groups, communication needs, level
of formality, frequency, format, and methods of communication. It is one of the outputs of the
business analysis planning and monitoring knowledge area, and it helps to ensure that the
stakeholders are informed, engaged, and satisfied with the business analysis process and
deliverables. A business analysis communication plan is not the same as a project communication
plan, which covers the overall communication needs of the project and is typically created by the
project manager. A business analysis communication plan focuses on the specific communication
needs related to the business analysis activities and requirements. Reference:
IIBA BABOK Guide v3
, p. 36, 38, 40, 42
How to Create a Stakeholder Management Plan Smartsheet
CBAP 150 Practice Questions Flashcards
, Question 5
How To Create an Effective Stakeholder Communication Plan
You are the business analyst for a smaller project where there are few requirements. Management
would still like you to create a method to trace the few requirements for this project.
What type of matrix would be best in this instance?
D
Explanation:
A requirements trace matrix (RTM) is a tool that helps to ensure that the project’s scope,
requirements, and deliverables remain consistent and aligned throughout the project lifecycle. It
traces the requirements from their origin to their fulfillment by linking them to other project
artifacts, such as design documents, test cases, and solution components. An RTM can also be used
to verify that all requirements are met and to identify changes to the scope when they occur. An RTM
is especially useful for smaller projects where there are few requirements, as it can help to track the
progress and status of each requirement and avoid scope creep. A requirements trace matrix is not
the same as a roles and responsibility matrix (A), a RACI matrix (B), or a coverage matrix ©, which
are different types of matrices that serve different purposes in project management. Reference:
IIBA BABOK Guide v3
, p. 30, 176, 264
Requirements Traceability Matrix – RTM - Project-Management.com
CBAP/CCBA/ECBA Certification Practice Test | MindsMapped
, Question 6
You are the business analyst for your organization and have many solutions available to an identified
problem. You would like a way to quickly and fairly determine which solution is the best choice for
your organization.
Which of the following approaches would allow you to determine the top-rated solutions for your
organization?
A
When an organization is using a change-driven approach to business analysis, how are
communications managed?
A, B
Explanation:
According to the BABOK Guide, a change-driven approach to business analysis is characterized by
frequent delivery of value to stakeholders, iterative planning and feedback, and adaptive responses
to changing needs and priorities. In such an approach, communications are managed by focusing
more on the frequency of communication and using face-to-face channels as much as possible. This
helps to ensure that information is shared quickly and effectively, and that feedback loops are
established and maintained. Formal communications are less emphasized in a change-driven
approach, as they may slow down the delivery process and introduce unnecessary overhead. Ad hoc
communications are not sufficient for managing change-driven projects, as they may lead to
inconsistency, confusion, and missed information. Reference:
BABOK Guide
, section 2.5.3, page 35
How to create a business analysis communication plan
, paragraph 2
CBAP/CCBA/ECBA Certification Practice Test
, question 8
You are the business analyst for your organization. Management has asked that you create a method
to store the project requirements including those under development, under review, and the
requirements which have been approved.
What is management asking you to create?
B
Explanation:
A repository is a centralized place where project requirements are stored and managed throughout
the project lifecycle. A repository can be a physical or electronic system that allows business analysts
to access, update, and track the status of the requirements. A repository can also facilitate the
communication, collaboration, and verification of the requirements among the stakeholders. A
repository is not the same as a change management system (A), a project scope statement ©, or a
requirements register (D), which are different tools or documents that serve different purposes in
project management. Reference:
IIBA BABOK Guide v3
, p. 30, 176, 264
How to Write Project Requirements | Smartsheet
, paragraph 3
What is Requirements Management? | IBM
, paragraph 1
You are the business analyst for your organization and working with Tim to identify the assumptions
within the business solution.
Which one of the following is an assumption?
A
Explanation:
An assumption is a factor that is considered to be true, real, or certain without proof or
demonstration. In this case, the vendor’s belief about the hardware delivery date is an assumption
because it is not verified or guaranteed. The other options are not assumptions, but rather
requirements, constraints, or criteria that the business solution must meet. Reference:
CBAP / CCBA
Certified Business Analysis Study Guide
, Chapter 2: Business Analysis Planning and Monitoring, page
62.
Certified Business Analysis Professional (CBAP®) Handbook
, page 6.
You are working with Terry on the conduct stakeholder analysis task as part of the business analysis
duties in your company. Terry wants to know why it's so important to identify stakeholders so early in
the business analysis duties.
Which one of the following statements best addresses the need to identify the stakeholders early on
in the business analysis duties?
C
Explanation:
Identifying the stakeholders early on in the business analysis duties helps the business analyst to
understand the needs, expectations, and interests of the stakeholders, as well as their influence and
authority on the project. This helps the business analyst to plan and manage the requirements
activities, communicate effectively with the stakeholders, and address any issues or conflicts that
may arise. By involving the stakeholders throughout the business analysis process, the business
analyst can ensure that the requirements deliverables are aligned with the stakeholder needs and
expectations, and that they are delivered on time and within budget. Reference:
IIBA, A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3, 2015, p.
30-311
IIBA, Business Analysis Competency Model, Version 4, 2018, p.
Nancy has asked you to trace a particular requirement for her.
What does 'to trace a requirement' mean?
B
Explanation:
According to the Wikipedia article on requirements traceability1
, tracing a requirement means to
follow the life of a requirement in both a forwards and backwards direction, from its origins, through
its development and specification, to its subsequent deployment and use, and through periods of
ongoing refinement and iteration. Tracing a requirement helps to ensure that the requirement is
linked to a business objective, that it is consistent and aligned with other requirements and
deliverables, and that it is verified and validated by the stakeholders. Tracing a requirement can also
help to identify the impact of changes, the source of defects, and the gaps in the requirements.
Option A is incorrect because it does not mention the business requirements, which are the high-
level needs and objectives of the organization or the customer. Option C is incorrect because it does
not mention the stakeholder and solution requirements, which are the detailed and specific
requirements that define the scope and functionality of the solution. Option D is incorrect because it
describes tracking a requirement, not tracing a requirement. Tracking a requirement means to
monitor the progress and status of a requirement throughout the project lifecycle, not to link it to
other related artifacts.
When do change requests generally increase in a project?
B
Explanation:
Change requests are more likely to occur in the early stages of a project, when the requirements are
being elicited, analyzed, and validated. During this time, stakeholders may discover new needs,
identify gaps, or revise their expectations. Change requests may also arise due to changes in the
business environment, such as new regulations, market trends, or competitor actions. Change
requests are less frequent in the later stages of a project, when the requirements are more stable
and the solution is being designed, developed, and tested. Reference:
A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3, Chapter 4:
Requirements Life Cycle Management, Section 4.5: Manage Changes1
CBAP Certification Study Guide v3.0, Chapter 4: Requirements Life Cycle Management, Section 4.5:
Manage Changes2
Ben is the business analyst for his organization. Ben is currently working on a solution to improve a
laser printer. He has taken the laser printer apart, identified each component, and documented each
component's purpose.
What type of requirements organization is Ben doing in this scenario?
C
Explanation:
Functional decomposition is a technique that breaks down a complex system or process into smaller
and simpler parts, each with a specific function or purpose. By doing so, it helps to understand the
structure, behavior, and functionality of the system or process, and to identify the requirements for
each part. In this scenario, Ben is doing functional decomposition by taking the laser printer apart
and documenting the purpose of each component. This can help him to improve the performance,
quality, or efficiency of the laser printer by analyzing and optimizing each component’s
function. Reference:
[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section
10.31.2.11
[CBAP Certification Study Guide v3.0], Chapter 6: Requirements Analysis and Design Definition,
Section 6.3: Organize Requirements, page 2502
Project Management: Different Types of Requirement - Visual Paradigm
, paragraph 4
Fred's organization is using a plan-driven approach for the business analysis deliverables.
In this approach how will the requirements be captured?
D
Explanation:
A plan-driven approach to business analysis is characterized by a high degree of upfront planning,
detailed documentation, and formal processes. In this approach, the requirements are captured
using standardized templates that provide a consistent and comprehensive format for describing the
business needs, objectives, and specifications. The templates may include sections such as scope,
assumptions, constraints, risks, acceptance criteria, and traceability. The templates are usually
predefined by the organization or the project management office, and they help to ensure the
quality, clarity, and completeness of the requirements. The templates also facilitate the
communication, verification, and validation of the requirements among the stakeholders.
Reference:
Plan Business Analysis Approach - iiba.org
, page 1
How to Choose the Right Business Analysis Approach
, paragraph 4
Business analysis approach planning – The Functional BA
, paragraph 2