Blogs about Jazz

Blogs > Jazz Team Blog >

What’s new in Rational Quality Manager 6.0?

IBM Rational Quality Manager (RQM) 6.0 brings both incremental improvements over v5 and a completely new dimension to managing test artifacts. On the incremental improvements front, the team has done a great job to continue to work closely with our customers to further improve the user experience on specific areas such as dashboard widgets or collaboration. At the same time, v6.0 introduces the support of configuration management for test artifacts, linked to other domains such as requirements or design, and contributing to the notion of global configurations across our Collaborative Lifecycle Management (CLM) solution. This version marks the beginning of a completely new set of capabilities that empower users to do parallel development and test, and to reuse artifacts in an effective way.

Improved user experience

Continuing on the work done in RQM 5.0.1 with the introduction of the Test Artifact dashboard widget, RQM 6.0 offers the new Test Statistics widget. Both of those widgets leverage the saved queries created in one of the test artifact views, such as the Test Case Execution Record view. Those live queries can now be reused with their results displayed directly on a dashboard. The Test Statistic widget offers the option to display the result in table format or in graphs such as bar charts, pie charts, or column charts.

The team has also worked on improving collaboration support, specifically for concurrent modification of test artifacts. If two people modify the same test plan, suite, or case at the same time, the second person to attempt to save is now prompted with the option to merge the changes.

Single sign-on authentication

On top of the existing types of single sign-on (SSO) authentication already supported, this version introduces the Jazz Security Architecture SSO based on the OpenID Connect authentication protocol. The new Jazz Authorization Server simplifies the authentication administration. Read more in John Vasta’s post about SSO options in CLM 6.0.


In v5, we introduced Jazz Reporting Service (JRS) as a new option to generate customizable analytics reports with a user-friendly web-based report builder. In v6.0, JRS is now included directly in the CLM package. This increases the availability for better reporting services for all of your applications without requiring the additional effort of organizing, installing, and configuring reporting capability through a separate download and install. There are also a number of new capabilities which make JRS the recommended analytics reporting solution for CLM, such as calculation and roll-up along with graphical report drill-through, new out-of-the-box reports, and interactive runtime filters in the dashboard widget. If you’d like to learn more, see Ernest Mah’s post on reporting in CLM 6.0.

Configuration management

RQM 6.0 is the first release that includes capabilities to aid in configuration management of test artifacts.

On a basic level, configuration management enables users to better manage changes and to go back in time if needed through the creation of baselines and the ability to compare and merge. Users can create baselines to record a state in time of a Quality Management (QM) project area. Baselines are immutable and defined for an entire project area. Test artifacts of a baseline cannot be modified. Users can then compare the current state of a QM project area with any previous baseline. The comparison provides both a high-level view of the differences at the project area level as well as a detailed side-by-side comparison at the artifact level. Then, users have the opportunity to roll back some of the changes by merging a previous baseline into the current state and replacing some artifacts with the previous versions from that baseline.

In a more advanced usage model, configuration management offers the ability for testers to work independently and in parallel on multiple versions or variants of test artifacts. Users can create parallel streams by branching from an existing baseline. Streams are versions of all the test artifacts of a project area that can be changed. Users can merge changes made in one stream into another by first looking at the differences and then replacing all or some of the current versions by the versions of the artifacts in the baseline.

The local Quality Management configurations, both streams and baselines, can then be contributed to global configurations. Global configurations are cross-domain configurations that can link to multiple local configurations from the Requirements Management, Design Management, Software Configuration Management, and Quality Management applications. Global configurations are used to define a common context in which users can work and create all the deliverables for a given version or variant.

Finally, by creating a hierarchy of global configurations, it is possible to manage composite product definitions and configurations that enable complex reuse scenarios at the subsystems and components levels.

Learn more about RQM 6.0