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.
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.
Subscribe to:
Posts (Atom)