RPE team at Interconnect 2016

The RPE team will be represented at Interconnect 2016 by the RPE Product Manager Jared Pulham, the RPE Dev Lead Nithya Rajagopalan and myself. We will be joining the Inner Circle’s QM, CM and RM tracks on Sunday, present sessions and roam the Solution Expo the remainder of the week.

With the Session Preview Tool you can get a sneak peak at the sessions dedicated to Publishing Engine, Reporting and any other topics of interest.

We are looking forward to seeing you there. Please contact any of us via email if you’d like to meet with us and chat about your reporting experience.

Advertisements

More traceability – following links from RQM

Continuing the series of articles on producing traceability documents from IBM CLM I will describe today how to follow links from RQM.

If you examine the RQM schema for testcase for example you will notice entries for workitems and requirements.

qm_schema
Click on the image to enlarge it.

With these properties it should be fairly straightforward to build a template that retrieves CM and RM data associated with the QM artefacts.

However if you run your report on a test case feed URL like https://giediprime:9443/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/JKE Banking (Quality Management)/testcase?abbreviate=false there is no requirement or work item data in the document. And if you examine the XML returned by RQM for this request you will see that information is not present there either.

So what is the problem? The answer is in the Rational Quality Manager Reportable REST API Documentation.  For efficiency reasons RQM does not return the link information by default. If you want to create traceability documents you’ll have to explicitly ask for the link information using the calmlinks argument in the request URL.

qm_calm_links
Which means that the right URL to use in the RPE docspec will look like this https://giediprime:9443/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/JKE Banking (Quality Management)/testcase?abbreviate=false&calmlinks=true

Note that the URLs to RTC and DNG are OSLC links and you will need to convert them to Reportable REST API URLs before fetching RM and CCM data.

Examples showing how to follow links from individual testcase or from a test case feed are available in the RPE DevWorks – Cross Domains Templates Wiki.

Accessing individual workitems through RTC’s Reportable REST API

When accessing individual RTC work items through the reportable REST API there are two ways of going about it.

Embed the work item ID in the URL as a filter

https://giediprime:9443/ccm/rpt/repository/workitem?fields=workitem/workItem[id=36]/(description|summary|severity|state)

Embed the work item ID in the URL as  a path segment

https://giediprime:9443/ccm/rpt/repository/workitem/workItem/id/36?fields=workitem/workItem[id=36]/(description|summary|severity|state)

Using the ID in the path segment is especially convenient when following links to RTC as it allows to convert the OSLC URL to Reportable REST without requiring additional variables and native filters as described in Assemble traceability documents from reusable building blocks.

Assemble traceability documents from reusable building blocks

When building a template you can take advantage of the reuse capabilities that RPE Template and Document Studio provide.  You can use this for any documents and traceability documents are a great candidates since they usually involve the same steps over and over again:

  1. Read the data from Product A and print the details you need
  2. In the data of Product A find the links to data in Product B
  3. Read the data from Product B and render it

The above is the outline of any 2 source traceability report and steps 2 and 3 are almost identical for all reports so they can be packaged as blocks to be reused as needed.

To show this I have created a document with DM and RTC data. The artifacts I use in my example are available on the Unclassified & Cross Domain Templates section of the RPE Wiki Community at #15  DM to CLM Traceability.

Continue reading “Assemble traceability documents from reusable building blocks”

CLM 6.0

More details here, https://jazz.net/blog/index.php/2015/06/26/collaborative-lifecycle-mangagement-6-0-in-a-nutshell/ and here:

For document generation, CLM 6.0 ships with RRDG 1.3 iFix 003 which is significant as it allows to use all the latest in template design.

Creating traceability documents with RPE and JRS

If you have ever had to generate a document that contains Requirements, the Test Cases that validate them and the related work items you’ve most likely ended up using (at least) 3 different data sources and you’ve had to use Java Script to switch between APIs.

Aside from a complex design, the performance of the report wasn’t that great as RPE had to crawl over all the data sources to fetch the required data.

JRS_Selecting_Data

Continue reading “Creating traceability documents with RPE and JRS”