| SysML behaviour modeling in Papyrus [message #1771389] |
Thu, 24 August 2017 15:05  |
 Ursula Kirchgaessner
Messages: 18
Registered: July 2017 |
Junior Member |
|
|
Hello, I am new to SysML and trying to set up a model in Papyrus. I am having difficulties finding the best way to define elements, because the notation in Papyrus seems not to correspond to the standard as I understand it from the book "A practical guide to SysML" by Friendenthal et al. (2009) and from the OMG standard Version 1.5.
I am trying to model object flow between actions (as described in section 8.5 of the book). Questions:
- In order to define the hierarchy of activities in a block definition diagram, how can I create <<activity>> blocks (as shown in the standard: table 11.3 p. 117)? Do I need to define a dedicated profile myself?
- Once I have defined the activity blocks, I indend to specify their behavior (in this case: an activity) as operations, which I detail in appropriate diagrams (activity, state). Is this what I should do?
- According to the standard, the call behavior actions in the activity diagram should show "action name : behavior name" and it should show a fork symbol in the lower right corner. I never get any colon nor fork in the diagram. Is this a question of settings? If yes, how can I "correct" this? If no, what is the logic in Papyrus? I suspect, I am not setting the right values and links in the properties of the action.
- Finally, I would like to create sequence and package diagrams, but I cannot find this type of diagram in the list. How can I model sequences? Should I use the interaction overview diagram for the package diagram?
I attach the screenshot of my minimal example.
Apart from my questions, any comment that could help me to better understand and use this tool is welcome!
|
|
|
| Re: SysML behaviour modeling in Papyrus [message #1771394 is a reply to message #1771389] |
Thu, 24 August 2017 16:00  |
|
Hi Ursula,
- In order to define the hierarchy of activities in a block definition diagram, how can I create <<activity>> blocks (as shown in the standard: table 11.3 p. 117)? Do I need to define a dedicated profile myself?
That feature is not yet supported in Papyrus. In block diagram currently you can only put blocks and not activities (even it is allowed by the specification).
- Once I have defined the activity blocks, I intend to specify their behavior (in this case: an activity) as operations, which I detail in appropriate diagrams (activity, state). Is this what I should do?
Simplest way is to create an activity diagram below your activity and then get immediate navigation from activity to its associated behavior.
- According to the standard, the call behavior actions in the activity diagram should show "action name : behavior name" and it should show a fork symbol in the lower right corner. I never get any colon nor fork in the diagram. Is this a question of settings? If yes, how can I "correct" this? If no, what is the logic in Papyrus? I suspect, I am not setting the right values and links in the properties of the action.
Well if you really use "CallBehaviorAction" then you have to define the "behaviour" property for the action by referencing another activity. And "fork" symbol should appear.
- Finally, I would like to create sequence and package diagrams, but I cannot find this type of diagram in the list. How can I model sequences? Should I use the interaction overview diagram for the package diagram?
Those diagrams are not "SysML specific" diagrams. They should be available from model explorer or top menu.
You will get sequence diagram available from an interaction element.
Package diagram should be available from "model" (root) element or from any package element.
best regards
raphaël
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03001 seconds
] 
Search
Help
Register
Login
Home
