When a business analyst performs requirements tracing, he may need to trace the requirements backward...

According to the BABOK® Guide, allocation is “the process of assigning stakeholder and solution requirements to solution components in order to provide a common understanding of the scope and value of each component” (p. 36). Allocation is a type of forward traceability, as it traces the requirements from their origin to their implementation in the solution. The other options are not correct because:

Lineage tracking is a type of backward traceability, as it traces the requirements from their current state to their source (p. 36).

Backwards pass is a term used in project management, not in requirements traceability. It refers to the process of calculating the late start and late finish dates for project activities (p. 215).

Derivation is another type of backward traceability, as it traces the requirements from their current state to their parent requirements (p. 36). References:

BABOK® Guide, p. 36, 215

Requirements Traceability: Definition, Why it matters & Tools, section “Forward Traceability”