Traceability is defined by identifying which relationships
between requirement types - or other artifacts -- are important enough to track and maintain.
| Selected Representation |
For each traceability relationship, a grid is prepared in
which the rows are of one requirement type - for example, features -- and the columns are of another requirement type -
for example, business objectives - or are of an artifact type outside of the requirements practice - for
example, test cases. Whenever an item in a row relates to an item in a column, put a mark in the intersecting cell
to represent the traceability relationship.
The table below shows an example of traceability
between business objectives and features.
|
Features \ Business Objectives
|
-bus_obj_01-
|
-bus_obj_02-
|
-bus_obj__03-
|
--bus_obj_04-
|
......
|
|
-feature_01-
|
|
X
|
|
|
|
|
-feature_02-
|
X
|
X
|
|
X
|
|
|
-feature_03-
|
X
|
|
X
|
|
|
|
-feature_04-
|
|
|
|
X
|
|
|
........
|
|
|
|
|
|
|