It shows 4 different forms for how use cases might be represented in SysML or UML: namely structured text, an activity diagram, an interaction model with sequence diagrams, and as an executable state machine model. The cool thing is that we’re free to use whatever you like. Neither SysML nor the UML specify how a use case shall look. The main thing to consider is that use cases take on a journey from analysis to design! Through-out this journey we will meet different people with different needs and levels of knowledge. We need to consider their needs, recognizing that different stakeholders will have different needs, and that needs will change over time. After all there is little value in building an executable state machine of a system, if a simple review of the use case description can determine that it is not what the customer wants after all.
Understand the art of the possible. My mission is to make executable Model-based Systems Engineering (MBSE) easy with the Object Management Group's Systems Modeling Language™ (SysML®) and UML® to make simple modeling easy to deploy to the masses. This site provides practical experience of tuning IBM® Rational® Rhapsody® - a precision engineering UML/SysML tool. Rhapsody tips and ideas will be posted with links to videos. You can follow by email (if google app is allowed).
Tuesday, 18 April 2017
4 Different Representations for Use Cases in OMG SysML/UML
This 6 minute video uses one of the example models from my 3 day Mastering MBSE with OMG SysML and IBM Rational Rhapsody training. I actually speak!
It shows 4 different forms for how use cases might be represented in SysML or UML: namely structured text, an activity diagram, an interaction model with sequence diagrams, and as an executable state machine model. The cool thing is that we’re free to use whatever you like. Neither SysML nor the UML specify how a use case shall look. The main thing to consider is that use cases take on a journey from analysis to design! Through-out this journey we will meet different people with different needs and levels of knowledge. We need to consider their needs, recognizing that different stakeholders will have different needs, and that needs will change over time. After all there is little value in building an executable state machine of a system, if a simple review of the use case description can determine that it is not what the customer wants after all.
It shows 4 different forms for how use cases might be represented in SysML or UML: namely structured text, an activity diagram, an interaction model with sequence diagrams, and as an executable state machine model. The cool thing is that we’re free to use whatever you like. Neither SysML nor the UML specify how a use case shall look. The main thing to consider is that use cases take on a journey from analysis to design! Through-out this journey we will meet different people with different needs and levels of knowledge. We need to consider their needs, recognizing that different stakeholders will have different needs, and that needs will change over time. After all there is little value in building an executable state machine of a system, if a simple review of the use case description can determine that it is not what the customer wants after all.
Monday, 17 April 2017
Rhapsody training updated to 8.2
Yep, it's official. In line with my goal to deliver the most up to date training, all my training has been updated to Rhapsody 8.2 (and what a nice release it is).
Sunday, 2 April 2017
Official launch of ExecutableMBSE.com
To better align with the refined mission statement of the business which is "to make executable MBSE simple through the provision of consulting and training services", I've created a new website http://www.executablembse.com/
The focus of this site (http://www.mbsetraining.com/) will remain on generic Rhapsody training & advice while aspects including the executable MBSE method, and updates to the supporting open-source SysML Helper profile, will be moved to the new website.
The focus of this site (http://www.mbsetraining.com/) will remain on generic Rhapsody training & advice while aspects including the executable MBSE method, and updates to the supporting open-source SysML Helper profile, will be moved to the new website.
Friday, 31 March 2017
Feedback from Rhapsody MBSE training on 15-17th March
Past performance is best indication of future performance. This was the aggregated top 5 feedback from my last training course (where 5 = Strongly agree and 1 = Strongly disagree):
Monday, 27 March 2017
Rhapsody Tip #21 - Display options for ports incl. PortsSingleLabelLayout (Intermediate)
Rhapsody has many properties and display options for how ports are show. This video shows some of these, including a rather cool (and slightly hidden) PortsSingleLabelLayout property. Some advanced ideas are also shown, such as using a stereotype to convey new default properties to a diagram as well as basic usability such as showing or hiding ports from display. Enjoy!
Friday, 27 January 2017
Run as administrator when doing Rhapsody 8.2 installation
Rhapsody 8.2 was released on 8th Dec 2016.
For 8.2 to correctly install you should right-click the setup.exe and choose Run as administrator (it is not sufficient that the user has admin rights to ensure correct installation)
Note also that there is an iFix1 for Rhapsody 8.2 client available on IBM's Fix Central website. If you're forming a deployment package then it may make sense to include this (which is critical if looking to use Jazz/dm with related iFix1, but also to ensure you're up to date with fixes).
For 8.2 to correctly install you should right-click the setup.exe and choose Run as administrator (it is not sufficient that the user has admin rights to ensure correct installation)
Note also that there is an iFix1 for Rhapsody 8.2 client available on IBM's Fix Central website. If you're forming a deployment package then it may make sense to include this (which is critical if looking to use Jazz/dm with related iFix1, but also to ensure you're up to date with fixes).
Sunday, 15 January 2017
Rhapsody Tip #20 - Adding a HyperLinkShortCut list to graphical elements for navigation (Simple)
In IBM Rational Rhapsody version 8.2 (released Dec 2016) to enhance navigation from individual graphic elements in diagrams, you can add a list of shortcuts that are accessible from the title bar of the element. In Rhapsody 8.2, the feature is only available for classes, objects, composite classes, and any "new term" elements based on these elements. It's still useful, however. This super short video shows how to use the Compartment display options to do it.
Subscribe to:
Posts (Atom)


