Integrating the Requirements Management application with IBM Rational Change

Edit online

You can integrate IBM® Rational Change with the Requirements Management (RM) application in the IBM Engineering Lifecycle Management (ELM). You can link RM requirement artifacts with change requests in Rational Change.

Note: The capabilities of the RM application in ELM are provided by IBM Engineering Requirements Management DOORS® Next (DOORS Next).

Configuring the integration

For information about configuring the integration, see these help topics in the Rational Change documentation:

The Rational Change documentation uses the integration with IBM Engineering Test Management (ETM) as an example. Other OSLC integrations are configured in a similar way. If you need to supply the root services URI for the RM application, the typical format is https://host-name:9443/rm/rootservices.

Optionally, you can modify a Rational Change lifecycle so that the RM application can automatically create links from change requests (CRs) back to their related RM requirements. In Rational Change, add these string attributes to your lifecycle and show forms with the OSLC_LINK web type:
  • tracksRequirement
  • affectsRequirement
For more information, see a similar integration with ETM that is described in Integrating with OSLC consumers in the Rational Change documentation.

Linking requirement artifacts and change requests

After the integration is configured, your team can create links between ELM RM artifacts and CRs in Rational Change.

In Rational Change, change requests can be configured as various types, such as defect, task, or enhancement. You can add links in Rational Change CR show forms in the relatedChangeRequests attribute. Select the RM application from the Friends list and create a link to a requirement artifact. For more information, see Integrating with an OSLC provider.

In the RM application, use the Implemented By link type to link requirement artifacts to CRs in Rational Change. You cannot link requirement modules or collections to CRs, but you can link artifacts in a module or a collection. For information about similar lifecycle linking from the RM application, see Linking to development, design, test, and requirement artifacts.