Download 6.0.6.1 Release
Try

IBM Rational DOORS Next Generation

Definition · Management · Analysis

Rational DOORS Next Generation 6.0.2

Product Release / Trial | April 25, 2016
This is not the most recent version. We recommend Rational DOORS Next Generation 6.0.6.1 . This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

Rational DOORS Next Generation 6.0.2 New & Noteworthy

Rational DOORS Next Generation 6.0.2 New & Noteworthy Summary

Rational DOORS Next Generation is an integral part of the Rational solution for Collaborative Lifecycle Management (CLM).

For a complete list of new and noteworthy items in this release, see the New & Noteworthy Details.

For a summary of items in this release, see the following highlights.

Assign workflows to specify and automate process for requirements

You can now assign a workflow to an artifact type on the Artifact Types tab of the Manage Project Properties page. Artifacts of that type can transition through the different states of the workflow. When you change the state of an artifact, only the possible and permissible actions for that state are displayed. After you assign a workflow to an artifact type, you can view and edit the workflow state of artifacts of that type as you would any other attribute. You can filter artifacts by workflow state or delete a workflow if it is not assigned to any of the artifact types in any of the configurations in a project.

By setting permissions on the workflow states, you can control which user roles can modify artifacts and attributes of those artifacts for each state of the workflow. For example, you can configure permissions so that, in the Approved state, only users with the JazzAdmin role can modify any attribute. Because you can assign a workflow to artifact types, when you compare or deliver changes from one configuration to another, you can compare or deliver that change just like any other attribute change on that artifact type.

When you create a project template by choosing the option to include artifact types and attributes, the workflow definitions must be added to the active template when you create a new project area under a template with those definitions. When you create a new project area, you can select the project template that you created before, so the new project area contains the workflow definitions that you added to that template. As result, you can see in the new project area that the workflows you included in the template are now used.

Export requirements in additional spreadsheet formats

In addition to CSV files, you can now generate XLS or XLSX files when you export requirements. After you select the Export menu option, a new window opens in which you can specify the file format. Both CSV and spreadsheet export formats now show special markup for links and embedded artifacts. You can use this markup to retain or create links and embedded artifacts upon import. For example, OSLC links are included in exported CSV and Mircosoft Excel files. OSLC links are also created when you import both of these file types.

Specify new options to ease compare and merge operations

This release includes several improvements for compare and merge operations, including the following ones:

  • Select a policy to resolve conflicts in the Merge Delivery wizard: When you deliver a change set by using the delivery wizard, you can select a delivery policy under the Express delivery section and have the server perform the delivery and resolve any conflicts according to that policy. The following conflict resolution options are available: Notify me to manually resolve conflicts, Always overwrite with source, Resolve according to defined policy.

  • Select attributes in the Merge Delivery wizard: When you deliver a change set by using the delivery wizard, if you select Express delivery and the Resolve according to defined policy option, an Attribute selection window opens. You use this window to select from a list of source attributes. In this policy, the selected dominant source attributes are used to overwrite any corresponding value in the merged target when a conflict occurs during the delivery.

  • Express delivery and the Delivery API: When you deliver a change set, any personal streams that have a contribution from that change set are updated. The update removes each contribution of that change set.

Increase security by permanently removing sensitive data from a repository

A new tab, Delete from Repository, was added to the Project Properties page for Jazz administrator users. The Delete from Repository page contains a tool that you can use to permanently delete resources from the repository based on versioned resource URLs, as opposed to archiving them. This tool helps you identify and remove resources that might contain sensitive information, even if they are already archived.

Migrate Rational DOORS 9 data with improved matching for identifiers

Artifact identifiers are now included in ReqIF export operations. The identifiers are imported as "ForeignID" by applications that follow the ProSTEP ReqIF Implementation Guide, or as "ReqIF.ForeignID" for applications that do not.

When you import a migration file from Rational DOORS 9, if the identifier does not already exist in the project, artifact types and link types are determined equal, or otherwise, according to their properties, such as default format and attribute definitions. If the identifier already exists in the project, matching is based on the identifier. Data types and attribute definitions are determined equal, or otherwise, according to the data type or attribute definition's properties (for example, name, bounds, and default value). Migration matching for data types and attribute definitions no longer occurs based on identifier or RDF URI.

New in previous versions of Rational DOORS Next Generation

For details about new features and functionality in previous releases, see these pages:

New in other CLM applications

For new and noteworthy information about other CLM applications, see these pages: