Rational Requirements Composer 4.0.1 gets mightier with modules!
VijaySankar 270000E5JQ Visits (5080)
Late last year, CLM (Collaborative Lifecycle Management) 4.0.1 was released. Rational Requirements Composer 4.0.1 was also part of it. This release marked a significant milestone for RRC with some great additions. In this post, I will try to briefly try to walk you through the new capabilities and enhancements made in RRC 4.0.1. For a more details, visit ibm.com or jazz.net pages.
CLM 4.0.1 has enhanced its higher enterprise development support with server renames and clustering. CLM 4.0.1 is now supported in Max OS X and also Safari and Chrome supports. Continuing with improving the flexibility when it comes to licensing, we introduced two varieties - CLM Contributor and Practitioner licenses. In 4.0.1, we have extended the workgroup licenses to RRC & RQM also. For a detailed review contact us or your respective account rep.
The biggest addition to RRC 4.0.1 is the inclusion of modules. So what are modules? Modules helps us in organizing the requirements into ordered lists and use hierarchy to group them. This is in addition to the collections we have presently. This helps Business Analysts to increase control for requirements by group and give teams’ additional meaning, awareness and understanding. Reporting of requirements could be improved significantly with documents with the templates provided.Here is a detailed video explaining modules in Requirements Composer.
The ability of comparing collections is also now included in RRC 4.0.1. This helps the business analysts to discover differences in project information progress quicker, learn what has changed and communicate across the team.
Ability to better control lock in a multi user environment is improved with an automatic edit lock option. The main utilities of this feature are to lock a requirement artifact while you are making changes or to apply permanent locks to restrict for security/regulation purposes.Here is a video showcasing the feature in detail.
We had introduced significant changes based on ReqIF in RRC 4.0. In this release, further improvements are made in terms of the ability to import the requirements into different projects. This enables for example of data transfer between DOORS & RRC; take the data offline to work on etc. We intend to improve the options available for offline data usage in the future releases.
Another significant improvement in RRC 4.0.1 is the RRC-HP Quality Center integration. Now we can directly preview QC tests in RRC. This helps in use of requirements definition and management capability from RRC to manage project requirements being tested using HPQC. The following screenshot showcases a customer using Requirements Composer to view various requirements collections. The user rests his pointer (“hovers”) over one of those collections and a pop-up window appears showing a preview of what’s contained in a test plan that’s being managed by HP Quality Center.
RRC 4.0.1 enables bi-directional connectivity from requirements to models/elements using Rational Software Architect (RSA), Rhapsody, and Design Manger. This seamless integration helps you to use requirements and models together to design and document the project needs.
To read more about enhancements in RRC 4.0.1, visit jazz.net.