How to integrate RRC, RTC and RQM

Hi Sandeep. The webinar you saw presented some prototyping we have done to show tighter integration across the ALM products (Rational Team Concert, Rational Quality Manager, Rational Requirements Composer).

There's nothing available to try out at the moment, but this is a key area that we're working to support for our June 2009 release.

What kinds of integration scenarios would you expect to be supported?

For the benefit of others, here's the link to the demo video on the jazz team blog:
https://jazz.net/blog/index.php/2008/12/01/surfing-the-collaborative-alm-web-%E2%80%93-rtc-rqm-and-rrc/

This tighter integration of RRC, RTC and RQM that's mentioned, does that include the ability to share the same repository database? This would be critical in repository backups.

If the tight integration does include sharing the same repository database, as I would expect it to, I have a couple of further questions:

- will the three products use the same project area or different project areas? I believe RQM currently creates a hard coded project area implicitly (I'm not sure about RRC).

- my team is using RTC and considering using RQM and RRC products at the 1.0 level. If we do, will we be able to consolidate them into a single repository database in 2.0 as part of the migration? If the integration will be down to the project area level (i.e. sharing of project areas), will the migration handle that as well?

We're trying to determine what the consequences of adopting the 1.0 release of these products will be and whether we'll have to maintain separate databases as a result. Thanks.

This tighter integration of RRC, RTC and RQM that's mentioned, does that include the ability to share the same repository database? This would be critical in repository backups.

From what I have been able to learn from existing product documentation, obtaining the traceability from requirements to deployment using RRC, RTC and RQM requires the RequisitePro V7.1 Web to interface with RRC V1.0. RequisitePro interfaces with ClearQuest and through the RTC CQ Connector you have the CQ and RTC connection. RQM V1.0 also interfaces with RequisitePro V7.1.
Unless I missed something in the documentation, using V1.0 RRC and V1.0 RQM with RTC seems a little heavy weight with a higher cost of ownership than a seamless integration between these three ALM tools.

I don't believe that repository sharing is part of the plan for 2.0. If
repository sharing ever does become a supported features, I imagine that
tools to help migrate to that setup would be included.

-
Matt Lavin
Jazz Server Team


On Tue, 2009-01-20 at 15:57 +0000, kmunir wrote:

If the tight integration does include sharing the same repository
database, as I would expect it to, I have a couple of further
questions:

- will the three products use the same project area or different
project areas? I believe RQM currently creates a hard coded project
area implicitly (I'm not sure about RRC).

- my team is using RTC and considering using RQM and RRC products at
the 1.0 level. If we do, will we be able to consolidate them into a
single repository database in 2.0 as part of the migration? If the
integration will be down to the project area level (i.e. sharing of
project areas), will the migration handle that as well?

We're trying to determine what the consequences of adopting the 1.0
release of these products will be and whether we'll have to maintain
separate databases as a result. Thanks.

thloeberwrote:
This tighter integration of RRC, RTC and RQM that's mentioned, does
that include the ability to share the same repository database? This
would be critical in repository backups.