Jakeline, per Smallwood $(2017),$ traceability is the ability to monitor, trace, or track, requirements, needs, and expectations throughout the lifecycle of a process and into the final solution. Tracking requirements through the project ensures that all requirements are built into the design, all requirements are built into the solution, all requirements are tested and all requirements are implemented in the final solution. This is part of a structured lifecycle process.

The easiest way to create a link between your requirements and other development elements is by developing a Traceability Matrix outlining the requirements such as design and development, the needs such as the type of usage, and expectations such error free approach. This tracking requires the details as the requirements, needs, and expectations are proceeding through the lifecycle. However, it may be helpful to understand the details of the initial requirement, the design element, the component that contains the code for the requirement and the particular test case that ensured that the requirement worked correctly.

Traceability should be enforced throughout the lifecycle or else it does not work. If the team assigns tracking numbers to the requirements, but the requirements are not tracked in subsequent phases, the whole tracking scheme will break down $($Smallwood$,2017).$

How do you feel the above information applies to these types of inventories?