Behavior : State Machine Diagrams - Transitions - Transition Effect
5 important questions on Behavior : State Machine Diagrams - Transitions - Transition Effect
A Transition may also have behavior associated with it.
In UML 1x this behavior was called an....
In the State Machine Diagrams, an action was limited to be noninterruptible and atomic at the current time scale.
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.
A transition effect may be a....
- 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.
- Higher grades + faster learning
- Never study anything twice
- 100% sure, 100% understanding
How is the Transition Effect listed?
The “/” prevents confusion of the transition event with the transition effect
Part 2:
What does this arrow by (ReserveRequest / #res++) means
![]()
The question on the page originate from the summary of the following study material:
- A unique study and practice tool
- Never study anything twice again
- Get the grades you hope for
- 100% sure, 100% understanding
![Trustpilot Logo](/images/design_2020/lp/clp-trustpilot-en.png)