This is the second of two videos that explores how Jazz-based Rhapsody Model Manager workings have changed in the 3 releases from 6.0.6 to 7.0.1. It follows on from tip #88. The main change is that the /am functionality is now provided as an extension to the /ccm application. This means that work items and model management are stored in the same repository. There is also a new license that enables the /ccm server to be used for either just Rhapsody models, or Rhapsody models and source code. In this caption-based video I look at a few aspects of using 7.0.1, including associating changes to work items, and being able to do more functions like accepting change sets directly from the Rhapsody browser. I also recap how to establish links to requirements in the IBM Engineering Requirements Management DOORS Next application (/rm) - although this is not new.
Friday, 20 November 2020
IBM Engineering Rhapsody Tip #89 - Exploring how RMM has changed, 6.0.6 to 7.0.1 - Part 2 of 2 (Intermediate)
Here's the transcript in case it helps:
In this silent video, I look at enhancements added between 6.0.6 and 7.0.1 in Rhapsody Model Manager (RMM) - the server-side technology for managing Rhapsody projects in IBM's Jazz platform.
Remember, in 7.0.x Jazz, RMM is now part of the /ccm application, not a separate /am application.
This makes integrated work item planning easier, as it's now managed by the same /ccm Jazz application as the change sets.
In 7.0.1, a new RMM license called "Model Manager - Systems and Software Engineer" is used rather than the "Design Manager" license.
Let's make changes to our model under RMM 7.0.1 control.
As in 6.0.6, I can also add OSLC links to requirements stored in the Jazz-based DOORS Next.
From Rhapsody menus, we can exploit Jazz governance and change tracking, e.g., associating changes with work items in /ccm.
Here we can see that the change set has been attached to the work item.
The Engineering Workflow Manager (EWM) Eclipse client still provide more advanced configuration management features such as work item editing.
Tight integration between model management and change management means that linked data and history is automatically captured.
You can also manage things like approvals and reviews using work items linked to elements under review.
Another key theme in the 3 releases since 6.0.6 has been additional menus enabling more EWM commands in the Rhapsody browser. Let's switch user.
Having got Bob to deliver his changes, I've switched user to Deb now.
She's notified of Bob's changes.
She can see there are changes directly in the Rhapsody browser from the descandant overlay icons.
She doesn't need to leave the Rhapsody client to know that changes have been made.
This is new! In 9.0.1 Rhapsody, she can accept incoming change sets directly from the Rhapsody menus.
Her Rhapsody model has been updated with the changes made by Bob.
To finish off, let's have a look at the RhapsodyModelManager > Requirements Coverage Table.
Here we can see the traceability that the elements in this package have with requirements, including those in DOORS Next.
Interested in RMM or Rhapsody training/customisations? Email me.