Blogs about Jazz

Blogs > Jazz Team Blog >

What’s new in Rational DOORS Next Generation 6.0.3

IBM Rational DOORS Next Generation (DNG) 6.0.3 introduces a new dimension to configuration management a simpler way to interact with requirements information and more.


It’s likely you will find information about “components” in a number of our blogs about 6.0.3.  That’s because they impact a number of our tools.

It is now possible to create multiple components in Rational DOORS Next Generation and Rational Quality Manager when their project areas are enabled for configuration management.  Each component has its own streams and baselines.  Instead of working with all the artifacts from the project area in one stream, you can create a component to represent a smaller set of artifacts such as a folder of requirements or a test plan and the associated test cases and test scripts.  These fine-grained component streams and baselines offer more flexibility for parallel development and strategic reuse. The baselines or streams of those components can contribute to an Application Lifecycle Management (ALM) global configuration.

Projects that are enabled for configuration management will, by default, have all information moved into a single component. Then restructure and reorganize your information into multiple components when needed.

Examples for components include:

  • A test team might want to test against a distinct version of the requirements. If you have multiple test teams that test different aspects of the same requirements, then move things in to components allows each team to work independently to each other but in a configuration controlled way.
  • Your requirements are developed and updated on different schedules:
    • User
    • System
    • Subsystem
    • Shared
    • Security / operational
    • Functional / non-functional

You would like to establish a baseline for each type of requirement and their supporting documentation separately and carefully manage updates in the hierarchy. In this case, you can move the individual sets of requirements into different components, and each component can be developed at their own pace and baselined independently.

  • You are engineering a complex system of systems with a hierarchy of sub-systems. Each
    subsystem can be represented by one or more components, and Global Configurations
    provide the hierarchy.
  • You are constructing multiple variants of your final solution. Either branch each component to create specific variants or do your development in superset streams of each component. Make use of feature modeling tools, such as BigLever Gears by BigLever Software, Inc. or purevariants by pure-systems GmbH to realize specific variants.

Requirements Navigation

Requirements Navigation












In this release, it is simpler to filter, search, and generally navigate requirements information Filters have now moved in to a more interactive control above the requirements to allow for simpler interaction and analysis of information without struggling to get to grips with a query. Views are placed in their own area to allow your organizations to more easily pre-define how team members should view requirements. Finally, the overall layout of the display is easier to control in hiding controls if all you require to do is read or write your requirements.

Migration and support of the supply chain

Migration from DOORS to DOORS NG has a new mechanism to improve the value of your data by instilling an artifact type to your previous DOORS data. Rather than relying on data validation techniques to make sure that accurate requirements are being added to DOORS, DOORS NG can now be more fully utilized to ensure that information can only be provided with relevant attribute values for each artifact type. For example, a requirement could have a priority whereas a heading might never need this attribute at all.

On a similar note, IBM is a full contributor to the ReqIF implementers forum, in accordance with the OMG. DOORS NG V6.0.3 makes a number of improvements for working with requirements across a supply chain where organizations use different CLM environments or even different requirements tools. This release introduces improvements with reporting around ReqIF import while making it far simpler to configure ReqIF files based on predefined module “views”.

Deprecation of RRCx

As previously announced, the older diagramming capability within DOORS NG, called “RRCx”, is now deprecated. DOORS Next Generation V6.0 introduced new Diagram Editors to support informal diagramming within requirements sets without the need to install an additional browser. The original graphical editors (RRCx) remained to provide consistency and time to move over to the new technology. The third-party components that were used within RRCx are now deprecated in two of the three major browsers (Firefox and Chrome). So it was not possible to support RRCxs for the 6.0.3 release.

  • Version 6.0.3 extends the new Diagram Editor to support a full UI Wireframe palette and
    associated functionality.
  • RRCx artifact types will be read only. The diagrams will look identical, will all be clickable, printable and reportable.
  • The DOORS NG product team intends to provide a utility to convert an RRCx diagram into the new Diagram Editor format. All of the RRCx format types will be supported. While this conversion will not be pixel perfect, it is expected to preserve every shape, connection, artifact link, and comment in the original RRCx diagram. While plans are subject to change, this conversion utility is expected in the first half of 2017.

Rational DOORS Next Generation is part of the Rational solution for Collaborative Lifecycle Management and the IBM IoT continuous engineering solution. For more details on what’s included in Rational DOORS Next Generation 6.0.3, see New & Noteworthy.

New users can try DOORS Next Generation on the cloud by going to

To download and install DOORS Next Generation, go to


Stay connected with on Facebook and Twitter.  Watch us on YouTube.