Sinsing interpreting the state diagram in UML modeling

First, the concept of a state diagram

A state diagram, also called a state machine diagram, represents the state of a model element during its life. From the start state of the model element, respond to events, perform certain actions, cause the state to move to a new state, respond to an event in a new state, execute an action, cause to move to another state, so continuous, until the state is finalized.

In a word, the source state enters the target state after an event has passed.

Second, the features that the state diagram contains

A state diagram contains three features: State, event, combined state

(1) Status: State name, enter action, exit action, activity occurring in state (state activity, status outward sent activity)

(2) Event: an action, or activity, that occurs at some point in time at which the state has changed. Conditions for the transformation of a State

(3) Combined state: A state inside contains other states, becomes a combined state, and the internal contained state is called a sub-state. If the containing is a sub-state diagram, then the sub-state diagram must have its own starting and terminating states.

Third, the icon of the state diagram

(1) Status: Rounded Rectangle

(2) Convert: Implement arrows

(3) Event: Conversion Description text

(4) Starting state: Ball

(5) Termination status: Arrow with a circle pointing to the arrow

IV, State diagram description

State diagrams describe the various states of model elements in the system life cycle, where the model elements contain objects, classes, or subsystems, which can be large and small.

From a large perspective, we can divide a system into several subsystems, to divide the state of the system, in this case, we just want to understand that the system has a few modules, the mutual conversion between the modules. If we start doing the project, then this macro state diagram may be for users or non-developers to see.

From a small point of view, we can make a state analysis of an object in the system, this is to developers to see, we have to from the thin point of analysis, consider the overall, the system to make reliable.

For different needs, we are to make a different state diagram, is not static, we should be based on the specific situation to grasp the size of the state diagram or other graphs.

Sinsing interpreting the state diagram in UML modeling