STATECHART DIAGRAM
SOFTWARE ENGINEERING
INTRODUCTION
DEFN: STATE CHART DIAGRAM
• A State chart (or state diagram) in software engineering is a graphical representation of a
system's states and the transitions between those states.
• It is part of the Unified Modeling Language (UML) and is used to describe the dynamic
behaviour of a system, particularly in terms of how it responds to events or changes in
conditions.
• It describes a state machine. State machine can be defined as a machine which defines
different states of an object and these states are controlled by external or internal events.
A State chart diagram consists of states, transitions, and events.
States represent the different states of an object or system,
transitions represent the movement from one state to another, and
events represent the triggers that cause the system to change state.
Consider a simple example of a Traffic Light System:
• States: Green, Yellow, Red
• Transitions:
o From Green to Yellow when a timer expires
o From Yellow to Red when the timer expires
o From Red to Green when the timer expires
• Events: Timer expiration
PURPOSE OF STATE DIAGRAM:
• To model dynamic aspect of a system.
• To model life time of a reactive system.
• To describe different states of an object during
its life time.
• Define a state machine to model states of an
object.
STATE DIAGRAM SYMBOLS:
State defines current condition of an event or activity. State
diagram is often used to describe state changes triggered by
events.
Start state symbol signals the first step of a process.
End state symbol stands for the result of a process.
Transition takes operation from one state to another and
represents the response to a particular event.
Decision were introduced in UML to support conditionals in
activities.
STATE CHART DIAGRAM OF AN ORDER MANAGEMENT SYSTEM:
ATM TRANSACTION:
USES OF STATE CHART DIAGRAM:
• To model the object states of a system.
• To model the reactive system. Reactive system consists
of reactive objects.
• To identify the events responsible for state changes.
• Forward and reverse engineering.
THANK YOU…