ECBA practice question 23 of 25

What tool can be used to determine the impact of a changed requirement on other requirements?

Full set: 210 questions
Answer options
A: Verification
B: Traceability Correct answer
C: Interview
D: Workshop
Correct Answer:
B. Traceability
Explanation

Traceability is the practice of linking requirements to other requirements, business objectives, and solution components throughout the project life cycle. When a requirement is changed, these established links are used to perform impact analysis. By tracing the relationships from the changed requirement, a business analyst can identify all other requirements, test cases, and system components that will be affected. This makes traceability the fundamental tool for understanding the ripple effect of a change.

Why Incorrect

A. Verification: Verification ensures that a requirement is well-formed, clear, and meets quality standards. It does not analyze the requirement's impact on other requirements.
C. Interview: An interview is an elicitation technique used to gather information from stakeholders. It is not a tool for systematically determining the dependencies between requirements.
D. Workshop: A workshop is a collaborative event. While impact analysis might be performed during a workshop, the workshop itself is the forum, not the underlying tool that shows the relationships.

References

1. International Institute of Business Analysis. (2015). A Guide to the Business Analysis Body of Knowledge (BABOK Guide) (Version 3). IIBA.

Section 5.1

Trace Requirements: The purpose of this task is "to ensure that requirements and designs at different levels are aligned to one another and to manage the effects of change to one level on related levels."

Section 5.1.1

Purpose: Explicitly states that tracing is used to support "requirements allocation and release planning

and impact analysis."

Section 5.1.5

Impact Analysis: "Traceability is used to help assess the impact of a change. Business analysts trace requirements to the affected stakeholders

solution components

or other requirements to identify all of the elements that will be affected by a proposed change."

2. Pohl

K. (2010). Requirements Engineering: Fundamentals

Principles

and Techniques. Springer.

Chapter 11

Section 11.2.2

Change Management: "Traceability information is the prerequisite for analyzing the consequences of a change request. Based on the traceability links

the requirements engineer can determine which other artifacts are affected by a change." (p. 261). DOI: https://doi.org/10.1007/978-3-642-12578-2

Scroll to Top