Traceability
This section is about traceability.
Traceability is an attribute of product documentation that allows you to demonstrate that consequent design decisions can be traced back to antecedent requirements.
Further that tests can be traced to requirements and so on.
For example; designs can be traced back to requirements and requirements can be traced back to needs.
In the old days (80s) we would use a word processor and build a Traceability Matrix.
In the left column we would write the requirement id and in subsequent columns the tests that demonstrated it or the design that implemented it.
A certain rigor is required in identification to make this possible.
For example you cannot use auto number in your word processor or else all the references will be skewed.
The id is a primary key and as such must be unique across products the test may be used in.
It must be possible to insert, delete and reorder tests with their IDs.
With the emergence of model based systems engineering we let the database do the tracing but someone has to audit the links to keep them up to date.
Test Engineers and Quality Analysts care about such things.
Back | Next
Copyright Spidel Tech Solutions, Inc. 2004 All Rights Reserved. Updated:
7/10/2009 6:33:58 PM
Idx: 1644 Site Design STS
