June 15, 2018
IBM Rational DOORS Next Generation
Definition · Management · Analysis
Rational DOORS Next Generation 6.0.3
Rational DOORS Next Generation 6.0.3 New & Noteworthy Summary
Rational DOORS Next Generation is an integral part of the Rational solution for Collaborative Lifecycle Management (CLM).
For a list of changes to the installation and upgrade process, see CLM and IoT CE 6.0.3 Installation and Upgrade Notes.
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.
Support for components
You can now manage versions of data at a finer level of granularity than entire project areas by dividing projects into smaller pieces called components. A component is a subdivision of a project area. Each project area has one or more components, and components do not cross project area boundaries. You can organize artifacts in a project area into multiple components.
Dividing a project into components provides flexibility for managing requirements. For example, you can reuse parts of a project in different places, or create a baseline for a smaller set of requirements. You might also divide the test strategy for a set of requirements across different teams, which allows test teams to work independently but maintain the version of the requirements that they test.
By reusing components, products can be decomposed into several components. These components can be managed like smaller products, and each component can be versioned separately with its own baselines and streams. Components can be developed by different teams on different schedules. For example, the following types of development projects might be divided into the following components:
- Phone: Screen, communications, bluetooth, and so on
- Car: Engine, drive train, braking system, locking system, and so on
- Software: GUI, data access, business logic, and so on
Streamlined application navigation
The Rational DOORS Next Generation interface was changed to simplify navigation.
and filtering are now separated. The left sidebar is used only for navigation, and the filter bar is used only for filtering. Also, the left sidebar now includes tabs.
- The header area now uses links instead of drop-down menus. An Artifacts link is available, and you can use tabs to see all artifacts, only module artifacts, or only collection artifacts. In previous releases, the drop-down menu items mixed navigation-related items with creation-related items. The creation-related items are now in the different navigational areas.
The following image shows an overview of the changes:
UI sketching support in in the diagram editor
The diagram editor includes a new palette and theme that you can use to create wireframe sketches. The palette contains several container-based shapes, and wireframe shapes also have custom properties that you can configure. The palette includes the following items:
- Windows, containers, browser
- Lists, trees, combo boxes
- Push buttons, radio buttons, check boxes
- Tabs, group boxes
- Menus and menu items
- Sliders and progress bars
Some general diagramming improvements were also made to the diagram editor. These improvements include stronger support for comments and links so that they are visible on diagrams, and a Copy & Paste as Link action to create links to diagrams or elements within a diagram.
Requirements Interchange Format (ReqIF) enhancements
Several key features were added to the ReqIF functions.
Selectively export module artifacts via ReqIF
You can now specify and add a module view to a ReqIF definition. If the view is a non-personal, single-module view (non-module shared), only the artifacts in the view are exported to the ReqIF output package.
Partial update of module structure via ReqIF
In addition to the ability to selectively export, the ReqIF import process performs partial updates on the structure of modules when the incoming package contains only a subset of all the artifacts in the module. New artifacts are added and the structure is modified as accurately as possible. Artifacts not present in the package are not deleted from the target module.
Support for incremental links in ReqIF
With incremental links, if you import a ReqIF package that has only one link endpoint, and then later import another ReqIF package that has the other endpoint, the link is created between the two endpoints. Incremental links are supported for the following imports:
Foreign ID and other information about the “away” database
Following the recommendations of the ProSTEP ReqIF Implementor Forum, system attribute values are exchanged using agreed alternative names so that other tools can understand them.
- ID: Exported as ReqIF.ForeignID, imported as ForeignID
- Created By: Exported as ReqIF.ForeignCreatedBy, imported as ForeignCreatedBy
- Modified By: Exported as ReqIF.ForeignModifiedBy, imported as ForeignModifiedBy
Reports for ReqIF imports and exports are organized by module
In ReqIF import and export reports, the information is grouped by module.
- Artifacts that are not in a module are listed separately.
- For each module, the report displays attribute definitions, artifact types, and artifacts for the module.
- The summary, data types, artifact types, links, and folder for a specific import or export of a ReqIF package is displayed at the root level.
- Artifact types are displayed at both the root level and the module level. Artifact types for the root level are specific to the ReqIF package and artifact types for the module level are specific to that module.
Removal of cross-project linking and filtering restrictions
Many of the cross-project and component linking and filtering restrictions were removed, which means you can create cross-project link constraints and filters between RM projects and components. When you use those features, the cross-project configurations must belong to the same global configuration.
When you create link constraints, you can select a cross-component type as the link end, and the cross-component name is displayed after the type name in cross-component types. Similarly, when you define new filters, you can filter based on types and attributes of remote components. When configured in the artifact's grid, an artifact's attributes are displayed for cross-project links.
Improved migration from Rational DOORS 9 to Rational DOORS Next Generation
You can now specify the artifact type for artifacts in incoming Rational DOORS 9 migration packages. During the import process, you can specify an existing artifact type to use as the type for each artifact during the import process. This feature allows basic artifact type mapping between Rational DOORS 9 and Rational DOORS Next Generation, and simplifies the mapping between their different data models.
New in previous versions of Rational DOORS Next Generation
For details about new features and functionality in previous releases, see these pages:
- Rational DOORS Next Generation & Noteworthy 6.0.2
- Rational DOORS Next Generation & Noteworthy 6.0.1
- Rational DOORS Next Generation & Noteworthy 6.0
- Rational DOORS Next Generation & Noteworthy 5.0.2
- Rational DOORS Next Generation & Noteworthy 5.0.1
- Rational DOORS Next Generation & Noteworthy 5.0
New in other CLM applications
For new and noteworthy information about other CLM applications, see these pages:
- Jazz Foundation (Jazz Team Server) and Global Configuration Management 6.0.3
- Change and Configuration Management 6.0.3
- Quality Management 6.0.3
- Jazz Reporting Service 6.0.3
- Rational Engineering Lifecycle Manager 6.0.3