It's all about the answers!

Ask a question

Finding bad links across RRC, RTC and RQM


Aaron Cabrera (45816) | asked Mar 28 '13, 4:51 p.m.

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.


Req ID

Requirement Name

TC ID

Test Case

Name

Tool

View

Notes

12345

Example Requirement Name

12001

TC 1

RM

Links and Back Links Good

12345

Example Requirement Name

12202

TC 2

RM

Links and Back Links Good

12345

Example Requirement Name

12003

TC 3

RM

Links and Back Links Good

12345

Example Requirement Name

12004

TC 4

RM

Links and Back Links Good

12345

Example Requirement Name

14000

TC A

RQM

TC is Linked to Requirement - Requirement Not Linked to TC

12345

Example Requirement Name

14001

TC B

RQM

TC is Linked to Requirement - Requirement Not Linked to TC

12345

Example Requirement Name

14002

TC C

RQM

TC is Linked to Requirement - Requirement Not Linked to TC

12345

Example Requirement Name

14003

TC D

RQM

TC is Linked to Requirement - Requirement Not Linked to TC

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


Comments
Paul Slauenwhite commented Apr 02 '13, 7:54 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

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).


Aaron Cabrera commented Apr 02 '13, 1:20 p.m. | edited Apr 02 '13, 2:09 p.m.

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?


Paul Slauenwhite commented Apr 02 '13, 2:21 p.m.
FORUM MODERATOR / JAZZ DEVELOPER

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.


Matthew Owenby commented Apr 02 '13, 4:52 p.m.

Does IBM offer something that is supported?


Paul Slauenwhite commented Apr 03 '13, 9:26 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

Matthew, please open a PMR.

One answer



permanent link
Junli Wang (5512) | answered Mar 29 '13, 3:14 a.m.
JAZZ DEVELOPER
edited Mar 29 '13, 3:14 a.m.
need some clarification:
1. the link you mentioned is seen from Web UI or from BIRT report or RRDI report?
if they are from BIRT or RRDI report, the link is stored in data warehouse as 1 single instance. eg. REQUIREMENT_TESTCASE_LOOKUP, in the report, you will see query subjects like: [Requirement Related Test Cases] and [Test Cases Related Requirements], from either one, the result with the link is the same.
2. in the table, "View" is RM or RQM, what does that mean? Does it mean RM or RQM Web UI or something else?

Comments
Aaron Cabrera commented Apr 02 '13, 1:14 p.m. | edited Apr 02 '13, 1:19 p.m.

The column View is confusing.  Please disregard.
The column Req ID, Requirement Name, TC ID and Name are all from RRDI 2.0.

Notice that the list is for 1 requirement.  The first 4 Test Cases have good links between RM and QM that are seen in the application.

The Last 4 Test Cases - the Requirement 12345 is viewable in QM in each test case.  The test cases are not listed in RM for the requirement.

Your answer


Register or to post your answer.