Which of the following tasks is used to ensure that requirements and designs at different levels are aligned to one another?

Question

Options

• AGather requirements
• BAnalyze requirements
• CVerify requirements
• DTrace requirements

• A
  3% (1)
• B
  3% (1)
• C
  9% (3)
• D
  85% (28)

Explanation

Tracing requirements (D) is the correct answer because traceability is specifically the practice of linking requirements and designs across different levels (e.g., business → system → component) to ensure they remain aligned and consistent with one another - this is exactly what a traceability matrix does.

• A (Gather requirements) is wrong because gathering is about eliciting and collecting requirements from stakeholders, not checking alignment between levels.
• B (Analyze requirements) is wrong because analysis focuses on understanding, clarifying, and modeling requirements - not verifying cross-level consistency.
• C (Verify requirements) is wrong because verification checks that requirements are well-formed, complete, and unambiguous, not that they align across hierarchy levels (that distinction is subtle but important).

Memory tip: Think of trace like following a thread - traceability literally "traces" a requirement from the top level down through each design level, so you can see exactly where it lives at every stage.

No community discussion yet for this question.