Download 6.0.6.1 Release
Try

IBM Rational DOORS Next Generation

Definition · Management · Analysis

Rational DOORS Next Generation with Configuration Management 5.0 beta 1

Early Access Milestone | June 2, 2014
This is not the recommended 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 with Configuration Management 5.0 beta 1 Release Notes

Rational DOORS Next Generation with Configuration Management 5.0 beta 1 Release Notes

This release of Rational DOORS Next Generation is a beta release that provides configuration management capabilities for requirement artifacts.

Known problems and workarounds

  • Suspect link and Rational Reporting for Development Intelligence capabilities work only in the context of a default configuration. An administrator can change the default configuration for a project on the Project Properties page. For more information, see work items 87635 and 76528.
  • Graphical artifacts, audit history, and formal reviews are not supported in this beta. For more information, see work items 75510, 72165, and 79218.
  • The revision history shows only the history for the main artifact (primary content and attributes). The revision history does not show the matching link, comment, and tag history. For more information, see work item 72165.
  • Module baselines are not supported in this beta. Instead, use the new snapshot capability.
  • The ability to sort by suspicion column is disabled. For more information, see work item 87635.
  • After you create a child configuration, if you create a module template in its parent configuration and then create a module in the child configuration based on the module template, the new module will not contain the artifacts from the module template. For more information, see work item 74382.
  • When you import a ReqIF file, even if only a few requirements were updated by the import, the comparison wizard marks all of the requirements as updated. For more information, see work item 87674.
  • If merge conflicts exist between your workspace and its flow target, in order to deliver your change sets you must first accept all of the change sets from the parent and resolve the merge conflicts.

    After you accept the change sets and resolve the conflicts, when you try to deliver your changes, you might still see merge conflicts that you just resolved. This issue is a known problem.

    In most cases, the system will identify and pre-select the correct change sets that you need to deliver, and you can safely click Next to proceed.