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
What part of defining the business needs process will evaluate the ends that the organization is
seeking to achieve?
A
Explanation:
According to the BABOK Guide, defining the business needs is the process of identifying the ends
that the organization is seeking to achieve. Business goals and objectives are statements of the
desired outcomes of the change initiative that align with the organization’s strategy and vision. They
provide the context for identifying and evaluating alternative solutions that can satisfy the business
needs. Alternative identification, solution assessment, and requirements are parts of other processes
that follow defining the business needs. Reference:
BABOK Guide
, Chapter 5: Strategy Analysis, Section 5.1: Define the Business Need, p. 100-101
CBAP Certification Study Guide v3.0
, Chapter 5: Strategy Analysis, Section 5.1: Define the Business
Need, p. 5-3 to 5-4
What type of a business analysis approach focuses on the rapid delivery of business value in short
iterations?
B
Explanation:
A change-driven approach to business analysis is one that adapts to the changing needs and
priorities of the stakeholders and the business environment. It focuses on delivering business value
in short iterations, rather than following a fixed and detailed plan. A change-driven approach is often
associated with agile methodologies, such as Scrum, Kanban, or XP, which emphasize collaboration,
feedback, and continuous improvement. A change-driven approach can help business analysts
respond to uncertainty, complexity, and ambiguity, and deliver solutions that meet the customer’s
expectations and satisfaction. Reference:
Defining Business Analysis
, section 1.3.2, page 7
How to Choose the Right Business Analysis Approach
, paragraph 4
Business Analysis Approach
, paragraph 2
The Agile Business Analysis Approach Means…
, paragraph 1
Defining the Business Analysis Approach in 2023
, paragraph 2
Wanda is the business analyst for her organization and she is currently working on the specify and
model requirements process. One of the elements of this process is the documentation of the textual
requirements.
Wanda must describe the capabilities of the solution, any conditions that must exist for the
requirements to operate, and what third component of the textual requirement?
A
Explanation:
According to the BABOK Guide, textual requirements are one of the forms of specifying and
modeling requirements. Textual requirements are written statements that describe the
characteristics of the solution in a clear, concise, and consistent manner. Textual requirements
typically consist of three components: the capability of the solution, the condition under which the
requirement is applicable, and the constraint that may limit the solution. The capability describes
what the solution must or should do, the condition describes the situation or scenario in which the
requirement is relevant, and the constraint describes the restriction or limitation that may affect the
solution’s ability to meet the requirement. For example, a textual requirement for a banking system
could be:
The system shall allow customers to withdraw cash from any ATM machine (capability) within the
network (condition) up to a maximum of $500 per day (constraint).
Reference:
[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section
10.31.2.11
Textual Requirement Artifacts - Blueprint Online Help - HelpDocs
, paragraph 1
How to Model Textual Requirements - Formal Mind GmbH
, paragraph 2
The business analysis approach generally defines all of the following attributes except for which one?
A
Explanation:
The business analysis approach is a plan that describes how the business analysis activities will be
performed, including the deliverables, the team roles, the analysis techniques, the communication
methods, the change management process, and the stakeholder engagement strategy. The business
analysis approach does not define the requirements for solutions acceptance, which are the criteria
that the solution must meet to be accepted by the stakeholders. The requirements for solutions
acceptance are part of the solution scope, which is an output of the enterprise analysis tasks, not the
business analysis approach. Reference:
[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 24, section
2.21
[CBAP Certification Study Guide v3.0], Chapter 4: Requirements Life Cycle Management, Section 4.1:
Plan Business Analysis Approach, page 4-22
Business Analysis Approach
, paragraph 1
Gary is the business analyst for his organization and he is preparing a presentation about the
requirements for a large software development project.
Before Gary makes the presentation what should he do as part of his preparation for the
presentation?
A
Explanation:
Before making a presentation about the requirements for a large software development project,
Gary should determine an appropriate format for the presentation. This means he should consider
the following factors:
The audience: Who are the stakeholders that will attend the presentation? What are their roles,
interests, and expectations? How familiar are they with the project and the requirements? How
much detail do they need to understand the requirements?
The purpose: What is the goal of the presentation? Is it to inform, persuade, or seek feedback from
the stakeholders? What are the key messages and takeaways that Gary wants to convey?
The time: How much time does Gary have to present the requirements? How can he allocate the
time effectively to cover the most important and relevant aspects of the requirements?
The tools: What tools and resources does Gary have to create and deliver the presentation? Does he
have access to a projector, a laptop, a microphone, or a whiteboard? What software or applications
does he need to use to create the presentation slides or documents?
The style: How can Gary make the presentation engaging, clear, and professional? What visual aids,
diagrams, charts, or examples can he use to illustrate the requirements? How can he use colors,
fonts, images, and animations to enhance the presentation? How can he structure the presentation
to have a logical flow and a strong introduction and conclusion?
By determining an appropriate format for the presentation, Gary can ensure that he communicates
the requirements effectively and efficiently to the stakeholders, and that he addresses their needs
and concerns.
Reference:
How to Make Interesting Presentations for Software Projects
, paragraphs 1-3
How To Write The Software Development Project Brief
, steps 1-7
Complete Guide to Software Development Requirements
, paragraphs 1-2