What's new in IBM Engineering Requirements Management DOORS Next 7.1

The ancestors and descendants of matched artifacts can be viewed when artifacts in a module are filtered. When a filter is active, options to show the ancestors, descendants, or both appear automatically. These options can be saved in a view. Depending on the selection of the option, you can also select the Highlight filter matches check box to differentiate the artifacts that match the filter from the ancestors and descendants of those artifacts. Highlighting is a user preference and is not saved with the view, but it can be enabled at any time.

Most filters can be combined with new group operators, including matching all, some, or none of the conditions in a group of filters. Filters for the basic attribute data types are supported. Filters for enumerations, tags, links, or full text are not supported. The user interface for editing the expanded filters is enhanced, and it aligns with the Carbon Design System. Filters are easier to read, the targets are larger, and the keyboard accessibility is improved. Filters can be edited in a separate window.

The Create Baseline operation now provides the option to create a historical baseline of a stream. This option allows you to select a date and time in the past to capture the state of the artifacts at that point in time. The baseline that is created is referred as historical baseline and is like any other baselines.

You can now export and download the ReqIF definitions available in a baseline. The definitions need to have been created before the baseline creation.

The new com.ibm.rdm.fronting.web.artifactSidebarDefaultWidth advanced property for DOORS Next servers can be used to set the width of the artifact sidebar in the Artifact editor. Users can set the percentage of the artifact sidebar width to the overall window width. The default value is 20 percent. Users can still manually adjust the width.

Introduced the following enhancements to the REST APIs:

• Create a historical baseline of the stream. A new option Create Baseline is provided that allows you to create a historical baseline of a stream for a specific historical timestamp. The baseline of a stream that is created earlier is referred as historical baseline. The resulting baseline is not different from another baseline.
• Allow HTTP clients to retrieve the content of the delivered and undelivered changesets. The changes retrieved are same as the changes displayed in the Changed Resources tab in the Changeset editor screen. The retrieved data includes resources that are added or deleted and provides concept and version URIs.
• Retrieve a list of baselines for a given stream by introducing a new public OSLC configuration query capability. This capability allows HTTP clients to retrieve a list of baselines for a given stream.
  Note: This API only retrieves baselines that are not archived from a stream.
• Provide information about an artifact such as when it was created, modified, or deleted by a specific user within a given period.
• Added a filter to an existing REST API that retrieves history of an artifact to allow the API to retrieve history of an artifact within a given period.

For more information, see the following topics:

• DOORS Next (DN) Changeset Contents API Overview
• DOORS Next (DN) OSLC Configuration Query Capability Overview: To retrieve a list of baselines for a given stream URI
• DOORS Next Generation data sources

The Scaled Agile Framework methodology is an industry-standard framework for helping organizations scale agile and lean practices to an enterprise level. Now, SAFe® 6.0 Full and Essential templates are available to establish a quality management environment that contains artifacts to validate cross-solution train portfolio epics, cross-ART capabilities, and ART features and stories in the scope of a portfolio of solution trains of one or more ARTs and its teams.

For more information, see Scaled Agile Framework® 6.0 Requirement Management process templates.

The DOORS Next TRS component is now more resilient to unplanned server outage and heavy server load. This improved TRS design and implementation is called the log-based TRS, while the previous version is referred as the event-based TRS. The new DOORS Next v7.1 server uses the new improved log-based TRS. On upgrading an existing DOORS Next t server to v7.1, you must also switch to log-based TRS as part of the upgrade process as event-based is no longer supported in v7.1.

For more details, see Switch to Log based TRS .