Traceability with DOORS 9 and RQM


Continuing the series of articles on the topic of creating traceability documents I have arrived at an interesting use case:  traceability from DOORS 9 and RQM.

doors2rqm_output

In this article I will describe how to create a document with requirements from DOORS 9 and their associated test cases from RQM.

You need to have DOORS 9, DOORS Web Access, QM installed and integrated. In my environment I am using DOORS 9.6.1 and QM 5.0.2 deployed on a Windows 7×64 machine. In the screenshot below I have 2 DOORS 9 requirements “validated by” RQM test cases.

doors2rqm_data

The procedure is identical to the one for creating traceability documents from Rhapsody to RQM.  Actually for building the template for this article I have reused the QM_TC_Snippet.dta referenced in that article.

The steps are:

  1. Iterate the DOORS 9 requirements
  2. Get the external links of type http://open-services.net/ns/rm#validatedByNOTE : The link is the OSLC URL of the test case which cannot be used directly for document generation. You need to get the Reportable REST URL first and this is what the next 2 steps do.
  3. Get the OSLC representation of the QM testcase
  4. From the OSLC representation read the Reportable REST URL for the QM resource
  5. Get the Reportable REST representation of the QM tescase and print it in your document

doors2rqm_template

The template is available on the RPE Developer Works Wiki Unclassified & Cross Domain Templates page.

For more information on how to generate traceability documents from RQM I recommend reading Dr. Einar Karlsen’s excellent Using IBM Rational Publishing Engine to generate compliance documents: Part 1. Report generation for Rational Quality Manager, introducing REST service URLs, importing schemas, and basic template authoring

 

Advertisements

Author: Dragos Cojocari

Architect for Rational Publishing Engine

3 thoughts on “Traceability with DOORS 9 and RQM”

  1. I tried to run your DTA but keep getting unconfigured data source error.

    Currently I am now trying to replicate the use of getting requirements in DOORS associated with test cases in RQM. I am following: https://rpeactual.com/2015/11/20/traceability-with-doors-9-and-rqm/

    I have gotten to the point where I am importing a REST v2 OSLC schema, however, RDF/TestCase/Relation is not an option in my imported schema.

    I am using this base URL: https://server:/qm/oslc_qm/catalog
    I am authenticating with Basic Authentication and using the default query capability for TestCase.
    The only option to select on the next page is oslc_qm:testCase http://open-services.net/ns/core#Resource

    Shouldn’t there be a relation option?

    When I try to use form or OAuth authentication, I get two different error messages.

    For form authentication, I get ‘Response message: Unauthorized’.
    For OAuth authentication, I get ‘Can not access to the OAuthentication URL’.

    Suggestions?

    1. Hi Dylan,

      Did you finally find the solution? I ‘m trying to build a report involving Rational DOORS Requirements and RQM Test Cases and I’m facing the same problems you mentioned.

      I loop through all the requirements in the module and extract the external links.

      Then I import the Rest v2 schema selecting Test Case capability but no relation option appears in the schema so it’s being imposible for me to reach Test Cases at the moment.

      I appreciate any help.

      Thanks.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s