State diagrams in LLD - System Design Guide

Problem Statement

When software components have complex behaviors that depend on many conditions, it becomes hard to track all possible states and transitions. This confusion leads to bugs, unexpected behavior, and difficulty in maintenance.

Solution

State diagrams visually map out all possible states of a component and the transitions triggered by events. This clear visualization helps developers understand, design, and implement behavior systematically, reducing errors and improving communication.

Architecture

┌───────────┐      event1      ┌───────────┐
│  State A  │ ───────────────▶ │  State B  │
└───────────┘                  └───────────┘
     ▲                              │
     │          event2              │ event3
     └──────────────────────────────┘
                 

This diagram shows two states, A and B, with arrows representing events that cause transitions between them.

Trade-offs

✓ Pros

→

Provides a clear, visual way to understand complex state-dependent behavior.

→

Helps identify all possible states and transitions, reducing missed edge cases.

→

Improves communication among developers and stakeholders by using a common visual language.

✗ Cons

→

Can become cluttered and hard to read if the system has too many states or transitions.

→

Requires upfront effort to create and maintain diagrams as the system evolves.

→

May oversimplify behavior if not detailed enough, leading to false confidence.

Use when a component or system has multiple states with complex transitions, especially when behavior depends on events or conditions. Ideal for UI workflows, protocol handling, or business logic with clear states.

Avoid for very simple components with linear or stateless behavior, or when the number of states is extremely large and better modeled with other techniques like state machines in code.

Real World Examples

Uber

Uses state diagrams to model ride lifecycle states such as requested, accepted, in-progress, and completed to manage driver and rider interactions.

Netflix

Models streaming session states like buffering, playing, paused, and stopped to handle user controls and network conditions.

Airbnb

Uses state diagrams to represent booking states such as requested, confirmed, canceled, and completed to coordinate host and guest actions.

Code Example

The before code uses a boolean flag without clear state management, which can become confusing as complexity grows. The after code uses an explicit state enum to represent door states, making transitions clear and easier to maintain.

LLD

### Before: No clear state management
class Door:
    def __init__(self):
        self.is_open = False

    def open(self):
        if not self.is_open:
            print("Door opened")
            self.is_open = True

    def close(self):
        if self.is_open:
            print("Door closed")
            self.is_open = False


### After: Using state pattern with explicit states
from enum import Enum

class DoorState(Enum):
    CLOSED = 1
    OPEN = 2

class Door:
    def __init__(self):
        self.state = DoorState.CLOSED

    def open(self):
        if self.state == DoorState.CLOSED:
            print("Door opened")
            self.state = DoorState.OPEN
        else:
            print("Door is already open")

    def close(self):
        if self.state == DoorState.OPEN:
            print("Door closed")
            self.state = DoorState.CLOSED
        else:
            print("Door is already closed")

Alternatives

Flowcharts

Flowcharts focus on process steps and decisions rather than explicit states and transitions.

Use when: Choose flowcharts when the focus is on procedural logic rather than stateful behavior.

Sequence diagrams

Sequence diagrams show interactions over time between components, not internal states.

Use when: Use sequence diagrams to model message exchanges rather than state changes.

Summary

State diagrams visually represent all states and transitions of a system component.

They help prevent bugs by clarifying complex state-dependent behavior.

Use them when your system has multiple states triggered by events or conditions.

Practice

1. What is the main purpose of a state diagram in system design?

easy

A. To display the database schema and relationships

B. To list all the classes and their methods in a system

C. To show different states of a system and how it moves between them

D. To outline the network topology of system components

Solution

1. Step 1: Understand what a state diagram represents

   A state diagram shows the various states a system or component can be in and the transitions triggered by events.

2. Step 2: Compare with other diagrams

   Class diagrams show classes and methods, database diagrams show data structure, and network diagrams show connections, not states.

3. Final Answer:

   To show different states of a system and how it moves between them -> Option C

4. Quick Check:

   State diagram = system states and transitions [OK]

Hint: State diagrams focus on states and transitions only [OK]

Common Mistakes:

• Confusing state diagrams with class diagrams
• Thinking state diagrams show data structure
• Assuming state diagrams show network layout

2. Which of the following is the correct syntax to represent a transition from state A to state B on event start in a state diagram?

easy

A. A => start => B

B. A -> B : start

C. A --start--> B

D. A -start-> B

Solution

1. Step 1: Recall standard state diagram notation

   Transitions are usually shown as arrows with the event label after a colon, like A -> B : event.

2. Step 2: Match options with notation

   A -> B : start matches this format exactly. Others use incorrect symbols or order.

3. Final Answer:

   A -> B : start -> Option B

4. Quick Check:

   Transition syntax = A -> B : event [OK]

Hint: Use arrow then colon for event label in transitions [OK]

Common Mistakes:

• Using double dashes instead of single arrow
• Placing event before arrow
• Omitting colon before event label

3. Given the following state diagram code snippet:

Idle -> Processing : start
Processing -> Idle : stop
Processing -> Error : fail

What is the next state if the system is in Processing and receives the fail event?

medium

A. Error

B. Idle

C. Processing

D. Start

Solution

1. Step 1: Identify current state and event

   The system is in Processing state and receives fail event.

2. Step 2: Find matching transition

   From Processing, on fail, the transition goes to Error.

3. Final Answer:

   Error -> Option A

4. Quick Check:

   Processing + fail = Error [OK]

Hint: Match current state and event to transition target [OK]

Common Mistakes:

• Choosing Idle instead of Error
• Confusing event names
• Ignoring event and state pairing

4. Identify the error in this state diagram transition:

Start -> Running : begin
Running -> Paused : pause
Paused -> Running pause

What is wrong with the last transition?

medium

A. Missing colon before event name

B. Wrong arrow direction

C. State name misspelled

D. Extra event name

Solution

1. Step 1: Review transition syntax

   Transitions should have a colon before the event name, e.g., State1 -> State2 : event.

2. Step 2: Check last transition

   The last line is Paused -> Running pause missing the colon before pause.

3. Final Answer:

   Missing colon before event name -> Option A

4. Quick Check:

   Colon before event is required [OK]

Hint: Check for colon before event label in transitions [OK]

Common Mistakes:

• Ignoring missing colon
• Assuming arrow direction is wrong
• Thinking state name is incorrect

5. You are designing a state diagram for a vending machine with states: Idle, Selecting, Dispensing, and OutOfStock. Which transition should be added to handle the event stockEmpty when the machine is in Idle?

hard

A. Dispensing -> OutOfStock : stockEmpty

B. Idle -> Dispensing : stockEmpty

C. OutOfStock -> Idle : stockEmpty

D. Idle -> OutOfStock : stockEmpty

Solution

1. Step 1: Understand event context

   The event stockEmpty means no items are left to dispense.

2. Step 2: Determine correct transition from Idle

   If the machine is Idle and stock is empty, it should move to OutOfStock state.

3. Final Answer:

   Idle -> OutOfStock : stockEmpty -> Option D

4. Quick Check:

   stockEmpty from Idle leads to OutOfStock [OK]

Hint: Event triggers transition to correct state logically [OK]

Common Mistakes:

• Transitioning to Dispensing when stock is empty
• Reversing transition direction
• Ignoring event meaning