Which artifact helps ensure that all requirements are satisfied by design and test cases?

Which artifact helps ensure that all requirements are satisfied by design and test cases?

• A. Risk register
• B. Requirements Traceability Matrix
• C. Project Schedule
• D. Stakeholder Register

Answer: (B)

The artifact that ensures all requirements are addressed through design and testing is the Requirements Traceability Matrix. It creates a clear link from every requirement to the design elements that realize it and to the test cases that verify it. This visibility helps you confirm complete coverage—so nothing important is left out—and makes it easy to spot gaps where a requirement isn’t mapped to any design component or test. It also supports impact analysis when a requirement changes, showing which parts of the design and which tests are affected. For example, a requirement about data encryption would be connected to the relevant design module and the concrete test cases that validate encryption works in practice. Other artifacts like a risk register, project schedule, or stakeholder register serve different purposes (risk management, timelines, and stakeholder information) and don’t provide the same end-to-end mapping from requirements to design and tests.

The artifact that ensures all requirements are addressed through design and testing is the Requirements Traceability Matrix. It creates a clear link from every requirement to the design elements that realize it and to the test cases that verify it. This visibility helps you confirm complete coverage—so nothing important is left out—and makes it easy to spot gaps where a requirement isn’t mapped to any design component or test. It also supports impact analysis when a requirement changes, showing which parts of the design and which tests are affected. For example, a requirement about data encryption would be connected to the relevant design module and the concrete test cases that validate encryption works in practice. Other artifacts like a risk register, project schedule, or stakeholder register serve different purposes (risk management, timelines, and stakeholder information) and don’t provide the same end-to-end mapping from requirements to design and tests.