When you modify a requirement's name, text, or type or the attributes associated with requirements that are traced to or from one another, the relationship between the requirements requires attention. RequisitePro signals this suspect condition with a red diagonal line through the traced to or traced from arrow in a Traceability Matrix or Traceability Tree. Note that when requirements change, only direct traceability relationships become suspect; indirect relationships are not affected.
For example, if traceability relationships exist between Requirements A and B and between Requirements B and C, and you modify Requirement A, the relationship between Requirements A and B becomes suspect, but the relationship between Requirements B and C does not. Requirement B may need to be updated to reflect the modifications made to Requirement A.
A red line through the arrow indicates that the traceability relationship is suspect. This occurs when either of the requirements has been modified after the initial traceability relationship has been established.
In a Traceability Tree, a suspect relationship is flagged as follows:
(In an Attribute Matrix, a suspect relationship is denoted by an "(s)" in the Traced to or Traced From columns.)
Your ability to modify traceability depends upon the security permissions that have been assigned to you as a user. Permissions define your ability to create, modify, and remove traceability relationships and also mark and clear suspect traceability relationships. If security has not been restricted on your project, all of these actions are available to you by default.