from RRC to HP Quality Center

we would like to send our requirements from RRC to HP quality Center(skipping RTC).

we are considering OSLC , but is there a simpler solution?

any suggestions??

For the current release of Requirements Composer 3.x we have relied on spreadsheet transfer methods or 3rd party vendors to provide a mechanism for exchanging requirements with information held in HPQC. We've also seen numerous examples of some RRC project teams transferring requirements from HPQC to RRC using the MS Word and spreadsheet import utilities. You certainly have these options to help you.

Beyond RRC 3.x some users here on jazz.net will be aware that Rational is working on an IBM integration initiative this year where we will have an automated integration between RRC (CLM) and HPQC. This integration solution would allow traceability (connectivity) between development projects between the two repositories and not require data transfer. We expect to provide more details on this integration as soon as possible.

-------------------------------------------------
Jared Pulham
Senior Product Manager, Requirements Management for CLM

we would like to send our requirements from RRC to HP quality Center(skipping RTC).

we are considering OSLC , but is there a simpler solution?

any suggestions??

we are using a bsd solution to transfer requirement work items form RTC to HPQC, and are relying on the rtc feature of "generating work items from collections" to transfer /link RRC requirements to RTC.

but here is where we get stuck , in our efforts to integrate RRC/RTC with HPQC...



"The generating work items from collections" feature transfer all attributes of the requirement to RTC EXCEPT the primary text. but this is the most important attribute of a requirement in RRC. it contains all the details.

well we found a work around to this ...

after getting the requirement work items generated and created in RTC. we then use a csv file containing the primary text content , and import this file into rtc; since the cvs file contains the requirement ID along with teh primasry text, it will Update the existing requirement work items with the primary text.

this works well...except for one catch...

the Import csv does get teh content of the primary text into our requirement work items nicely EXCEPT it wont import/update non-textual content. So the Basic and Alternate flows of our use cases do not come into RTC (teh structure is somewhat garbled) because we put the steps of these flows as a table in our RRC primary text.

tables are nontextual so the Import doesnt bring the table into the requirement works items , in a structured manner.

we are so close...but this shuts down our clm solution

any suggestions or qwork arounds ??

 Hello,

You might also find this article useful for an additional future option https://jazz.net/library/article/855