 |
The aforementioned simplistic approach to traceability indeed has merit, and it is a first step in the right direction. But is it complete? No. Does it satisfy modern engineering standards such as SEI CMM/I, DO-178B Traceability, DO-254 Traceability, IEC-61508, or FDA 510(k) standards? Absolutely not. What are the shortcomings with this simplified approach to traceability?
- There is no traceability to the implementation components, necessary during the review of such components
- There is no traceability between increasing levels of requirement granularity, necessary to corroborate the requirements decomposition process
- There is no traceability to design data, necessary to review and maintain such data
- There is no ability to isolate extraneous implementation components, such as unused code
To remedy these shortcomings, modern standards require traceability which is more detailed, more complete, and which traces not only forwards but backwards as well.RelyTRACE is unique in that it satisfies such traceability requirements, while allowing the user the flexibility to define the traceability structure and the tagging mechanisms with which to implement that traceability. |