The ability to identify and document the lineage of each requirement, including its derivation. allocation, and relationship to other requirements is known as requirements.

Requirements traceability is the process of documenting the life of a requirement. It involves tracking the relationships between requirements and other system artifacts, such as design components, test cases, and business objectives. This lineage provides visibility and helps manage the impact of changes, ensuring that the final product aligns with the initial goals and that all requirements are addressed. The question provides a textbook definition of this concept.

A. Validation ensures the requirements meet stakeholder needs ("building the right product").
B. Management is the overall process of handling requirements; traceability is a specific activity within it.
C. Verification ensures the system is built according to the requirements ("building the product right").

1. Gotel, O. C. Z., & Finkelstein, A. C. W. (1994). An analysis of the requirements traceability problem. Proceedings of the First International Conference on Requirements Engineering, 94-101. https://doi.org/10.1109/ICRE.1994.292398. This foundational academic paper defines traceability as the ability to describe and follow the life of a requirement.

2. Pohl, K. (2010). Requirements Engineering: Fundamentals, Principles, and Techniques. Springer. Chapter 1, Section 1.2.3, "Requirements Traceability," defines it as the ability to trace a requirement both forwards and backwards through the development lifecycle.

3. Systems Engineering Body of Knowledge (SEBoK) v. 2.9. (2023). Requirements Traceability. The SEBoK defines requirements traceability as linking requirements to their sources and to the downstream work products created from them.