Traceability is defined as:

Traceability is defined as:

• A. The ability to estimate project duration
• B. The ability to trace the history, application, or location of an object/entity/item
• C. A practice for risk management
• D. A method for distributing responsibilities among teams

Answer: (B)

Traceability means you can follow the history, application, or location of an object from its origin to its current state. In systems engineering, this lets you connect a requirement to every artifact that implements or verifies it, such as design elements, code, tests, and deployment notes. With traceability, changes are manageable: if a requirement evolves, you can see all items affected and ensure nothing important is missed, verify that every requirement is covered by tests, and support configuration management and regulatory compliance. This makes it possible to answer questions like where a component came from, where it’s used, and how it’s been modified over time. The other options refer to different activities: estimating how long a project will take, practicing risk management, or assigning responsibilities among teams, none of which describe tracing the lineage or location of items through the development lifecycle.

Traceability means you can follow the history, application, or location of an object from its origin to its current state. In systems engineering, this lets you connect a requirement to every artifact that implements or verifies it, such as design elements, code, tests, and deployment notes. With traceability, changes are manageable: if a requirement evolves, you can see all items affected and ensure nothing important is missed, verify that every requirement is covered by tests, and support configuration management and regulatory compliance. This makes it possible to answer questions like where a component came from, where it’s used, and how it’s been modified over time.

The other options refer to different activities: estimating how long a project will take, practicing risk management, or assigning responsibilities among teams, none of which describe tracing the lineage or location of items through the development lifecycle.