UML 2.6 RTF Avatar
  1. OMG Issue

UMLR — History pseudo states in protocol state machines

  • Key: UMLR-383
  • Legacy Issue Number: 19648
  • Status: open  
  • Source: KnowGravity Inc. ( Markus Schacher)
  • Summary:

    I see no reason why UML prohibits history pseudo states in protocol state machines (constraint at the bottom of page 362). As I understand history states, they are merely a syntactical convenience that may be loss-lessly converted into a semantically equivalent state machine without history states. However, using history states usually greatly simplifies the specification of complex protocol state machines.

  • Reported: UML 2.5 — Wed, 29 Oct 2014 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT