|
|
You can implement requirements tracing with hyperlinks, which associate pairs of VOB objects. The association should be at the version level (rather than the branch or element level): each version of a source code module must be associated with a particular version of a related design document.
For example, the project manager creates a hyperlink type named DesignDoc, which is used to associate source code with design documents:
cleartool mkhltype -c "associate code with design docs" ^
DesignDoc@\dev DesignDoc@\design
Created hyperlink type "DesignDoc".
Created hyperlink type "DesignDoc".
The hyperlink inheritance feature makes the implementation of requirements tracing easy:
When the source module, hello.c, and the design document, hello_dsn.doc, are updated, the project manager creates a new hyperlink connecting the two updated versions:
cleartool mkhlink -c "source doc" DesignDoc hello.c \design\hello_dsn.doc
Created hyperlink "DesignDoc@90@\dev".
When either the source module or the design document incorporates a minor update, no hyperlink-level change is required: the new version inherits the hyperlink connection of its predecessor.
cleartool checkin -c "fix bug" hello.c
Checked in "hello.c" version "\main\2".
To list the inherited hyperlink, use the -ihlink option to the describe command:
When either the source module or the design document incorporates a significant update, which renders the connection invalid, the project manager creates a null-ended hyperlink to sever the connection:
cleartool mkhlink -c "sever connection to design doc" DesignDoc hello.c
Created hyperlink "DesignDoc@94@\dev".
Figure 43 illustrates the hyperlinks that connect the source file to the design doc.
Figure 43 Requirements Tracing
|
|
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |
