Download 6.0.4 Release
June 12, 2017
Try
Buy

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.4 . 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 Details

For a summary of new and noteworthy items in this release, see the New & Noteworthy Summary.

For a complete list of items in this release, see the following details.

Artifact workflow

Artifact workflow editor

A new workflow editor is available that you can use to create and modify custom workflows for artifacts. A workflow consists of a set of states, a set of actions, and a state transition model. After a workflow is associated with an artifact type, artifacts of that type can move through the various states as part of its lifecycle. For consistency, the workflow editor is similar to the Rational Team Concert and Rational Quality Manager workflow editor.

Sample default workflow

A sample default workflow is available for you to view, use, or customize. This workflow is available for new projects in new installations of Rational DOORS Next Generation. It is not currently available if you upgrade.

Create a new workflow

You can create a new workflow by clicking Add. In the Add Workflow window, you enter a unique workflow ID and name.

Add Workflow Dialog


Add workflow states

After you specify a workflow name and ID, you can add the workflow states by clicking Add. The workflow state information is displayed in the States section.

Workflow States


Add workflow actions

After the states are defined, you can create the workflow actions by clicking Add. Workflow actions are used to transition to a particular state. Note that when you define the action, you only specify the resulting target state; you do not specify the source state (which is where state transitions apply). You can also define multiple actions that result in the same target state.

Workflow Actions


State transition model

State transitions provide the link between the source and target states. You can use the state transition model to specify which action can be applied to a particular state to transition it to a different state.

State Transition Model


Workflow permissions

By setting permissions on workflow actions, you can control which user roles can move or transition an artifact to a particular state.

Keeping actions and transitions separate provides flexibility for how you define permissions. For example, you can have a permission control each way to get into a particular state by using a single action for every transition to that state. Then, you only have to define the permission once. You can also have different permissions for different ways to get to a given state by using different actions for the different transitions into that state.

Workflow Permissions


Assigning workflows to artifacts

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 now 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.

Workflow support for process automation of requirements

View and edit an artifact's workflow state

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.

Filter by workflow state

You can now filter artifacts by workflow state.

Filter By Workflow State


Delete a workflow

You can now delete a workflow if it is not assigned to any of the artifact types in any of the configurations in a project.

Workflow state permissions

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.

Examples:

In the Approved state, only users with the JazzAdmin role can modify any attribute. In the New state, all users can modify any attribute.

Workflow State Permissions


Compare or deliver artifact type workflows

Because you can assign 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.

Compare Workflow


Project template creation and workflow definitions

When you create a project template by choosing the option to include Artifact Types and Attributes, the workflow definitions must be added to the template being used when you create a new project area under a template with those definitions.

Artifacts


Which workflow definitions are created: The workflows registered in the current project before creating the template are created. For example, if the current project in the system has these following two workflows:

Artifacts


Why workflow definitions are useful: 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.

Create a new project area to use the created template with workflow definitions:

Artifacts


Then, select the template:

Artifacts


As result, you can see in the new project area that the workflows you included in the template are now used.

Improvements to round-trip import and export support for spreadsheet file formats

Support for XLS and XLSX file 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:

XLS and XLSX Export


You can also use the import wizard to choose these file formats when you create or update requirements:

Import File Format


Export and import round-trip operations support links and embedded artifacts

Both CSV and spreadsheet export formats now show special markup for links and embedded artifacts. This markup can be used to retain or create links and embedded artifacts upon import.

You can export links by including a link column in the view. Links, images, or embedded artifacts can also be present in the primary text of the requirement, which can be shown in the view and subsequently exported.

In the exported file, links within link columns are represented as follows:
{LINK id=3129 uri=https://server/rm/resources/_abaf26f172a149b2aaf8f22933be1661}

Links within the primary text column are represented as follows:
"The text contains a link:{LINK id=3129 title=""3129: AMR Information Architecture"" uri=https://server/rm/resources/_abaf26f172a149b2aaf8f22933be1661}."

If you add a new link to an exported link column, a new link is created during the import process, using the type specified by the column name. If the new link is added to the primary text column before the import, a new link is not created.

In CSV files, the images and embedded artifacts are represented as follows:
{EMBEDDED id=3498 title=""new requirement"" uri=https://server/rm/resources/_klHmkbljEeWqUL0WZ--HjQ}
{IMAGE id=3496 title=""watson-analytics-logo.png"" uri=https://server/rm/wrappedResources/_dyVrMLljEeWqUL0WZ--HjQ

Additionally, in spreadsheet files, the images are included in the file, and can be seen as a comment on the spreadsheet cell:

Image In Spreadsheet Cell


When adding new references to images or embedded artifacts on import, only the identifier of the resource is needed. For example, to embed a reference to a requirement in the primary text of a requirement, the following markup could be used: {EMBEDDED id=123}

OSLC links are included in exported CSV files

When you export artifacts that contain OSLC links (Validated By, Implemented By, Affected By, and Tracked By) to another application's resources, the CSV file displays each of them with this format: {LINK id=24 uri=https://... }. The value of the link URI depends on the current view that you are working in.

The following line is an example of how the link must be shown in the CSV file:
{LINK id=3129 uri=https://rm602.com:9443/qm/oslc_qm/contexts/_Tj9i0LiLEeWWFuQ1aZ9WjA/resources/com.ibm.rqm.planning.VersionedTestCase/_t451QLiWEeWk1cqv1JwgRA}

For example, consider an artifact that is linked to a Quality Management test case through a Validated By link. If you initiate a CSV export operation, the exported file shows the following results:

Import Export Artifacts


id,Name,Link:Validated By,Link:Implemented By,Link:Affected By,Link:Tracked By,Artifact Type
1261,RM Artifact,{LINK id=1 uri=https://rm602.com:9443/qm/oslc_qm/contexts/_Tj9i0LiLEeWWFuQ1aZ9WjA/resources/com.ibm.rqm.planning.VersionedTestCase/_t451QLiWEeWk1cqv1JwgRA},"","","",Feature
METADATA
Exported Artifact IDs=1261
Export Project Area=https://rm602.com:9444/rdm/process/project-areas/_PKm88LiLEeWwYpIdQ6WZhQ
Export Configuration=https://rm602.com:9443/gc/configuration/2

As the example shows, in the Link:Validated By information, the link is displayed in the previously specified format.

OSLC links are included in exported Microsoft Excel files

When you export artifacts that contain OSLC links (Validated By, Implemented By, Affected By, and Tracked By) to resources in another application, the Microsoft Excel file displays each of them in this format: {LINK id=24 uri=https://... }. The value of the link URI depends on the current view that you are working in.

The following line is an example of how the link must be shown in the Microsoft Excel file:
{LINK id=3129 uri=https://rm602.com:9443/qm/oslc_qm/contexts/_Tj9i0LiLEeWWFuQ1aZ9WjA/resources/com.ibm.rqm.planning.VersionedTestCase/_t451QLiWEeWk1cqv1JwgRA}

For example, consider an artifact that is linked to a Quality Management test case throught a Validated By link. If you initiate an Excel export operation, the exported file shows the following results:

Import Export Artifacts


Import Export OSLC Exported File


As the example shows, in the Link:Validated By column, the link is displayed in the previously specified format.

OSLC links are created when you import Microsoft Excel files

When you import artifacts that contain OSLC links (as specified in the table below) to artifacts in another application, those links are created only if the current project contains an OSLC association to another application.

For example, if a Microsoft Excel file contains a Validated by link, the project must have an OSLC association to a Quality Management application that matches the specified link.

Application OSLC link types
Requirements Management References, Referenced by
Quality Management Validated by
Change and Configuration Management Implemented by, Affected by, Tracked by
Design Management Satisfied by architecture element, Refined by architecture element, Traced by architecture element

The following line is an example of how the link must appear in the Excel file to import:
{LINK id=3129 uri=https://rm602.com:9443/qm/oslc_qm/contexts/_Tj9i0LiLEeWWFuQ1aZ9WjA/resources/com.ibm.rqm.planning.VersionedTestCase/_t451QLiWEeWk1cqv1JwgRA}

Consider that you have the following Excel file:

Artifacts


Import the file as a new entry:

Artifacts


The result is a new artifact with OSLC links.

Artifacts


Note: As a prerequisite, the project must have OSLC associations.

OSLC links are created when you import CSV files

When you import artifacts that contain OSLC links (as specified in the table below) to artifacts in another application, those links are created only if the current project contains an OSLC association to another application.

For example, if a CSV file contains a Validated by link, the project must have a OSLC association to a Quality Management application that matches the specified link to the CSV file.

Application OSLC Link Types
Requirement Managements References, Referenced by
Quality Management Validated by
Change and Configuration Management Implemented by, Affected by, Tracked by
Design Management Satisfied by architecture element, Refined by architecture element, Traced by architecture element

The following line is an example of how the link must appear in the CSV file to be import:
{LINK id=3129 uri=https://rm602.com:9443/qm/oslc_qm/contexts/_Tj9i0LiLEeWWFuQ1aZ9WjA/resources/com.ibm.rqm.planning.VersionedTestCase/_t451QLiWEeWk1cqv1JwgRA}

Consider that you have the following CSV structure:

id,Name,Link:Validated By,Link:Implemented By,Link:Affected By,Link:Tracked By,Artifact Type
"",RM Artifact,{LINK id=1 uri=https://rm602.com:9443/qm/oslc_qm/contexts/_Tj9i0LiLEeWWFuQ1aZ9WjA/resources/com.ibm.rqm.planning.VersionedTestCase/_t451QLiWEeWk1cqv1JwgRA},"","","",Feature

METADATA
Exported Artifact IDs=1261
Export Project Area=https://rm602.com:9444/rdm/process/project-areas/_PKm88LiLEeWwYpIdQ6WZhQ
Export Configuration=https://rm602.com:9443/gc/configuration/2

Import the CSV file as a new entry:

Artifacts


The result is a new artifact with OSLC links.

Artifacts


Note: As a prerequisite, the project must have OSLC associations.

Enhancements to compare and merge

Attribute selection in the Merge Delivery wizard

When you deliver a change set by using the delivery wizard, if you select Express Delivery and the option Resolve according to defined policy, you are presented with an Attribute selection window. 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.

Delivery policy selection

Delivery policy selection


Dominant source attribute picker window

Artifacts


Selecting 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 in the wizard and have the server perform the delivery and resolve any conflicts according to that policy.

In the initial step of the delivery wizard, which confirms the source and target configurations, you can select the delivery policy under the Express delivery section. The server automatically resolves any conflicts according to the policy that is selected.

Delivery policy selection


Notify me to manually resolve conflicts
  • If you select this option, all non-conflicting changes are delivered.
  • Any module structure conflicts are automatically resolved.
  • Any remaining conflicts cause the delivery to fail and you are notified of conflicts that require manual resolution.
Always overwrite with source
  • If you select this option, all non-conflicting changes are delivered.
  • Any module structure conflicts are automatically resolved.
  • Any remaining conflicts are resolved to where the version in the source is delivered.
Resolve according to defined policy
  • If you select this option, all non-conflicting changes are delivered.
  • Any module structure conflicts are automatically resolved.
  • When this option is selected, a source attribute selection dialog box opens. The selected attributes are used to resolve any remaining conflicts, where the selected source attributes overwrite the corresponding value in the merged target.

Dominant source attribute picker


Express delivery feature and 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.

Improvements to rich text editor toolbar

New menu buttons

The Rich Text Editor Toolbar is enhanced to include menu buttons for some of the editing operations.

Toolbar


  1. The Edit menu button contains Cut, Copy, and Paste commands, along with the Select All command.

    Edit menu


  2. The Align menu button contains the text alignment operations. The active alignment is displayed in bold font on the drop-down menu.

    Align menu


  3. The Insert menu button contains the insert operations, along with the Add Link, Save Selection as New Artifact, and Create Term operations. The Remove Link operation is no longer on the toolbar, but can be invoked from the editor context menu.

    Insert menu


Editing rich text in the module editor, the collection editor, and on the artifacts page

When you edit Primary Text or Contents attribute fields in the module editor, the collection editor, or on the Artifacts page, the rich text toolbar is displayed at the top of the grid in place of the header row.

Toolbar


If the toolbar cannot be fully displayed on one line, a button for showing more or less of the toolbar is shown.

Expanded Toolbar


When focus moves out of the rich text cell, the toolbar disappears.

Edit menu

These toolbar items were moved to the Edit menu:

  • Undo
  • Redo
  • Find and Replace
  • Remove Format

Edit Menu


Keyboard accessibility

When focus is in the editor cell, if you press Alt+F10, the focus moves to the first element on the toolbar. When the toolbar has focus, the following keystrokes can be used to navigate within the toolbar:

  • Tab and Shift+Tab move focus between the toolbar groups.
  • Left Arrow and Right Arrow move focus between the items in a toolbar group.
  • Esc places focus back into the editor cell.

Improvements to module editing

Most grid cells edited via pop-up editors

In past releases, when a grid row was placed in edit mode, it would result in inline cell editors appearing for all of the editable cells within the row. This approach was problematic for editable cells in narrow columns. The Requirements Management application now uses pop-up editors for all fields except for the following: Contents, Primary Text, Name, Description, and Alternative Spellings. The vertical spaced provided by using a pop-up editor makes the cell editors intuitive and approachable. The following image shows an example of one of these editors:

[An example popup editor (for Boolean)]


Different keys for navigation when editing rows

In past releases, when you placed a grid row in edit mode, you pressed Tab and Shift+Tab to move forward and backward between all the editable fields. In addition, tabbing past the last editable cell (or before the first editable cell) would commit the changes and put the row back into view mode.

The introduction of pop-up editors has changed this tab-based approach to navigation. When a row is in edit mode, you now press the Right Arrow and Left Arrow keys to move between the cells. When focus is on an editable cell, you can press Enter to change the cell value. If the cell is based on a pop-up editor, such as Priority, a pop-up editor is displayed and focus is placed within the pop-up editor. If the cell is based on an inline editor, such as Name or Contents, the focus is moved into the inline editor within the cell. To get out of an inline editor, press Tab to move the focus back to the enveloping cell. From there, you can press the Right Arrow and Left Arrow keys to move focus to adjacent cell editors. To save your changes, move focus somewhere outside of the row or, as in previous releases, press Ctrl+S.

New filterable grid widget for user and enumeration attributes

For user and enumeration attributes, there is a new widget with a filter field that is used for editing in the grid. For single value attributes, labels are used for selection. For multiple value attributes, check boxes are used. The new widget is accessible to keyboard navigation.

Tooltip associated with cell edit buttons includes the attribute name

In previous releases, hovering over the edit button for a particular grid cell resulted in a tooltip with the text Edit. This tooltip is now changed so that it also mentions the attribute, for example, Edit Priority.

Automatic pop-up help only appears for the contents cell

In previous releases, the automatic pop-up help would appear the first three times you put a module row into edit mode. Now, this automatic pop-up help is only shown for the Contents cell, whereas previously it was shown for every editable cell within the row. This change was required to enable the pop-up editors to be displayed.

DateTime attribute pop-up editor

You can now edit the DateTime attribute by using a pop-up editor with a date text input and an inline calendar, and a time text input with a drop-down time selector. The drop-down time selector is a list of times in the 24-hour system in 15-minute increments.

DateTimeAttributePopupEditor


Date attribute pop-up editor

You can edit the Date attribute by using an attribute pop-up editor with a text input and an inline calendar. When you select a date in the inline calendar, the text input updates accordingly. When you enter a date into the text input, the calendar is updated when focus is placed away from the text input.

DateAttributePopupEditor


Time attribute pop-up editor

You can edit the Time attribute by uisng an attribute pop-up editor with a text input and an inline time selector. The text input allows you to enter time in HH:mm:ss format and the time selector is a list of times in the 24-hour system in 15-minute increments.

TimeAttributePopupEditor

Permanently remove data from repository

Delete from Repository tab

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 enables you to permanently delete (purge) resources from the repository based on versioned resource URLs, as opposed to archiving them.

Export data dump tool

A export tool is available for Jazz administrators to transcribe (dump) resources from a component area to the server file system. This tool helps you identify resources that might contain sensitive information, even if they have already been archived. After you set the "data.purge.enabled" advanced server property, the tool is available from the Delete from Repository tab on the Project Properties page.

Improved Rational DOORS 9 migration

With ReqIF export, include artifact 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.

Following the recommendations in the ProSTEP ReqIF Implementation Guide, the values are exported by using a special "ReqIF.ForeignID" attribute. Applications that follow this guide import these values as "ForeignID", and do not return them in round-trip export operations. Applications that follow the guide include IBM DOORS and IBM DOORS Next Generation.

Applications that do not follow the implementation guide import the values as "ReqIF.ForeignID", and might include them in export operations.

Migration import from Rational DOORS 9: Artifact type and link type equality matching

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 now determined equal, or otherwise, according to their properties, such as default format and attribute definitions. If the identifier already exists in the project, matching continues to be based on the identifier.

When you import a migration file from Rational DOORS 9, data types and attribute definitions are now 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.

Miscellaneous improvements

Support for cross-project links with user-defined link types

User-defined links that have a RDF URI set should behave as system links. The following behavior is supported:

  • Create cross-project links:
    • Artifact grid
    • Links sidebar
    • Drag and drop
  • Display cross-project links in both projects:
    • Artifacts grid
    • Links sidebar
    • Links explorer
  • Edit/remove cross-project links from both projects:
    • Artifacts grid
    • Links sidebar
    • Links explorer

Insert symbol plug-in

A plug-in was added to the editor that enables you to insert special characters. The plug-in is available in the rich-text artifact editor, the comment editor, and the floating module editor. The following image shows the button to open the window and the window.

Toolbar Button

Insert Symbol Dialog


Saved views with lifecycle filters

In lifecycle projects, saved views that contain lifecycle filters behave in the same way for both projects that are enabled for configuration management and that are not.

Import and extract wizards support filtering by module type

The Import Requirements and Extract Requirements wizards now filter the list of artifact types for the new module to show only module format types with a More option to display all types. In addition, the artifact types for the created requirements in the next step are also filtered by the module type's preferred types, if they exist, with another More option.

Copy from project: Correlating types by the same RDF URI or title

The Copy From Project operation that performs type system alignment was modified to correlate by title if the sameAs RDF URI property was missing or did not find any correlations. This makes the feature less sensitive to typing errors or missed entries.

Used In collections and reviews columns

Collections and Reviews are new grid columns that list all the collections or reviews that the artifact is used in.