Download 6.0.6 Release
June 15, 2018
Try
Buy

IBM Rational DOORS Next Generation

Definition Management Analysis

Rational DOORS Next Generation 6.0.1

Product Release / Trial | December 14, 2015
This is not the most recent version. We recommend Rational DOORS Next Generation 6.0.6 . 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.1 New & Noteworthy

Rational DOORS Next Generation 6.0.1 New & Noteworthy

Rational DOORS Next Generation is an integral part of the Rational solution for Collaborative Lifecycle Management (CLM). For new and noteworthy information about other CLM applications, see these pages:

For a list of changes to the installation and upgrade process, see CLM 6.0.1 Installation and Upgrade Notes.

To activate the configuration management capabilities that were added in CLM 6.0, Rational DOORS Next Generation and Rational Quality Manager require a no-cost activation key. For more information, see Enabling configuration management in CLM 6.0.1 applications.

New in Requirements Management 6.0.1

Enhancements for configuration-enabled projects

New link validity feature

Enabling and disabling link validity

Link validity can be enabled or cleared for a specific project area. You can set the link validity capability on the Manage Project Properties page, in the Configuration Management section. New and migrated projects have the link validity setting cleared by default.

New Link Validity column

A new Link Validity table view column has been added for use in configuration management-enabled projects where link validity has been enabled. This column summarizes the overall link validity state for a resource and displays it using an easily identifiable icon.

Validity status roll-up

A validity status roll-up is now computed and rendered in the new Validity column. The column provides at-a-glance summary information about link validity for all relationships on a given requirement.

Validity status on links

Validity status can now be set on links on an individual basis from within link columns as well as the Links section of individual artifacts.

New link validity controls on links

New controls were added to artifact links for configuration-management-enabled projects in which link validity is enabled. These new controls allow you to assign the validity status (valid or invalid) for individual artifact links. When you view an artifact, the controls are located beside artifact links in the "Links" section of the sidebar and also when link columns are present in the artifact grid.

Information provided on link validity indicators

On individual link validity indicators, you can now see who set the current status and when it was set.

Set link validity with comments

A new menu option is available for setting link validity. You can provide a comment when you set the validity status for a link. The comment is displayed in the hover preview for the link validity status widget.

Validity status icons in the Link Explorer

A new validity status icon is available for the link section. The icon shows the validity status of the links. A new validity status icon is available in the Link Explorer over the link information. The icon shows the validity status of the links. You can also set the validity status to Valid, Invalid, or Unknown by clicking the icon.

Link validity can be set from hovering over the validity status icon

You can set the link validity status directly in the hover preview window when you hover over the validity status icon.

Overall configuration management improvements

Change set workflow

Two new options are now available to allow more control over how and when changes are made to requirements. These options are displayed on the New Details tab of a stream. Configuration management must be enabled in order to see this page. The two new options are To edit this stream, changes must be made in a change set and To deliver to this stream, change sets must be linked to an approved change request or work item. Enabling the first option prevents any edits made directly in the stream and forces users to manually create change sets and make their changes there. Enabling the second option requires that users link change sets to a change request or work item that is in the approved state before the change set can be delivered to its parent stream.

Creation of Requirements Management baselines and streams from the Global Configuration Management application

Rational DOORS Next Generation now implements the OSLC API for creating Rational DOORS Next Generation streams and baselines. The Global Configuration Management application adopted the API, which enables users to bulk create Rational DOORS Next Generation streams and baselines from the Global Configuration Management application without using Rational DOORS Next Generation.

To create a baseline from a global configuration stream, first create a baseline staging stream and then navigate to the staging stream. Right-click the root global configuration node and click Commit Baseline. This action generates a new global configuration baseline, generates a new baseline from each child stream, and adds the new child baseline to the global configuration baseline.

To create a stream from a global configuration baseline, right-click the root global configuration node within a global configuration baseline and click Create Stream. This action generates a new global configuration stream, generates a new stream from each child baseline, and adds the new child stream to the global configuration stream.

Configuration-aware project dashboard widgets

The Recent Changes, Comments, and Requirements View widgets on the project dashboard can now be scoped to a configuration for projects that are enabled for configuration management.

Setting Viewlet Configuration

If the Use current Configuration option is selected, the widget shows results for the configuration that is active in the configuration context banner button.

Current Configuration Viewlet

If the configuration that is active in the configuration context banner button is not valid for a widget's scope, a warning message is displayed. In the screen capture below, the widget is scoped to the "JKE Banking and Securities" project, but the current configuration is a configuration in the "AMR Sample" project. A similar message is displayed if you scope a widget to a global configuration and the widget's specified project is not part of that global configuration.

Viewlet Configuration Warning
Configurations in personal dashboard widgets

On personal dashboards, you can now scope the Recent Changes, Comments, and Requirements View widgets to a configuration for projects that are enabled for configuration management.

Change management constraints for cross-stream delivery

When you deliver from one stream to another, if the target stream has the options enabled to require change sets, and change sets must be linked to approved work items or change requests before delivery, only change sets that meet this criteria are available for delivery. Additionally, the entire chain of dependent change sets must meet this criteria for one to be delivered. For example, if change set "update requirement abc" depends on change set "create requirement abc," both change sets must be linked to an approved work item or change request for "update requirement abc" to be available for delivery.

Ability to deliver and merge change sets that contain restructuring operations

Change sets that contain restructuring operations in a module can now be delivered and merged. Artifact move operations are identified and can be merged into the module structure in the target stream. The merge algorithm attempts to find a suitable place for the moved artifacts in the target stream and the UI highlights the moved artifacts.

Delivering change sets that affect module structure

You can now choose whether or not to include change sets that affect the structure of a module when delivering between streams. You can decide which change sets to include, such as move, add, or remove artifacts, and the module layout is computed according to their selection. The only exception is that you cannot deliver a change set that depends on another change set. For example, you cannot create an artifact and child artifact and then deliver only the child without delivering the parent.

Personal stream improvements

Several improvements were made to make it easier to work with change sets in personal streams. You no longer need to switch between the Rational DOORS Next Generation and Global Configuration Management applications to work with personal streams.

Newly created change sets

When you work in a global configuration, if you create a change set, it is automatically added to your personal stream. The current configuration is updated to reflect this. Also, if your personal stream does not already exist, one is created for you automatically.

Discarded change sets

When you work in a personal stream, if you discard the change set, it is automatically removed from your personal stream. The current configuration is updated to your global configuration.

Delivered change sets

When you work in a personal stream, if you deliver a change set, it is automatically removed from your personal stream. The current configuration is updated to your global configuration.

Changes to module merging

Improved compare and deliver UI when merging modules

The compare and deliver UI has a cleaner design. The compare and deliver screens now expand to the full height of the available space rather than being fixed at 500 pixels.

Compare and Merge view for modules has new change indicators

The Compare and Merge view for modules now contains sidebar annotations so that you can easily locate and navigate to changes.

Updated module merge display for changed artifacts

When an artifact in a module is changed, for example, an attribute value is modified, the row is now marked as having changed in the module merge display.

Ability to commit a merged module structure

Having computed the new module structure, the Requirements Management client can now pass that new structure to the server for use in the module when the user completes the delivery.

Improvements to compare and merge UI

In the compare and merge UI, you can now view all of the attributes, links, and tags for any row in a module regardless of whether that row has been changed.

Jazz Reporting Service

Version-aware reporting with Jazz Reporting Service

Rational DOORS Next Generation now provides a new version 2.0 Jazz Reporting Service. The service exposes configuration management data and version resources in all existing configurations in projects that are enabled for configuration management. You can use this capability to report on Rational DOORS Next Generation artifacts in any stream or baseline, including global configurations. You can also create traceability reports based on links to resources in other CLM applications (Rational Quality Manager and Rational Team Concert).

Note: Server administrators might need to follow certain configuration procedures to enable version-aware reporting in Jazz Reporting Server. See the Reporting topics in the CLM documentation in IBM Knowledge Center.

The following images show the Jazz Reporting Service Report Builder. These example reports contain Rational DOORS Next Generation data from the JKE Banking LPA sample in a global configuration context. The reports were created in Jazz Reporting Service by using the "Lifecycle Query Engine using Configurations" data source.

User story elaboration implemented by work item

Test cases validate requirements

Extracted features
Jazz Reporting Service data access at the project level for Rational DOORS Next Generation data

Jazz Reporting Service can control data access in reports at the project level for Rational DOORS Next Generation data. The Rational DOORS Next Generation artifacts provided to the Lifecycle Query Engine define an access context property, which enables Jazz Reporting Service to validate the reporting user permission against those artifacts.

Improvements to links

Link by attribute

Overview

The Link by Attribute window includes several options:

  • Create links for all IDs in the attribute
  • Add IDs to the attribute for each existing link of the specified type
  • Add both links and IDs that do not have a match
  • Remove both links and IDs that do not have a match

You then choose one of the following options:

  • An attribute that contains the artifact IDs
  • The type of link to use

The following image shows these UI elements in use:

The Link by Attribute dialog box

Attribute type and contents

The attribute must be of type string and each instance can contain one or more numeric references to artifact IDs anywhere in the repository. Thereby, cross-project references are supported. The artifact ID is that which is displayed in the ID attribute for any specific artifact.

Reference types

Using just an artifact ID creates a core link to the specified artifact. Using both a module and artifact ID in dot notation (for example, 33.44) creates a link with module visibility.

Menus

The following image shows the artifacts Link by Attribute menu:

The Link by Attribute artifacts menu

The following image shows the module view Link by Attribute menu:

The Link by Attribute module view menu

Results

The following image shows how link attribute references are transformed into physical links:

The results of a Link by Attribute session

Other considerations
  • A module.artifact reference to an artifact that appears multiple times in the specified module creates a link to each appearance of the artifact.
  • Each attribute should represent a single link type. A Link by Attribute command is required to process changes for each attribute.
  • The direction of the link is determined by the link type. Both incoming and outgoing links are supported. Incoming link types treat the specified attribute ID as the source of the link.
  • Link types are filtered by constraints when launching from the Link by Attribute menu on one or more selected artifacts.
  • Link types are not filtered when launching from the Link by Attribute menu on a module view.

Defining and enforcing link constraints

Creating links when link constraints are defined

When you create element-based links from rich-text and diagram artifacts, the project's specified link constraints are applied. Only those artifacts that are allowed to be a target for the selected link type are available for linking.

Create link filtering

When you create links by dragging and dropping or by copying an artifact and using the Paste as Link command, only the link types that are allowed for all of the selected artifacts are available.

Creating links by dragging and dropping or the Paste as Link operation

When you create links across projects, the link constraints for both projects are applied. If no link constraints are defined for a project, cross-project linking is not restricted. However, if you define link constraints for a project, only those link types that can link to any artifact are available for cross-project linking. Also, only those projects that allow cross-project linking for the constrained link type are available for the target of the link.

In the following image, Link To is available for cross-project linking because the JKE Project link constraints define a rule (Business Goal > Link To > ANY) that allows cross-project linking for that link type.

Cross-project linking allowed

Additionally, the Use Case Project link constraints define a rule (Use Case Diagram > Link From > ANY) that allows cross-project linking and that matches the JKE Project rule so that use case diagrams can be selected when performing cross-project linking between the JKE project and the Use Case project.

Cross-project linking
Link constraints administration

You can now restrict links between artifact types by using link constraints. You configure link constraints in the project properties on the Link Constraints page.

Project Properties: Link Constraints tab
Adding link rules

By default, no link rules are specified and all links are allowed. Adding one or more rules constrains all links according to the specified rules.

Link Constraints: Adding Link Rules

CSV file exporting and importing

You can now both create new requirements and update existing requirements with a CSV import. The import wizard has additional options that you can use for the following operations:

  • Create requirements
  • Update matching requirements and create new requirements for new entries
  • Update matching requirements and ignore new entries
Import requirements

Identification of existing requirements

When you export requirements to a CSV file, an ID column is included. You can use this column to find existing requirements upon import. If you select the option to update requirements, the requirement is updated. You can updated the following properties: name, description, primary text, artifact type, and all user-defined attributes.

Replacement of rich text

When you export requirement text to a CSV file, the rich-text markup is not shown. If the requirement text in the CSV file is changed before the import, the rich-text formatting is replaced. However, if the requirement text is unchanged, the rich text is not updated.

Hierarchy and ordering of requirements in modules

The "parentBinding" column controls the hierarchy in modules upon import. You can now update the hierarchy in a module by changing the values in this column. Also, you can reorder requirements in a module by changed the order in the CSV file. New requirements are placed relative to existing requirement rows in the CSV file.

Removal of requirements from modules

When you export requirements to a CSV file, the file also contains a list of which IDs were exported. If you remove a requirement row from the file, you can now choose to remove the requirement from the module upon import. This option was added to the import wizard, and only applies when requirements are being updated.

Import requirements with delete

Enhancements to views

Scoping views by module type

You can now scope module views by type, so that they are only visible in modules of that type. Also, the tooltip for the view informs you of the type it is scoped by.

Tooltip change for View eraser

Instead of "Load default view," the tooltip for the View eraser now displays "Clear view settings."

Audit History view is enabled for modules

The Audit History view is now enabled for modules. All changes to the structure, attributes, and member artifacts are now visible in the audit history.

Last used view is stored

For project pages, such as artifacts, collections, and modules, and for each module and collection artifact, the last used view is stored in the browser's local storage. As a result, when you select a view in any such page, you can now close the tabs or browser, and then return at a later time to find that the same view settings are saved and applied for each of those contexts. The selected view is stored for each context for 90 days. Loading the context again resets the timer. After the timer runs outs, you simply need to select a view again. This works for all views, including views with unsaved changes.

ReqIF now shows views scoped to a module's type

In addition to showing views scoped to the chosen module, ReqIF now also shows views scoped to that module's type.

ReqIF now only shows public views scoped to everyone

ReqIF views are now limited to public project views and public module views that are available to everyone.

Scoped views get deleted when no longer usable

Whenever a type, module, or collection gets deleted, the server now also deletes any views scoped to it, for cleanup purposes.

The Save Shared View permission is now a team area permission

You can now assign the Save Shared View permission in team areas, in addition to project areas. This permission affects a user's ability to create and edit shared views.

Preferred views

You can now mark any view as a preferred view. Preferred views are shown in bold font, and are candidates for the default view.

Scoping of shared module and collection views by team area roles

You can now scope a shared module or collection view to a team area, plus one or more roles. This capability enables users to filter what is displayed, depending on their current roles in that module or collection.

Improvements to cross-project copying

Cross-project copy wizard

You can copy artifacts between projects by using a wizard. To copy artifacts between projects, the target project must already contain the same artifact types, artifact attributes, and attribute data types, including identical RDF URIs, for the artifacts being copied as the source project. The wizard is initiated from the target project and guides you through selecting artifacts from the source project, starting the copy, and reporting progress. A copy report is displayed when the operation is complete.

Copy artifacts into a selected folder

When you use the Cross Project Copy wizard to copy artifacts from a source project into a target project, you can copy the artifacts into a target folder.

Completion status for copying artifacts

The Cross Project Copy wizard displays progress feedback and completion information when performing a cross-project copy. The progress status is shown in the form of a progress bar. When a copy operation is complete, results of the operation are displayed to indicate whether or not the copy was successful. If an artifact or parts of an artifact are not copied, the cause is displayed.

Improved resilience to data type mismatches

The cross-project copy capability was strengthened to be more resilient to data type mismatches between the source and target project areas. When attribute mismatches occur (attribute definition or attribute data type), you are can choose to remove the affected attribute values from the copy. When artifact type mismatches occur, the copy is stopped and all changes are rolled back.

Enhancements to filters

Filtering on a user-based attribute now supports "Current User"

When you filter on a user-based attribute, you can now specify Current User, which adds the current user to any other users that you select in the filter. The current user is available regardless of whether the operator selected is is any of or is not any of. You can specify a current user-based filter to enable creating a shared view such as "My Requirements," which, when invoked, enables team members to see user-specific results.

Filters involving custom attributes now support "is unassigned"

You can now specify is unassigned as the operator for filters that have custom attributes. The "is unassigned" filter only includes artifacts that do not yet have a value for the specified attribute, and the artifact types for these matched artifacts are restricted to those artifact types that include the specified attribute.

New "is" filter for string-based attributes

For string-based attributes, you can now filter by the "is" condition. Previously, you could only filter by "contains," "does not contain," "starts with," and "ends with."

New support for adding an artifact ID filter in "More attributes"

Past releases allowed for involving an Artifact ID filter in the the Linked artifacts sidebar filter section. You can now specify multiple artifact IDs in the filter. You can also drag and drop artifacts into the input field to add their IDs.

More importantly, you can now involve an Artifact ID filter in the More attributes sidebar filter section. You can either type in the artifact IDs, separated with spaces or commas, or you can Drag and Drop artifacts to have their IDs added.

More attributes now allows for an Artifact ID filter

For collections and modules, selecting the "Artifact format" filter results in fewer entries

If you are in a collection and you select Filter by Attribute > More attributes > Artifact format, Collection is no longer displayed in the resulting the check box listing. Similarly, if you are in a module and you select Filter by Attribute > More attributes > Artifact format, Module or Collection is no longer displayed in the resulting check box listing.

The artifact picker window also contains similar changes; for example, if you are in a module and you are trying to add an existing artifact, the Filter by Attribute > More attributes > Artifact format filter no longer displays either Module or Collection its check box listing.

Rational DOORS to Rational DOORS Next Generation migration

Migrate OLE objects in any text attributes

You can now migrate OLE objects from Rational DOORS that are in any text attributes. Previously, only OLE objects embedded within object text were migrated, such that they were visible in the migrated artifacts. 

When you import a Rational DOORS migration package that contains an OLE object, these artifacts are created:

  • An artifact that contains the OLE object itself.
  • An image of the OLE object at the time of export. This might be either a visual representation of the object content, or an icon.

If the OLE object was not embedded in object text, the migrated text value indicates where these artifacts can be found. The following example shows a text value of a migrated Rational DOORS object, which contained an embedded OLE object:

Results are shown in this chart: OLE object

Note: Migration from Rational DOORS is available in Rational DOORS 9.6.1.3.

Tracking the progress of migration and ReqIF imports

The Rational DOORS Next Generation server now outputs additional diagnostic information during ReqIF and Migration imports. The additional information enables performance analysis of imports.

Performance improvement in tables with many embedded artifacts

The artifact viewer and editor performance was greatly improved for when artifacts that contain many embedded artifacts are opened. Typically, these artifacts are created when migrating from Rational DOORS.

Additional improvements to migration

  • Regular internal links are created when the missing endpoint object is finally migrated into RDNG. 
  • OSLC link fragments, which had previously been created when one endpoint of a link was migrated, are removed when the missing endpoint object is finally migrated into RDNG.
  • A new option is available via the artifact import menu option. The new option allows you to initiate migrations using DOORS9 .migiz migration packages. Apart from the initial, separate migration radio button, the remaining wizard pages are identical to the existing ReqIf import wizard pages.
  • Migrations from DOORS9 to RDNG also migrate DOORS table information in migration packages and convert them into an appropriate xhtml representation in the RDNG web client. Table migrations are only available via the migration import option and are not available via standard ReqIf imports.

Usability and general UI improvements

Paged audit history

Audit history for a module is now paginated in order to provide faster service response and better user experience.

Settings preserved in the New Artifact window

Values in the new artifact window are now set by default based on the values that were last used.

  • Artifact type: The last used type is used unless the value is specified when opening the window.
  • Artifact format: The default format is used based on the artifact type.
  • Template: The last used template is preserved based on the selected type and format combination.
  • Folder: The folder is preserved based on the context of the new artifact being created unless specified. Example: Artifact, Module, Collection, Upload File, and Image.
  • Open Artifact check box: This is preserved across browser sessions of the same browser.

Comments column is now widely available

In previous releases, you could only add a Comments column when a particular module had been opened. You can now add the Comments column regardless of whether you are viewing the Artifacts, Collections, or Modules pages, or whether you have opened a particular collection.

You can now add the Comments column to the Artifacts page

New context menus

The user interface was enhanced with several context menus, which you right-click to activate (or press Shift+F10). The context menus were added to these interface locations:

  • All grid views for artifacts, collections, and modules
  • Views
  • Tags filter
  • Folder trees

Suspect link traceability is only enabled for project areas that support suspect links

Suspect link traceability and suspicion profiles are only enabled for project areas that support suspect links. In addition, the suspect link controls are displayed only if suspect links are present. The suspect link functionality is not available in project areas that are enabled for configuration management.

Link selection preserved

The settings in the link selection dialog box are now preserved between instantiations. The values remain selected when the link dialog box is closed, and are refreshed with the same values when it is opened again. In most cases, this prevents the need to reselect values.

New support for displaying a Team Ownership column

The grid area's Configure Page Settings drop-down menu now enables you to select a Team Ownership column. When this column is shown, the full team ownership hierarchy for each artifact is displayed. If an artifact's team ownership is more than one level deep, hierarchy is displayed by using '>' separators; for example, "Team1 > Team1A." If an artifact has not yet been assigned to a team area, the project name is displayed. Note that you cannot currently sort on this column, group by this column, or involve Team Ownership as a filter.

The new Team Ownership column

Attributes of type DateTime and Date now support relative time values

You can now use relative time values when you specify "after (including)" or "before (including)" for an attribute of the DateTime or Date type. For the DateTime attribute, you can now specify a value of either "yesterday", "today" or a duration that represents a specific number of hours, days, months, or years. Similarly, for the Date attribute, you can now specify a value of either "yesterday", "today" or a duration that represents a specific number of days, months, or years. The DateTime and Date attributes still support an absolute-based value (a date and time for DateTime-based attributes, and a date for Date-based attributes).

Relative Time Values

Updated link display in artifact grids

The link text displayed in artifact grids, for example, artifacts, collection, and modules pages, is updated so that it can be optionally displayed as one truncated line. For newly added columns, the link display text is truncated by default. The options Trim words to fit and Wrap words to show all are now displayed in the Format Link Display Column window.

Persistence of recently viewed artifacts in drop-down menus

In previous milestone releases, the drop-down menus provided a list of recently viewed artifacts, collections, and modules. Now, the persistence of the recently viewed artifacts for each category is improved. The list of the ten most recently viewed modules, collections, and artifacts is stored on the server and will be restored for each browser that a given user can access. The lists are stored by user and by project, similar to how they were in previous releases, except instead of losing this information each time you navigate to a different site, it now persists indefinitely.

Certain selection lists have been improved

In certain scenarios, the check box listing for the Artifact format filter is reduced; the window used for creating a new collection or module now shows with an initially reduced Artifact type listing; the window used for adding new columns now allows you to select Preferred Artifact Types when you open it from within a module.

The Create a New Collection or Module window now defaults to showing only certain artifact types

When you use Collections > Create Collection or Modules > Create Module you are now shown only artifact types that match the associated format; for example, for a Module only artifact types whose default format is Module are shown. When selected, a new More menu item in the Artifact type drop-down menu enables you to display the complete list of artifact types.

For modules, the Change Column Display Settings window now allows you to select Preferred Artifact Types

When you configure the columns to display within a module, the Change Columns Display Settings window now shows a new third menu item, Preferred Artifact Types, within the Choose artifact types or links drop-down button. When selected, the drop-down button is labeled Preferred Artifact Types and the listing below it is filtered to only show those attributes that are associated with the underlying module's preferred artifact types.

Majority of unlabeled buttons were moved to drop-down menus

Buttons without a label in the header of many UI locations were moved to drop-down menus in their respective location to provide a textual label for the user. The locations include:

  • All grid views, such as artifacts, collections, and modules
  • Artifact pages, such as the Text Editor and Diagram Editor
  • Artifact history pages

The Refresh and Lock buttons remain in their current location.

Ability to remove pencil menu from grid and other areas

The ability to remove the pencil or context menu is now available in multiple locations throughout the UI:

  • All grid views, such as artifacts, collections, and modules
  • Views sidebar
  • Filter by Tags sidebar
  • Folder trees

To remove the pencil menu throughout the UI, on the top bar, click the User Profile menu, and then click My User Preferences. Next, select the Hide pencil menus check box. Click Close to leave the User Preferences menu. To restore pencil menus, clear the Hide pencil menus check box.

"Tip of the week" dashboard widget is now translated

The "Tip of the week" dashboard widget that provides helpful tips for how to use the product is now available in all supported languages.

Miscellaneous

Project template changes

Several changes were made to the project creation page. Pre-existing templates were renamed to be simpler and more concise. The following list and figure show some of the changes:

  • A new SAFe template is included for use with the Scaled Agile Framework.
  • Templates that contain sample artifacts have a title that ends with the word sample.
  • Templates that do not contain artifacts end in template.
  • Templates and samples that are similar, meaning the template is used for a similar development process or purpose, are grouped together.

The following table shows the relationship of the templates from before the 6.0.1 release to the new 6.0.1 templates:

Before 6.0.1: Title and description 6.0.1: Title and description
(SAMPLE) JKE Business Recovery Matters (A sample agile project that contains user stories and requirements for a fictitious company.) Agile Requirements Sample (A sample agile project that contains user stories and requirements for a fictitious company.)
(SAMPLE) JKE Enterprise (A sample enterprise project that contains enterprise requirements, terms, and so on, for a fictitious company.) Traditional Requirements Sample (A sample enterprise project that contains enterprise requirements, terms, and so on, for a fictitious company.)
(SAMPLE) JKE Private Banking and Securities (A sample use case project that contains use cases, diagrams and requirements for a fictitious company.) Use Case Requirements Sample (A sample use case project that contains use cases, diagrams and requirements for a fictitious company.)
Agile Requirements Template (This template helps you get started with agile requirements at scale. ) Same as previous
Automated Meter Reader (Sample) (A sample project that contains requirements for the Automated Meter Reader. ) Systems Requirement Sample (A sample project that contains requirements for the Automated Meter Reader. )
JKE Banking (A sample project that contains requirements for a fictitious company.) JKE Banking Sample (A sample project that contains requirements for a fictitious company.)
Requirements Template for Testers Same as previous
Systems Template (sample) (A template that contains the basic structure for a systems engineering project.) Systems Requirement Template (A template that contains the basic structure for a systems engineering project.)
Traditional Requirements Template (This template helps you get started with traditional requirements management.) Same as previous
Use Case Requirements Template (This template helps you get started with use-case driven requirements management.) Same as previous
NA SAFe Agile Template (This template helps you get started with agile requirements at scale. Used as part of the Scaled Agile Framework.)

The following image shows the Project Creation page with the new titles and descriptions.

Project Creation Page

New advanced server property to enable or prevent graphical artifact creation

A new property is available on the Advanced Server Properties page under the "RM Client Component" section to enable the creation of plug-in-based graphical artifacts. When the value is set to false, graphical artifact formats cannot be created.

Artifact formats:

  • User interface part
  • User interface sketch
  • Screen flow
  • Storyboard
  • Business process diagram
  • Simple flow diagram
  • Use case diagram

Any artifacts with a default graphical artifact format are converted to the diagram format. By default, this value is set to false and must be enabled to create graphical artifacts. You can still view, edit, and perform other functions on the artifacts that have already been created.

Rational Reporting for Document Generation version 2.0.1 adopted

Document-style reports are enhanced as result of the adoption of Rational Reporting for Document Generation version 2.0.1.

New in previous versions of Rational DOORS Next Generation

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