Tracing Beyond The Requirements
Requirements are realized into design artefacts, implementation, and are finally verified, the artefacts tied to the latter stages should be traced back to the requirements as well. This is typically done via a Requirements Traceability matrix.
Establishing traceability beyond requirements into design, implementation, and verification artefacts can become difficult. When implementing software requirements for instance, the requirements may be in a requirements management tool, while the design artifacts may be in Matlab/Simulink, Rhapsody, or Microsoft Visio.
Furthermore, implementation artefacts will likely be in the form of source files, links to which can be established in various ways at various scopes. Verification artefacts such as those generated by internal tests or formal verification tools (i.e. The LDRA tool suite, Parasoft Concerto, SCADE)
Repository or tool stack integration can present a significant challenge to maintaining traceability in a dynamic system.
Read more about this topic: Requirements Traceability
Famous quotes containing the word tracing:
“Our life is a faint tracing on the surface of mystery, like the idle, curved tunnels of leaf miners on the face of a leaf. We must somehow take a wider view, look at the whole landscape, really see it, and describe what’s going on here. Then we can at least wail the right question into the swaddling band of darkness, or, if it comes to that, choir the proper praise.”
—Annie Dillard (b. 1945)