CBAP · Question #47
You are the business analyst for your organization and you are completing the manage requirements traceability process. You are tracking the requirements to determine how the requirements are…
The correct answer is D. Quality control. The three defined purposes of requirements traceability are impact analysis, requirements coverage, and requirements allocation - quality control is a separate concern.
Question
You are the business analyst for your organization and you are completing the manage requirements traceability process. You are tracking the requirements to determine how the requirements are interrelated with one another and with the actual delivery of the project scope. There are actually three reasons why the business analyst should trace requirements. Which one of the following is not one of the three reasons why trace requirements is useful?
Options
- AImpact analysis
- BRequirements coverage
- CRequirements allocation
- DQuality control
How the community answered
(47 responses)- A2% (1)
- B13% (6)
- C9% (4)
- D77% (36)
Why each option
The three defined purposes of requirements traceability are impact analysis, requirements coverage, and requirements allocation - quality control is a separate concern.
Impact analysis is one of the three valid reasons for tracing requirements, enabling the BA to understand how a change to one requirement affects related requirements and deliverables.
Requirements coverage is one of the three valid reasons, ensuring every requirement is mapped to a solution element so nothing is overlooked.
Requirements allocation is one of the three valid reasons, assigning requirements to specific solution components and release iterations.
According to BABOK-aligned BA practice, the three specific reasons for tracing requirements are impact analysis (assessing the ripple effect of changes), requirements coverage (confirming all requirements are addressed in the solution), and requirements allocation (linking requirements to solution components and releases). Quality control is a distinct process focused on verifying outputs meet standards, not a purpose of requirements traceability.
Concept tested: Three purposes of requirements traceability management
Source: https://www.iiba.org/standards-and-resources/babok/
Topics
Community Discussion
No community discussion yet for this question.