Legacy Issue Number: 3201
Source: OpenModeling ( Jos Warmer)
Why is "FinalState" a separate metaclass ?
It seems that a final state can be modeled as a kind of PseudoState
(with PseudoStateKind = final).
FinalState has no attributes of its own, and all associations inherited
from State must be empty for a final state:
- A final state cannot have an entry action
- A final state cannot have an exit action
- A final state cannot have an doActivity
- A final state cannot have a deferrableEvent
- A final state cannot have an internalTransition
Could anybody explain the reason of existence for a FinalState metaclass ?
Reported: UML 1.2 — Mon, 10 Jan 2000 05:00 GMT
Disposition: Resolved — UML 1.3
Updated: Fri, 6 Mar 2015 21:37 GMT