| Using ports for state machine interactions [message #1009151] |
Thu, 14 February 2013 14:58  |
 Yannick S.
Messages: 15
Registered: February 2013 |
Junior Member |
|
|
Hello, all.
Using Papyrus 0.8.2 for SysML modeling, I'm looking for a way to :
* have two blocks with state machines as behavior
* describe their interactions with standard ports providing and requiring an interface with receptions (for example)
* use the interface attached to the ports to trigger the transitions (and therefore, use the transition effects to call the required interface).
Of course, the state machines have other external inputs, but this is not the point here.
I'm able to use "receive signal events", attached to a signal, as triggers, but these events are simply owned by a package and not related to the ports or interface.
I would like to make sure that every communication is managed by ports.
Might seem obvious for you, but I'm afraid I'm a bit lost in Papyrus and probably SysML also (in books it seems so easy ...).
I would appreciate if somebody would be kind enough to provide a step-by-step explanation of how to do this (if it's possible ?), or something similar.
Best regards.
|
|
|
|
| Re: Using ports for state machine interactions [message #1011341 is a reply to message #1009151] |
Tue, 19 February 2013 10:57  |
Eclipse User |
|
|
|
Yannick,
every trigger can specify a port where this event is expected to be
received. See page 191 in UML 2.2 spec.
This will do the trick.
Marc-Florian
"Yannick S." schrieb im Newsbeitrag news:kfiu20$soc$1@xxxxxxxxe.org...
Hello, all.
Using Papyrus 0.8.2 for SysML modeling, I'm looking for a way to :
* have two blocks with state machines as behavior
* describe their interactions with standard ports providing and requiring an
interface with receptions (for example)
* use the interface attached to the ports to trigger the transitions (and
therefore, use the transition effects to call the required interface).
Of course, the state machines have other external inputs, but this is not
the point here.
I'm able to use "receive signal events", attached to a signal, as triggers,
but these events are simply owned by a package and not related to the ports
or interface.
I would like to make sure that every communication is managed by ports.
Might seem obvious for you, but I'm afraid I'm a bit lost in Papyrus and
probably SysML also (in books it seems so easy ...).
I would appreciate if somebody would be kind enough to provide a
step-by-step explanation of how to do this (if it's possible ?), or
something similar.
Best regards.
|
|
|
|
Powered by
FUDForum. Page generated in 0.02643 seconds
] 
Search
Help
Register
Login
Home
