Study Cards on transition, action, effect
In UML 1x this behavior was called an....
The reason for this limitation was that the action has to execute during the transition between the states. If it were to be interrupted, it would leave the state machine in some undefined state.
In UML 2.x, we call this a ....?
and do not enforce the atomic restriction.
- Call to an operation
- a sending of a signal
- some direct execution of opaque code
as long as it is understood by the :
- model readers
- or code generation engine
- of the modeling tool.
The “/” prevents confusion of the transition event with the transition effect
What does this arrow by (ReserveRequest / #res++) means
- Higher grades + faster learning
- Don't study anything twice
- 100% sure, 100% understanding