This information is for planning purposes only. The information herein is subject to change or removal without notice before the products described may become available.
The CE/CLM products were renamed in version 7.0. As the help is updated to reflect the changes, the topics might contain inconsistencies. For details on the name change, see Renaming the IBM Continuous Engineering Portfolio.

Linking test script steps to requirements in Engineering Requirements Management DOORS

If you have test scripts that fulfill multiple requirements, you can link a test script step to one or more requirements.

Before you begin

  1. Integrate IBM® Engineering Test Management with IBM Engineering Requirements Management DOORS® Version 9.4 or later by using Open Services for Lifecycle Collaboration (OSLC).
  2. Link a Quality Management project to a Engineering Requirements Management DOORS requirements project.
  3. Add test scripts to a test case that has associated requirements.
  4. By default, the Validates column in the test script editor that you use to link requirements to test script steps is disabled. To enable the Validates column in the Manual Steps table, see Setting test script preferences for requirements management.
  • Discovering and repairing missing back links is not supported for configuration management enabled projects.
  • If you have not enabled configuration management, when you create a link to external artifacts in a ELM application, a link is automatically created back to the source artifact in the target application, which is called a back link. However, the synchronization between bidirectional links and the traceability between source and target artifacts are not guaranteed.
Learn more about bidirectional links: When a source artifact and target artifact link to each other, this is known as bidirectional linking. The source and target applications store their links in separate databases, and the source application does not have access to the database in the target application. Certain transactional operations, such as when artifacts are copied or deleted, can occur on the source application server. In these cases, corresponding back links in artifacts in the target application are not automatically added or removed. Also, instances occur where back links are intentionally removed from the target application without removing the corresponding link from the source application. As a result, if bidirectional links are not in a state of synchronization, traceability between the source and target artifacts can appear different based on your starting viewpoint.


  1. Open an existing test script (Construction > Browse > Test Scripts) or create a new test script (Construction > Create > Test Script).
  2. If the attachments and links column is not shown, click the Show/hide Contents icon, and then select the Show Attachments/Links check box.
  3. To link a single step to a requirement that is associated with the parent test case:
    1. From the manual test editor toolbar, click the Show Requirement View icon (Show Requirement View) to open the Requirement View.
    2. In the Requirement View, select one or more requirements, and then click the Add Requirement Link icon (Add Requirement Link). The linked requirement is shown in the attachments and links column. Alternatively, drag the requirement link from the panel to the attachments and links column.
  4. To link a step to any requirement that is associated with the project:
    1. In a step, click the Action Menu icon (Action menu drop down), and then click Link to any Requirement.
    2. In the Links window, select a requirement from the Requirements Management project that is linked to this project.
    Tip: If you want requirement links in a test script to be automatically copied to the Requirement Links section of a parent test case when you add an existing test script to the test case, you can enable the Copy Requirement links into Test Cases when adding new child Test Scripts option in Test Scripts Preferences.

    When this preference is enabled, it also applies to a requirement link added to a step by using the Open Services for Lifecycle Collaboration (OSLC) QM API. In this scenario, a link is automatically created from the test case to the requirement that was linked to the test script step.

  5. Click Save.


Linked requirements are displayed in the Validates column of the table. In the Engineering Requirements Management DOORS application, links are created from the linked requirement to the test script artifact, not to the individual test script steps.

video icon Video channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community forums library

support icon Support

IBM Support Community
Deployment wiki