Continuing the Assemble traceability documents from reusable building blocks I want now to add QM data in the mix. I will be using the same DM model as a starting point and I will follow links to QM Test Cases.
As you read this I recommend also going through Geoff Rosenthal’s the excellent Rational solution for Collaborative Lifecycle Management Traceability Templates with Rational Publishing Engine tutorial.
The artefacts for this tutorial are available on the Unclassified & Cross Domain Templates section of the RPE Wiki Community at #15 DM to CLM Traceability.
Getting the DM link information is already covered in Assemble traceability documents from reusable building blocks so I will skip it here. This article starts from the point where you have your DM and DM link data in place in your template.
How QM linking works
But before I go there I want to explain how QM linking works and what are the various schemas you will encounter in the process.
QM, just like all the other CLM products has an OSLC API that is used for linking. A QM Test Case will be referenced from another product using a URL that looks like this:
For the example I am presenting you can get these URLs from the link page of the DM artifact. And if you access these URLs from a tool like Poster and specify “application/xml” for the “accept” header you can see the data available. One thing you will notice is that even though the data is not in the form you are used to when reporting on QM with RPE which is the QM’s Reportable REST API.
Unlike DNG there is no way to convert from the RQM OSLC v2 URL to the Reportable REST URL but for QM the OSLC representation of the QM artifact contains the link to the RQM Reportable REST URL.
So to get from the OSLC URL to the Reportable REST URL you firsy need to access the OSLC resource, read the Reportable REST URL and then accesses the data there.
How QM linking works – TL;DR version
When you want to access linked QM data you need to:
- access the OSLC representation of the artifact
- you need to use RPE’s Reportate REST v2 schema discovery to find the schema form QM’s OSLC representation. The starting point for the schema discovery process is https://server:port/qm/oslc_qm/catalog
- read the URL to the Reportable REST representation of the QM artefact
- access the Reportable representation of the artefact
- Use the data as needed
- RQM OSLC v2 REST API – for linking data
- RQM Reportable REST API – for document generation
Get linked QM Data from DM
- Insert the QM_TC_Snippet.dta in the indicated position
- Edit the condition on the QM Container such that you are only processing QM Data. I have used the “link type” property to only accept “Validated By” links
- Connect the QM snippet to your template by specifying
- A data source to have the QM_OSLC_TC inherit from
- The data property that holds the OSLC QM URL
- Make a test run to verify all the pieces fit together. Just like with the RTC example you only need to specify the entry point and credentials for accessing the DM UML project.
NOTE: You will need to replace the QM schema from my snippet with your particular QM schema so that you can use the custom attributes defined in your particular QM instance.
You now have 2 RPE snippets for accessing RTC and QM linked data that you can reuse in your traceability documents. I recommend evaluating your existing templates to identify other sections in your templates that you use on a regular basis and transform them in reusable snippets.