OCUP part 6: protocol state machines

In addition to the behavioral state machines described in the previous article (that model the behavior of individual entities), there are also „protocol state machines“, which express the valid transitions that can be triggered on a classifier instance.
This type of state machine is widely used in framework documentation to describe the permitted order in which operations of a class can be invoked. A good example for that is the hibernate persistence lifecycle.

A protocol state machine has the keyword „{protocol}“ in its diagram header to be distinguished from behavioral state machines.

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.