Login :
Password :

Design patterns


Static diagram :

Static diagram

Description :

Type :  Be  (Behavioral)
Intent : Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.
Applicability : Use the State pattern in either of the following cases :
- An object's behavior depends on its state, and it must change its behavior at run-time depending on that state.
- Operations have large, multipart conditional statements that depend on the object's state. This state is usually represented by one or more enumerated constants. Often, several operations will contain this same conditional structure. The State pattern puts each branch of the conditional in a separate class. This lets you treat the object's state as an object in its own right that can vary independently from other objects.

Strong points :

  1. 1. Extensibility
    1. 1.1 States' protocol factorization
    2. 1.2 Addition or removal of a state does not need code modification
  2. 2. Simplified management
    1. 2.1 Possibility of state modification at execution time without deletion
    2. 2.2 State behavior decoupling

Pattern's participants :

Spoiled patterns :

  1. 1. Bad classification
  2. 2. Hidden switch statement

Problems :

  1. 1. Dynamic state changing
Les têtes de mule