Engineering Test Management and Engineering Requirements Management DOORS integration
When you integrate IBM® Engineering Test Management with IBM Engineering Requirements Management DOORS® , you can link requirement collections or modules from DOORS with test plans from Engineering Test Management and requirements from DOORS with test cases or test script steps from Engineering Test Management.
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 Engineering Test Management and DOORS versions that you use. For more information, see the following table:
Linking types between Engineering Test Management and DOORS
| Linking type | Engineering Requirements Management DOORS version | Engineering Test Management version |
|---|---|---|
| Back link support | Up to 9.6.1.3 | Latest version |
| Link discovery support | From 9.6.1.4 | 6.x |
| Linking with a configuration management-enabled project area | From 9.7 | 7.x |
Using back links
When you create a link with the external artifacts in an Engineering Lifecycle Management (Engineering Lifecycle Management) 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. But, in case of CM- disabled Project area with OSLC API operation, back-link is not getting created between the external artifact and source artifact. Thus, linking the artifact needs to be done externally. For example, when any requirement is linked to test case (in CM disabled PA) in Engineering Test Management, it doesn't create a requirement to test case link in RM. A manual linking of requirements to test case in RM is necessary.
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:
- 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 Engineering Test Management. With DOORS 9.6.1.4 or later, the link discovery service is used instead of back links between DOORS and Engineering Test Management. A state of synchronization cannot be guaranteed between bidirectional links and the traceability between source and target artifacts.
Integrating DOORS with configuration management-enabled Engineering Test Management project areas
Integration of configuration management-enabled Engineering Test Management project areas (from version 7.x) is enabled with DOORS from version 9.7.