Traceability Links and Suspect Links
76
Chapter 5 - Creating Requirements
Exercise: Link the use case requirement to a feature requirement.
1
In the RequisitePro
Explorer
window, go to ClassicsCD Web Shop > Database Views >
Traceability Matrix Views
, then double-click Use Cases to Features relationships.
RequisitePro displays this view, showing the entire hierarchy of requirements. To
see more details, you may need to move the horizontal and vertical dividers of the
matrix.
2
Scroll to UC7 and, if necessary, expand it to see the child requirements.
3
Right-click the cell at the intersection of FEAT1 and UC7. From the shortcut menu,
click Trace To.
An arrow symbol appears in the cell, showing the relationship. The Arrange
Shipment use-case requirement and its child requirements, including the
requirement you just added, are now linked to this feature.
4
Browse this view of the requirements using the scroll bars to learn more about the
relationships between use cases and features.
Traceability Links and Suspect Links
The matrix in the RequisitePro View shows some of the links between requirements.
These links describe dependencies between requirements.
An arrow with a line through it (
) indicates that the link is suspect. A link becomes
suspect after a requirement in the link relationship changes. An analyst must examine
the changes, and decide whether to modify one or both requirements before clearing
the suspect link.
Other Requirement Types
So far, we've discussed high-level feature requirements and more detailed use case
requirements. Some requirements do not lend themselves to use cases, so
RequisitePro supports other types of requirements. For example, you can define
supplemental requirements for performance targets and platform support. Additional
requirement types include: design requirements, business needs, and glossary
requirements.
You can also define new requirement types. RequisitePro can manage any type of
requirement that you need on your project.
