Finding bad links across RRC, RTC and RQM
We have a good number of situations where links and back links are not always present. Example: We see many instances where a Requirement artifact has a list of Test Cases where the Test Cases are back linked successfully. We see many instances where a Test Case is linked to a Requirement but the Requirement is not showing the Test Case. Here is a table to help illustrate the issue.
We have similar issues with linking between RTC and RQM. This also affects the data warehouse and any traceability reporting.
Is there a way to find bad links and possibly repair them so that we can have confidence in the traceability reporting? We are using CLM 3.0.1.4 with RRDI 2.0
|
One answer
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
You can find/fix/remove missing forward/back links using the OSLC V2 APIs. For example, see the source code for the unofficial OSLC Cleaner Utility attached to ConcurrentModificationException when removing broken forward links using the OSLC Cleaner. (62209).
We will look into this utility! Thank you for the information!
Are there utilities available for fixing links between...RRC <-> RTC and
RQM <-> RTC as well?
The OSLC Cleaner Utility is not supported but rather made available as a sample. You are welcome to use it as-is or refactor the source.
Does IBM offer something that is supported?
Matthew, please open a PMR.