Engineering Test Management and Engineering Requirements Management DOORS integration

When you integrate IBM® Engineering Test Management (ETM) with IBM Engineering Requirements Management DOORS® (DOORS), you can link requirement collections or modules from DOORS with test plans from ETM and requirements from DOORS with test cases or test script steps from ETM.

Open Services for Lifecycle Collaboration (OSLC) is used to integrate ETM (from version 5.x) with DOORS (from version 9.6).
Note: ETM versions 5.x and higher do not support the RQMi integration with DOORS.

OSLC integration

When you upgrade to the latest version of DOORS, you must migrate to the OSLC integration instead of RQMi integration or configure the OSLC integration for the first time. For more information about upgrading, see the Engineering Requirements Management DOORS documentation.

Artifact linking when using OSLC

Various integration options are available depending on the ETM and DOORS versions that you use. For more information, see the following table:

Linking types between and and DOORS

Linking type Engineering Requirements Management DOORS version and version
Back link support Up to Latest version
Link discovery support From 6.x
Linking with a configuration management-enabled project area From 9.7 7.x
Note: Back links are not supported for configuration management-enabled projects.

Using back links

When you create a link with the external artifacts in an Engineering Lifecycle Management (ELM) workbench source application, a link is automatically created with the source artifacts in the target application. The link in the target application is called a back link. When a link is created between the source artifact and an external artifact, the back link gets created between the external artifact and the source artifact. These links are referred to as bidirectional links.

The source and target applications store the 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, are completed in the source application server. In such cases, the corresponding back links in artifacts in the target application are not automatically added or removed. There can also be instances where the 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 differently based on your starting view point.

The accuracy of traceability reports might be affected if bidirectional links are not in a synchronized state. For example:

A report that is run against artifacts in the target application might provide different results than a report that is run in the source application against the same artifacts. Links to the following artifacts are included in this limitation:
  • Requirement collections
  • Development plans
  • Requirements
  • Change requests, such as Defects, Tasks, Plan Items, and Stories

Using link discovery

With link discovery, artifacts that are related by a single link are stored by ETM. With DOORS or later, the link discovery service is used instead of back links between DOORS and ETM. A state of synchronization cannot be guaranteed between bidirectional links and the traceability between source and target artifacts.

Integrating DOORS with configuration management-enabled ETM project areas

Integration of configuration management-enabled ETM project areas (from version 7.x) is enabled with DOORS from version 9.7.