Tag: RQM

Categories
Rational Quality Manager

Broken Back Links to DOORS and DNG

When linking to requirements, the links are not always formed correctly. In these cases the link is visible from RQM but not from DOORS or DNG.

To address this first enable Back Link Checks via the preferences window:

Then

Ensure the bottom option is selected.

You can now return to a traceability view within RQM (for example browse Test Cases, if you now add the “Validates Requirements” column to the view, the Back Links check will be performed and a broken link symbol displayed when an issue is found. Note this can take some time to actually display.

Using the action menu on the broken link symbol enables the link to be repaired.

Categories
Rational Publishing Engine

Extracting RQM linked requirements from DOORS 9.x

When generating a report on RQM data using RPE you may want to include linked requirements. If the requirements are held in DNG then this is a relatively easy process. The complication is when the linked requirements are held in DOORS 9.x. In this situation the requirement data is extracted from DOORS Web Access (DWA).

The DWA requirement schema is not provided as part of RPE and is not discoverable. It must be loaded from a .xsd file. A sample DWA schema (which was downloaded from RPE Actual) is provided below.

DWA_Sample_SchemaDownload

This file should be saved locally and then when adding a data schema within RPE, the main.xsd selected as the schema file.

RQM will provide a requirement URI of the form:

https://[server]:[port]/dwa/rm/urn:rational::1-55bb46603d9c55be-0-10009-000bf60

Which can be used to dynamically configure the DWA data source.

Unfortunately, this only works for DWA requirements that are not linked to RQM!

When a requirement has an RQM link, it has a different schema. Within the above schema the main.xsd file must be modified with the following:

<xs:element name="RDF"> 
    <xs:complexType> 
      <xs:sequence> 
<xs:element name="Statement"> 
<xs:complexType> 
<xs:sequence> 
<xs:element name="subject"> 
<xs:complexType> 
<xs:sequence> 
<xs:element ref="oslc_rm:Requirement"/> 
</xs:sequence> 
</xs:complexType> 
</xs:element> 
</xs:sequence> 
</xs:complexType> 
</xs:element> 
<xs:element ref="oslc_rm:Requirement"/> 
      </xs:sequence> 
    </xs:complexType> 
  </xs:element>

Using the modified schema will then allow the requirement data to be extracted.