Rhapsody Tip #38 - Introducing Diagram Views, new in 8.3.1 (Intermediate)

In my previous Rhapsody tips and tricks video I covered a feature of IBM Rational Rhapsody known as Custom Views. This capability worked in conjunction with things like Queries to create filtered views. The powerful thing about these views is that they can filter both the diagrams and the browser in Rhapsody. The thing is that the filtered diagrams would only be visible if the Custom View was active. In 8.3.1, the Rhapsody development team have expanded Rational Rhapsody’s capabilities by allowing these views to be persisted in the browser. These persisted views are known as diagrams views. As well as making it easier for users to access them, it also makes them easier to include in documents generated from the model. It’s a layer on top of other layers that adds a cool new capability. This short video demonstrates the base concepts of Diagram Views by building on the project created in the previous video.

Training material updated to 8.3.1 (Version 8 of Mastering MBSE with OMG SysML and IBM Rational Rhapsody)

My mission is provide up-to-date affordable and fun training for IBM Rational Rhapsody, i.e. latest release. I've just been through my Mastering MBSE with IBM Rational Rhapsody training labs to test and update to release 8.3.1 (Build 9835550). No major issues. Surprisingly good given that I had 650 tool training slides with no workarounds, hence my training can happily move to this version.

I did find occasional reload pop-up (not seen as an issue but will check).

I also had an issue with Notes populating correctly via API (presumably because it was changed to allow rich text hyperlinks). However, I then found that there is an iFix called 8.3.1-RAT-RHAPSODY-IFix1 that fixes this! (yep, should've installed this first. Doh!).

Summary is that 8.3.1 is worth for going over 8.3 but don't forget to check Fix Central for iFixes and install these at the same time. In terms of rational for 8.3 over 8.3.1 the RMM upgrades with 6.0.6 are enough to warrant this but also there's also polish in other areas worth keeping up with, e.g., I'm getting used to double-clicking to use stamp mode now.

Feedback from last week's MBSE with OMG SysML an IBM Rational Rhapsody training

Last week's Mastering MBSE with OMG SysML and IBM Rational Rhapsody 8.3 training was fun. This was the collated average feedback from the 9 attendees (where 5 = max, 1 = min):

Lot's of active participation again, with attendees from multiple companies (big auto-slant). I also learnt that the collective noun for a group of functional safety engineers is "a hazard" ;-)

Feedback/testimonials included:

"The presentation was clear and at a good pace. I feel I have gained a good understanding of the strengths of the tool" (senior electrical/electronics engineer)

"Trainer (Fraser) is very knowledgeable, very receptive and approachable to questions. Course provides a good overview of SysML" (software engineer)

"Good mixture of s/w, presentation & group activities" (engineer)

"I liked the flexibility on topics and insights / real-work experience of application" (snr engineer)

"I liked the entire class group exercises. Very much enjoyed the class. Fraser is a true expert and an excellent instructor" (director)

Rhapsody Tip #37 - Filter diagrams and the browser with CustomViews (Intermediate)

You can easily get the impression with IBM Rational Rhapsody's CustomViews that they're too powerful for their own good. The possibilities are endless though, hence they have a lot of pent-up power you can unleash. First introduced in 8.2.1, this video actually uses 8.3.1 to show them (hence you'll see me double-click the drawing toolbar to enable stamp mode!).

Rhapsody's CustomViews are a layer on top-up of existing layers, hence this video tries to build things up from the ground level. I first create a tag for ASIL A to D ratings and use a stereotype to convey the tag value to multiple elements. I can then easily create Query elements in the browser able to find elements with particular tag values, e.g., a query that finds all the elements with an ASIL tag value of D. Once I have the Queries built then I form some simple CustomViews that use the queries. Like Query elements, CustomViews appear in the browser, hence can be shared between projects in a profile. They can also be used to filter the browser. This is a bit like putting your reading glasses on (if you have them). Unlike filtering the browser with queries, you can multi-select the CustomViews to show in the browser or on diagrams (like putting on bifocal glasses?). Of course, this video just shows one example of usage. There are many other possibilities (modeling variants is one that springs to mind). Hope it helps!

Rhapsody 8.3.1 was made Generally Available (GA) on 15 Jun 18

Rhapsody 8.3.1 was released on 15th June 2018. Key things for me are:

1. Improvements related to Rhapsody Model Manager 6.0.6 (the RTC file-based replacement to Design Manager's client-server based architecture). RMM supports OSLC with increased scalability and ability to work over WAN and in software-centric workflows (like RTC). P.s. Although I mention software-centric, there is equally important thing for systems engineers especially in shared environments where you're exchanging models. Don't forget, RMM is licensed with Design Manager Jazz licenses. Existing users with Designer and Developer licenses under maintenance therefore have entitlement to use it.

2. More little usability tweaks. The intersection bridges and stamp mode improvements are ones I've already covered in tips and tricks videos, but there are others (e.g. diagram views allow you to persist query-based views of diagrams and enables some new 'interesting' possibilities, particularly around filtering diagrams, e.g., for variants or SIL level views).

3. Visual Studio 2017. Important for software users that Rhapsody is keeping up with the every changing software world.

4. An option to display name of operation for Call Operation in activity diagram. This is a small but important enhancement for me as it opens up the possibility to use call operations better to re-use actions across activity diagrams. My SysMLHelper toolkit already supports improved call operation usage workflows hence this will help join the dots for those interested in that workflow. Importantly you can now write the operation description in the call operation's compartment on the diagram.

5. Webify in 64 bit. Hallelujah! Does this mean I no longer have to recommend sticking with the 32 bit for system simulations? The promised land is close.

6. Lots of AUTOSAR stuff (if that's your bag). Did you know AUTOSAR profile is created using MDA techniques, i.e. model-to-model transformations? I think it's rather clever how they keep up to date with the standard. Even, if you're not using AUTOSAR, Rhapsody is big in automotive usage.

This is the list of all the Rhapsody releases.

V7 of Mastering MBSE with SysML and Rational Rhapsody

I have just completed the version 7 update of my 4-day Rational Rhapsody SysML training material. As with the v6 material it's still based on Rhapsody v8.3. However, I've added an improvements particularly in the ports and interfaces area including new theory slides and a full new lab (covering standard vs proxy ports).  If any previous training attendees want the new slides then email me.

My next open training course is 3-4, 5-6 July in conjunction with HORIBA-MIRA academy. It's not only automotive focused but I imagine the topics of how SysML and Rhapsody can be used in 26262 and A-SPICE projects will be on the radar. Course is confirmed but there's still time to register if you're fast. There are options for 2-day Foundation in SysML, essentials 3-day or advanced 4-day training on SysML with Rhapsody. The material is up-to-date and developed with a license agreement with IBM.

Looking at a Pizza chain system from 4 different perspectives - MBSE Interest Group Mtg - 22 Jun 18

Following on from a practical session I tried another team exercise at the INCOSE UK MBSE Interest Group yesterday (at Thales in Reading) using white boards. This came from positive feedback to the idea of the last practical session I did (on ports). The topic this time was around the confusion that is often caused if you don't understand or stakeholders misinterpret the system context. 

The room was split into 4 different teams and each team was given 10 minutes to come up with the use cases for a Pizza restaurant chain that makes Pizza, from a different perspective: The organisation, a restaurant, the kitchen and the chef were the 4 levels. These were the results:

Each team then presented back and we explored the idea of looking at a system-of-systems like this with use cases at different levels, how actors and goals might be different at different levels of abstraction and how the higher levels allow you to make bigger decisions with more impact.

Personally I think there's a lot of value of doing recursive use cases system models, and ensuring that all use case models are created in team workshops rather than individually. Also, I think it was good also as it gets people talking and learning each others view points. I enjoyed the meeting and learnt a lot from the feedback. Importantly, rapport is often key in a team and getting each others views really helps this. I might use the idea in my next training!