State

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.

Pattern's participants :

• Context
  Defines the interface of interest to clients.
  Maintains an instance of a ConcreteState subclass that defines the current state.
• State
  Defines an interface for encapsulating the behavior associated with a particular state of the Context.
• ConcreteState subclasses
  Each subclass implements a behavior associated with a state of the Context.

Spoiled patterns :

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

Problems :

1. 1. Dynamic state changing