dmmckinn 1200006SCS Visits (1221)
Integrations between Rational Team Concert and Rational ClearQuest
There are various types of integration capabilities between IBM Rational Team Concert (RTC) and Rational ClearQuest: the bridge, the synchronizer, and the importer. If you are looking for help in deciding which integration capability best suits your current deployment or your future deployment plan, read on to get a better understanding about the technologies that are available to you, as well as some of the deployment considerations.
Note: Additional "Getting Started" information and "Quick Tour" videos are available in the Rati
Rational ClearQuest Bridge
The Rational ClearQuest Bridge provides a bi-directional traceability link from records in Rational ClearQuest to work items in Rational Team Concert. It is a linked-data type integration based on the Open Services for Life-cycle Collaboration (OSLC). It provides a seamless user experience with rich hover UI preview, and delegated dialogs including advanced selection dialogs, and fully functional creation dialogs. These dialogs support ClearsQuest record form layout and hooks. The bridge integration also enables ClearQuest live data on a Rational Team Concert dashboard.
Rational ClearQuest Bridge is primarily for users who want to continue to use Rational ClearQuest as a change management system, but also want to take advantage of other features of Rational Team Concert, such as agile planning and dashboards. You do not have to change your current usage of Rational ClearQuest, but you can enhance your Rational ClearQuest deployment by using Rational Team Concert in a complementary fashion. It provides a ClearQuest shop with a fast path to realize the value of Rational Team Concert.
It is implemented as a function of the ClearQuest Web and uses the ClearQuest OSCL REST API interface. ClearQuest is an OSLC Change Management(CM) provider and a consumer. It provides OSLC CM v1 and v2 interfaces, and also consumes OSLC CM services provided by other tools. ClearQuest OSCL REST API is also a desired interface if you want to integrate your own application to ClearQuest. Since it is HTTP-based, you can call it from any program that supports HTTP, and it does not require the ClearQuest client to be installed on the machine where you execute your application.
Through the same bridge integration technology, you can also integrate ClearQuest with other Rational tools, such as Rational Quality Manager (RQM), Rational Requirement Composer (RRC), and Rational DOORS, and with 3rd party tools, such as HPALM and Git.
Rational ClearQuest Synchronizer
The Rational ClearQuest Synchronizer is a data replication between Rational ClearQuest records and Rational Team Concert work items. It supports flexible bi-directional or one-directional synchronization between a Rational ClearQuest record and a Rational Team Concert work item. Changes in one application are applied to another using synchronization rules, which provide the mapping and transformation information.
It is primarily for the customers that want to incrementally adopt Rational Team Concert by having different teams use different tools. Some projects/teams (for instance, a development team) can choose to start using Rational Team Concert while other teams (for instance, a support team) continue to use ClearQuest. The teams using Rational Team Concert and the teams using ClearQuest have access to the same data (duplicated by the Synchronizer based on the configured sync rules). Reports can also be run in either system since the data is consolidated.
The ClearQuest Synchronizer is implemented as an application of the general Jazz item connector framework. It is a separate component of the Rational Team Concert offering, and requires setting up a Gateway service. It uses ClearQuest CM API interface to communicate with ClearQuest. It can also be used between Rational Qualify Manager (RQM) and ClearQuest.
Please note that there is a high maintenance and support cost associated with the Rational ClearQuest Synchronizer. Conflicts can occur when two users make nearly simultaneous changes to a ClearQuest record and its corresponding work item, and an administrator needs to constantly monitor these conflicts and resolve them manually by selecting the appropriate value. It is highly recommend that you evaluate the Rational ClearQuest Bridge integration before jumping into the Synchronizer integration.
Rational ClearQuest Importer
The Rational ClearQuest Importer provides a one-way data migration from Rational ClearQuest records to Rational Team Concert work items. It imports ClearQuest records based on a user specified query, and uses a mapping file to declare how fields and values are mapped from a ClearQuest scheme to a Rational Team Concert process definition. It supports importing stateful record types, Users, Notes, Attachments, Work Item Relationships (duplicates, parent / child, blocks / depends on, and related), and creates missing objects, such as Contributors, categories, and iteration, on the fly.
The Rational ClearQuest Importer is primarily for the customers that want to move from using ClearQuest to Rational Team Concert as the change management system instead of maintaining both applications, and want to bring over certain ClearQuest records to Rational Team Concert.
It is implemented as a function in the Rational Team Concert eclipse client. It is based on the Bugzilla Importer, and uses the ClearQuest CM API to communicate to ClearQuest. You must install ClearQuest client on the machine you run the ClearQuest Importer.
IBM Rational Rhapsody family provides a collaborative design, development and test environment for systems engineers and software engineers. It uses Systems Modeling Language (SysML) and Unified Modeling Language (UML) to enable rapid requirements analysis and visual, model-based design.
The UML diagrams are views into the underlying semantic system model; each kind of diagram emphasizes some aspect of the model.
Example - Dynamic aspects is represented by behavior diagram - State chart.
Statecharts define the behavior of objects by specifying how they react to events or operations. The reaction can be to perform a transition between states and possibly to execute some actions. When running in animation mode, IBM Rational Rhapsody highlights the transitions between states.
The discussion covers few modeling challenges with state chart using Rational Rhapsody and how to over come those challenges:
1) Evaluation of condition connector in state chart
A scenario where a variable (count) is decremented before the condition connector and is expected to terminate if value of variable is 9 (count==9).
However, on executing you observe that the condition doesn’t take the change in the variable on the transition. Instead it takes the initial value of the variable for comparison.
The work around here is to have an additional dummy state in between to get the desired output.
2) Multicasting with rapid ports in layered structure
Currently, the multicasts of event via rapid ports (ports that have no provided/required interfaces) are supported only from a direct invocation.
Example - One sender object and two receiver objects
Consider a scenario where the event is first sent from the Class A's object(itsA) and then it reaches the Class B's object(itsB), from where it is delegated to its 2 inner parts(itsB1 and itsB2
No multicasting is available on having multi layered structure.
The Workaround is to add an additional state chart and MULITCAST_GEN() macro in class B.
3) Working of Reaction in State
In a single state for a Reactive class, you would expect to continuously print a statement after elapse time of tm (1000). However, upon execution it prints only once instead of continuous timer.
Using a tm (1000) as a trigger for a reaction in state means that 1 second after you enter the state you'll be triggered. It's not a continuous timer.
To restart the timer you have to exit the state and re-enter it. It needs a design change as below.
4) Combining Junction Connector and Condition Connector in a state chart
You would like to have several events from a state and a condition to determine the other state.
You cannot join several transitions into a condition connector neither you can have a transition from a junction connector to a condition connector.
However, you can model to add a dummy state in between that will further evaluate for condition connector.