Sample assets in RPE Document Builder

Out-of-the-box sample assets have been available in the Rational Publishing Engine (RPE) Desktop installation of RPE Document Studio and RPE Launcher for many versions. These sample assets are now included within RPE Document Builder 2.1.1.

Find details at https://jazz.net/blog/index.php/2017/01/19/sample-assets-in-rational-publishing-engine-document-builder/

 

Printing DOORS Object Heading without line break

While extracting Object heading from DOORS using RPE, RPE will try to retain DOORS heading formatting and styles and the heading is put in a new line. For example, add Object ID or Heading Number before Object Heading in a RPE template as below:

rpetemplate

Though you expect the RPE document to show Heading Number and Object Heading in same line, they will be shown in separate lines. Continue reading “Printing DOORS Object Heading without line break”

OSLC API and POX Profile simplifies CLM traceability

Further to OSLC + POXProfile post, RPE 2.1 with CLM 6.0.2 simplifies the data source configuration; especially while configuring dynamic data source for traceability reports.

Use OSLC / Permanent link for configuring the data source URL without having to modify the URL manually or through JavaScript. This simplifies the data source configuration to a great extent as the Permanent / OSLC links are available to the user from the product UI.

Watch video, created by Dragos, on requirement (DNG) to use case design (DM) traceability document generation using Permanent / OSLC links from DNG and DM without having to go through building Rest URL. Continue reading “OSLC API and POX Profile simplifies CLM traceability”

Studio Integrated with 2.1 Web application

RPE Studio 2.1 could now access assets from RPE 2.1 Document Builder (Web Services). The templates, snippets and stylesheets from 2.1 web services are available in Studio 2.1. The “Load From Library” in Open Template dialog lists templates and snippets, which could be view, modified and saved back to the web app.

The remote services preference setting is similar to how remote services 1.x were configured. However, the service URL should be pointed to RPE 2.1 web service URL. Find complete documentation here. Continue reading “Studio Integrated with 2.1 Web application”

DOORS and DOORS Next Generation Enlightenment Series 2016

I’ve received this from Nancy Rundlet and I’d like to share it here. I’m glad to see that at least one of the sessions will cover document generation with RPE.

We are very pleased to announce the DOORS and DOORS Next Generation Enlightenment Series  for April through June 2016.

Each month, the DOORS Next Generation webinars will be held on the 1st Thursday, and DOORS 9.x will be on the 3rd Thursday at  11:00 AM ET (8:00 AM PT).  Details with abstracts and registration links for each of the webinars are in the attached Word Document or you can register by clicking on the registration link below.

The abstracts for the session are provided in the attached document. DOORS Abstracts Q2 2016

Date Webcast series –  Thursday 11:00 ET for approximately 1 hour        DNG on 1st Thursday and DOORS 9.x on 3rd Thursday Speaker Registration Link
3/17/2016 Creating Traceability in DOORS and Beyond – The Various Methods Jim Marsh, IBM Register

4/7/2016 Importing and Exporting with DOORS Next Generation Carlos Ramirez, IBM Register

4/21/2016 An Automated Method for Collecting Metrics Kori Haynes, Crane Aerospace Register

5/5/2016 Exploring Navigation in DOORS Next Generation Ed Gentry, IBM Register

5/19/2016 DOORS 101: An Introduction to DOORS 9.6 Rick Learn, IBM Register

6/2/2016 Rational Publishing Engine (RPE) for Custom Reports Across the Lifecycle (DNG, RQM, and Rhapsody) Don Cunningham, IBM Register

6/16/2016 Customizing DOORS and Web Access to Speed up Reviews and Save Lives Cliff Sadler, Brockwell Technologies (US Army) Register

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.

Continue reading “Traceability with DOORS 9 and RQM”

How to report from multiple data sources selected dynamically

The example uses DOORS 9 modules but it is applicable to any data source RPE supports.

The problem: create a document from multiple DOORS 9 modules.

The static solution: use the same template multiple times in a docspec with a different module each time. This is what is used in most cases and it’s the simplest solution when you have a fixed list of modules you want to report on.

The dynamic solution:

  • create a list of the DOORS 9 modules you want included
  • iterate the list and reconfigure the template data source with the information read from the list

The list can be kept in a DOORS 9 module or in a separate XML file. The list can generated/altered right before you start the document generation.

Continue reading “How to report from multiple data sources selected dynamically”