Home » Modeling » Papyrus » StateMachine local vs. external transition
| StateMachine local vs. external transition [message #1006568] |
Thu, 31 January 2013 19:42  |
|
According to the UML specification (2.5 b1 pag. 377)
A transition may be one of these three kinds:
internal
Implies that the Transition, if triggered, occurs without exiting or entering the source State (i.e., it does not cause a state change). This means that the entry or exit condition of the source State will not be invoked. An internal Transition can be taken even if the SateMachine is in one or more Regions nested within the associated State.
local
Implies that the Transition, if triggered, will not exit the composite (source) State, but it will exit and re-enter any state within the composite State that is in the current state configuration.
external
Implies that the Transition, if triggered, will exit the composite (source) State.
As far as I understand, the internal basically implies the execution of an Action within the source state when certain condition occurs. Am I right?
the external is the transition that actually corresponds to a change from the source state to the target state.
I can't really see the meaning of the local transition explanation. May someone please provide a simple example helping me to get it?
Regards
Follow me on Twitter @andreasindico
[Updated on: Thu, 31 January 2013 19:45] Report message to a moderator |
|
|
| Re: StateMachine local vs. external transition [message #1006639 is a reply to message #1006568] |
Fri, 01 February 2013 10:00  |
 Klaas Gadeyne
Messages: 165
Registered: July 2009 |
Senior Member |
|
|
Andrea Sindico wrote on Thu, 31 January 2013 14:42According to the UML specification (2.5 b1 pag. 377)
A transition may be one of these three kinds:
internal
Implies that the Transition, if triggered, occurs without exiting or entering the source State (i.e., it does not cause a state change). This means that the entry or exit condition of the source State will not be invoked. An internal Transition can be taken even if the SateMachine is in one or more Regions nested within the associated State.
local
Implies that the Transition, if triggered, will not exit the composite (source) State, but it will exit and re-enter any state within the composite State that is in the current state configuration.
external
Implies that the Transition, if triggered, will exit the composite (source) State.
As far as I understand, the internal basically implies the execution of an Action within the source state when certain condition occurs. Am I right?
the external is the transition that actually corresponds to a change from the source state to the target state.
I can't really see the meaning of the local transition explanation. May someone please provide a simple example helping me to get it?
Regards
Hi,
As far as I remember, the difference is that, in the case of a "local" transition, both "exit" and "entry" actions of the state will be executed. In the case of an internal one, they will not be executed (only the action specified on the transition itself will be executed.
|
|
|
| Re: StateMachine local vs. external transition [message #1006845 is a reply to message #1006639] |
Sat, 02 February 2013 19:47 |
Eclipse User |
|
|
|
Andrea,
please have also a look in the more elaborated (simlified?) UML 2.5 spec at
http://www.omg.org/spec/UML/2.5/Beta1/, section 14.2.3 and 14.2.4,
especially Figure 14.32 Local Transitions.
In short, a local transition does not exit a composite state and, thus,
never executed the exit behavior of the composite state. Local transitions
are only valid in composite states, where source and target Vertex are
different.
Regards,
Marc-Florian
"Klaas Gadeyne" schrieb im Newsbeitrag
news:keg3n4$8a9$1@xxxxxxxxe.org...
Andrea Sindico wrote on Thu, 31 January 2013 14:42
> According to the UML specification (2.5 b1 pag. 377)
>
> A transition may be one of these three kinds:
>
> internal
> Implies that the Transition, if triggered, occurs without exiting or
> entering the source State (i.e., it does not cause a state change). This
> means that the entry or exit condition of the source State will not be
> invoked. An internal Transition can be taken even if the SateMachine is in
> one or more Regions nested within the associated State.
>
> local
> Implies that the Transition, if triggered, will not exit the composite
> (source) State, but it will exit and re-enter any state within the
> composite State that is in the current state configuration.
>
> external
> Implies that the Transition, if triggered, will exit the composite
> (source) State.
>
> As far as I understand, the internal basically implies the execution of an
> Action within the source state when certain condition occurs. Am I right?
> the external is the transition that actually corresponds to a change from
> the source state to the target state.
> I can't really see the meaning of the local transition explanation. May
> someone please provide a simple example helping me to get it?
>
> Regards
Hi,
As far as I remember, the difference is that, in the case of a "local"
transition, both "exit" and "entry" actions of the state will be executed.
In the case of an internal one, they will not be executed (only the action
specified on the transition itself will be executed.
|
|
| | |
Goto Forum:
Current Time: Thu Apr 25 07:21:47 GMT 2024
Powered by FUDForum. Page generated in 0.03530 seconds |
] 
Search
Help
Register
Login
Home
