One: state diagram---> Status graph shows a state machine. The---> state machine is used to model the dynamic nature of the element. More specifically, the event-driven aspects of system behavior are modeled. ---> typically use a state diagram to illustrate the possible state of a business role or business entity----the actions that result from events and state transitions that cause state transitions---> state machine is primarily used to describe the state of an object to determine what behavior alters the state of the object, and how the object's state changes affect the system. (1) Initial state: The initial state is the position of the state machine, and he does not need to trigger the event. (2) Status: A state is a condition when an object executes an activity or waits for an event. (3) Composite state: A state with a sub-state (or a nested state) becomes a composite state. (4) Transfer: A transition is a relationship between two states, which indicates that the object of the first State performs some action and enters the second state when a specified event occurs and the specified condition is met. (5) Event: a specific action or behavior, sometimes including a timer such as the system clock. If the condition is met, the occurrence of the event triggers a transfer. (6) Condition: The condition is a Boolean expression that checks the value of the expression when the event occurs. The conditional evaluation result may decide which branch to transfer, or reject the transfer. A condition may refer to the current state. (7) Final state: The final state indicates the end of the state machine execution, or the end of the object life cycle.
< 16 >uml Core view Dynamic view state diagram
