State Diagram

What is a state diagram, what does it visualise, where is it used and what advantages does it offer?

State Diagram Definition

A state diagram – also known as state chart, state machine diagram or state transition diagram – visualises a sequence of states that an object can assume in its lifecycle. It is used to describe the behavior of a system, subsystem, component, or class. The use of system interfaces can also be specified by state diagrams. Particular attention is paid to the transitions between different states of the object, the triggering actions and the properties of the object that it possesses or must possess before the state change.

Origin of the State Diagram

State diagrams are based on a concept by David Harel, an Israeli professor of computer science, who published Statecharts: A Visual Formalism for Complex Systems as early as 1987. Only later was the state diagram included as one of 14 diagram types in the Unified Modeling Language (UML) and identically constructed in the Systems Model Language (SysML). The concept was extended by hierarchically nested states, orthogonal areas and actions, which can depend on the state of the system and a triggering event at the same time. The use of entry and exit actions, which are more condition than action oriented, was also integrated. Thus, UML state machines have adopted properties of the Mealy and Moore machines.

UML 2.5 also defines behavioral state machines, which model the behavior of systems, system parts or instances of a class, and protocol state machines, which document protocols implemented by a system element.

Application of State Diagrams

State diagrams are often used in embedded systems for monitoring, controlling and regulating functions or for data or signal processing. Embedded systems – as a combination of software and hardware – often perform services invisibly for the user in cars, airplanes, refrigerators or elevators. They control cash dispensing at ATMs and ensure Aqua Stop at the dishwasher. Entire economic sectors such as medical technology, the entertainment industry, the communications industry or transport rely on embedded systems and thus also on state diagrams. And even in different areas of the company that take care of product production in the broadest sense, such as product and project management or requirements engineering, the use of state diagrams is widespread.

State Diagram - an Example

Explanations:

Initial state: A state diagram begins with an initial state, also known as a pseudo state.

Decision node: A decision has to be made after adding the points. If you score 100 or more, the exam is passed, if you score less, you fail.

Fork: If the exam is passed, the grade has to be determined and then published and the study certificate issued.

Join: After a forking follows a join .

Final state: The state machine ends with the final state, which is reached in two ways: by failing the exam and by publishing the grade and issuing the study certificate.

Advantages of State Diagrams

State diagrams are a very good tool for describing systems and their possible behaviour. They offer the following advantages:

  • The lifecycle of an object, from initialisation to release, can be modelled. This increases the common understanding of the participants about the modelled object.
  • The permitted states of an object and the events triggered by state transitions can be described. This makes the behavior of the object visible and comprehensible.
  • State diagrams can be used easily and in many situations, especially since even inexperienced readers can easily understand them with a little practice.

 

The important Terms in State Diagrams

The Finite State Machine

A state diagram shows a sequence of states of an object and visualises the actions by which state changes occur. A state diagram thus describes a finite state machine with a number of finite states at any given time. A machine is finite if the set of states it can assume is finite. The machine stores the states that have passed through from system start to the current point in time. A change of state indicates a change and is described by logical conditions. The state transition is only triggered if these conditions are fulfilled.

States

The UML 2.5 distinguishes between three types of states:

  • the simple state,
  • the composite state
  • and the submachine state.

A simple state has no sub-states and can include various activities and transitions. In principle, the following prerequisites must be fulfilled when modeling objects in state diagrams:

  • The object is always in exactly one of the defined states.
  • The object is never in any of the defined states.
  • The object is never in more than one state at a time.

Sub-states are possible with the composite state. For example, a door could know two states unlocked and locked and be open or closed in the unlocked state. Open and closed would be corresponding sub-states.

The submachine state describes a state that contains sub-states that are represented in a subordinate state diagram. States, which are composed of several sub-states, are also called complex states. If the complex state and exactly one sub-state are active, one speaks of disjoint sub-states. By dividing the state into regions, substates can also be concurrent and active at the same time. This is called orthogonal state or super-state.

Complex States

Pseudo States

In addition to the three types of states, there is a general classification of states: real states in which a system can be permanently located and pseudo states that a system cannot permanently occupy.

The pseudo state is an element that influences the process of a state machine. It is not a real state, because there are no value combinations that this state represents.

The UML 2.5 knows ten different pseudo states. Each describes a special property that controls the state transitions:

  • the initial state
  • the final state
  • the fork
  • the join
  • the junction
  • the choice
  • the entry point
  • the exit point
  • the shallow history
  • the deep history

History states are used if a transition is to return to the same state that was active before the transition occurred. With the shallow and the deep history state, there are two types of history states. The shallow history restores the previous state at the same level, while the deep history state activates the last active sub-state over an entire nesting depth. In principle, each state may only have a maximum of one shallow and one deep history state.

Transition

State changes from one state to the next are called transitions. They are triggered by events. Transitions connect two states, i.e. a source node and a destination node. The transition can be linked to a behavior specification that describes the behavior that leads to the state change. The triggered behavior is called an effect. In addition, there are guard expressions that ensure that transitions are only run through if the guard expression is true.

There are two types of state transitions:

  • Inner transitions are the reactions to an event that triggers an activity but not a state transition. No entry or exit activities are performed due to the missing state change (see events).
  • Outer transitions lead to a change of state due to the reaction to an event. Possible entry or exit activities are also executed accordingly. A special external transition is the self-transition, in which the source state and the target state are identical.

 

Transition in a State Diagram

Events

Events trigger transitions. They consist of a name and assigned arguments. A state can attach conditions to an event that must be fulfilled before a specific state can be assumed by an event. There are basically three possible behaviors for an event:

  • A behavior that is executed when the state machine enters the state (entry behavior).
  • A behavior that is executed when the state machine leaves the state (exit behavior).
  • A behavior that is executed as long as the state is not changed (do activity).

In addition, there is also a behavior that is executed when an event occurs, e.g. a “peep” noise during a mouse over. In addition to such signal events, there are call events for the reception of messages, time events for state transitions over time or at defined times and change events. In the case of a change event, a condition is permanently checked and a corresponding change of state is triggered if no monitoring condition blocks this. In contrast, a condition is only checked if an assigned event occurs. The condition itself cannot trigger a state transition.

Challenges for companies

The meaningful Usage of State Diagrams

State diagrams can be used universally. They can be used sensibly in project and product management, in change and risk management, or in requirements engineering. They help to describe system behavior and to define requirements. Due to their logical structure with specified states, transitions, events and conditions, they are ideally suited for modeling workflows using software. Visualisation of the various elements in the form of state diagrams is usually superior to documentation with tables. Nevertheless, companies must decide for which objects they want to use state diagrams to describe. Just because state diagrams provide an easy way to display, does not mean that organisations should now only sketch corresponding diagrams. It is advisable to use state diagrams only for complex objects, because the added value of using state diagrams is rather low for simply structured objects.

The behavior diagrams should always be designed in such a way that they can be read easily from top left to bottom right. Although a state diagram should describe the entire behavior of a state machine, it can be very useful to refine details in subordinate diagrams. A little practice is needed here. Basically, however, the UML 2.5 notation or its equivalent in SysML offers a clear and understandable structure that is easy to create and understand.

We are happy to provide you with knowledge, experience and 100% passion for your software development and requirements analysis. We help you with the collection, structuring and administration of requirements and pay attention to consistency, completeness and traceability. We support you in identifying technical correlations, model state diagrams and take stakeholders, goals and boundary conditions into account. And we implement your projects based on your requirements.

Find out more about software development here  »

More details and information ...