Interoperability of collaborative Application Lifecycle (collaborative ALM)

Options for integrating rational ClearQuest with rational Team concert or rational Quality Manager

Learn this article to integrate IBM rational ClearQuest with rational Team concert and rational Quality Manager to implement Program Lifecycle Management (ALM) interoperability options.

This article uses a new ibm®jazz™ based tool to provide guidance to the enterprise team. Such teams often want to integrate with existing projects or set up change management workflows, and they need interoperability of tools to integrate new change management tools with existing tools.

Deployment and integration of a new Jazz-based tool with existing change management workflows can be summed up in two scenarios, each representing specific requirements, and choosing the right interoperability strategy for new deployments and integrated scenarios:

In the first case, teams based on tools such as Ibm®rational team concert™ and Ibm®rational®quality Manager might want to participate fully in a canonical change management operation as a ibm®rational Implement the enterprise-side change management deployment on the ®clearquest®. Under this condition, the integration through synchronization is the recommended method.

In another case, a team that uses the collaborative Application Lifecycle Management (C/alm) approach and team change management operations may choose an integration strategy based on traceability created through the linkage of the enterprise change Management resource.

In both cases, implementing an interoperability scenario will also provide the user with more powerful collaborative functionality of Rational ClearQuest.

This article describes more details about adoption and explains how you can choose and deploy interoperability strategies for a variety of integration scenarios.

Methods of Change Management

The next scenario gives you more information to help you decide on the interoperability approach.

The change management method of traditional specification

Regulatory change management is an easy to build operation that is easy to use by most software delivery agencies. Figure 1 illustrates this approach. It consists of an End-to-end workflow to ensure that the control of the change request passes through the defined lifecycle. This lifecycle begins with the submission of the change request, followed by the implementation and validation of the result change, and finally the resolution of the request.

Figure 1. Standard Change Management workflow