CCBA practice question 30 of 35

When a business analyst performs requirements tracing, he may need to trace the requirements backward through their lineage and may need to trace the requirements forward through their relationship to other requirements. What is the backwards tracing activity called in requirements traceability?

Full set: 638 questions
Answer options
A: Allocation
B: Lineage tracking
C: Derivation Correct answer
D: Backwards pass
Correct Answer:
C. Derivation
Explanation

In requirements traceability, tracing a requirement backward to its origin is known as tracing its derivation. This involves understanding the lineage of a requirement by linking it back to the higher-level business or stakeholder requirement from which it was derived. This ensures that every solution requirement directly supports a stated need and helps in performing impact analysis if the source requirement changes. The relationship type used for this is 'Derive', indicating that one requirement is a result of decomposing another.

Why Incorrect

A. Allocation is the process of assigning requirements to solution components or releases for implementation, which is a form of forward, not backward, tracing.
B. Lineage tracking is a general term for following the life of a requirement, but 'Derivation' is the specific term for the backward relationship to its source.
D. Backwards pass is a technique used in the Critical Path Method for project schedule analysis, unrelated to requirements traceability.

References

- A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3

Section 5.1.4.2

International Institute of Business Analysis

2015. (This section describes relationship types

including 'Derive'

which is fundamental to backward tracing).

- A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3

Section 7.4.4.2

International Institute of Business Analysis

2015. (This section discusses 'Relationship to Other Requirements' including derivation).

Scroll to Top