What does traceability to requirements ensure in software verification?

• A. Mapping each design output to the originating requirement to show coverage.
• B. Tracking only budgetary constraints.
• C. Recording only user preferences.
• D. Making the design process longer.

Answer: (A)

Traceability to requirements means you can map every design output and test case back to the exact requirement it satisfies. This shows coverage and proves that each requirement is implemented and verified, and it supports impact analysis if requirements change. By enabling bidirectional traceability—linking from requirements to artifacts and from artifacts back to requirements—you can quickly identify gaps, justify changes, and ensure auditability and compliance. It’s not about budgets or user preferences, and while there is some overhead, this approach helps prevent missed requirements and reduces rework later.