I’m writing this as a response to what seems to be a surge in interest for reporting on DOORS 9 data through the DOORS Web Access, or DWA. This integration is documented in the RPE Infocenter here and on my blog here.
The main point of this article is the scope and limitations of this integration. The RPE-DWA has been added to support exclusively traceability reports that start from other products (ex: RQM) and use DOORS 9 requirements through DOORS’ OSLC API. As such the RPE-DWA integration is only meant to support retrieving a single requirement at a time through it’s DWA URL.
For all and any scenario where multiple requirements are needed, such as getting the content of a module/view, the traditional DOORS 9 route is the only supported method.
As a rule of a thumb you should you should never use DWA as the starting point for a report. These URLs must be obtained dynamically from other data sources in your report.
It has to be noted as well that the DOORS OSLC API is not reportable which has two main implications for RPE and document generation. First this API lacks support for OLEs and images which means that only text content will be served correctly. Second there is no XML schema provided with the API (there is not a ?metadata=schema URL) nor there is a way to “discover” such a schema as we have for DOORS 9. The DWA example schema we have provided has been created manually from instances of the data.
To summarize the above for all scenarios other than the one explicitly stated above the RPE-DWA integration is not a viable nor is a supported alternative to the traditional RPE-DOORS 9 integration.