Creating a Traceability Link Between Requirements in the Requirements Structure Editor

You can select the source and target of a traceability link to establish a refining or covering relationship between the selected requirements in the Requirements Structure Editor.

Before you begin: The source and target requirements must already exist in the requirement specification structures that you open in Requirements Structure Editor. The source and target requirements can be in requirement specifications that are open as root objects in the same or different tabs.

After you open the Requirements Structure Editor instances, you must add a scope to the context of the requirements specifications using Systems Traceability Dashboarding. This helps you to automatically define the direction of traceability link created between the requirements in the Requirements Structure Editor instances. The Requirements Structure Editor is only aware of scopes created while it is open in the dashboard. Only the last scope added in any Systems Traceability Dashboarding instance open in the dashboard is available to the Requirements Structure Editor. If you remove the last scope added in any Systems Traceability Dashboarding, no scope is available to the Requirements Structure Editor.

See Also
Requirements Structure Editor
Requirements Structure Editor User Interface
Reordering Structures in the Requirements Structure Editor
Managing the Status of a Traceability Link Between Requirements in the Requirements Structure Editor
Removing a Traceability Link Between Requirements in the Requirements Structure Editor
Configuring Preferences for the Requirements Structure Editor
  1. Right-click the source requirement, and select Start Link.
  2. Navigate to the requirement specification that contains the target requirements.
  3. Right-click the target requirements, and select End Link.

    If there is a scope and context defined between the requirement specifications in Systems Traceability Dashboarding, the traceability link is automatically created using the existing context.

    If there is no scope and context defined between the requirement specifications in Systems Traceability Dashboarding, the Select a relationship dialog box opens.

  4. Select the traceability link direction:
    • Downstream Requirement means that the source requirement is refined into the target requirement.
    • Upstream Requirement means that the source requirement covers the target requirement.
    A downstream or upstream link is created with multiple requirements.

    Notes:
    • For creating links only requirement and its sub-types are supported.
    • An information message is displayed once all the links are successful. If one or more links fail, a panel is displayed with an error message.

  5. Click Confirm to create the traceability link.

The traceability link is created between the requirements. The Refined Into and Covers columns are updated when the content is indexed.