| State entry/exit/do behavior : reusing existing behavior [message #1008214] |
Mon, 11 February 2013 09:15  |
Eclipse User |
|
|
|
Hello,
using Papyrus 0.9.1a or 0.8.2 (TOPCASED) for SysML modeling, it seems I can only create (for example) a new activity to specify an entry behavior.
I would like to reuse the same activity several times, for several states, possibly with a parameter, but this does not seem to be possible.
So, is there some workaround, or is what I want to do not SysML compliant ?
Thank you for your help.
|
|
|
|
| Re: State entry/exit/do behavior : reusing existing behavior [message #1008616 is a reply to message #1008247] |
Wed, 13 February 2013 05:16  |
| Eclipse User |
|
|
|
Hello, Raphaël,
this is clear, thanks for the fast answer.
Well, I'm just a beginner with SysML (and UML ...) and don't know the specifications in detail.
However, from a systems engineer's point of view, I feel this is not user-friendly, and using calls as you suggest would be a solution, but too cumbersome for the need.
The model should be simple and easy to understand because it's a means of communication.
There are many examples, i. e. in the OMG tutorials (distiller controller), where it seems obvious that you need the same behavior with only a slight change in a parameter.
Also, in a BDD, when a block A "owns" a part typed by block B, it does not mean that another block C could not also include a part typed by B.
After all, reusing blocks is one of the aims here.
So, maybe the UML specification is too restrictive, but some usability improvement would be welcome.
Regards.
Yannick.
|
|
|
Powered by
FUDForum. Page generated in 0.28804 seconds
Home