Issue 4739: UML 1.4: Wrong target for StateMachine.top association (uml2-superstructure-ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: A StateMachine compositely contains a State through the "top" association
[UML 1.4, pp. 2-147, fig. 2-24].

However, the wellformedness rules for StateMachine state that "A top state
is always a composite: self.top.oclIsTypeOf(CompositeState)" [UML 1.4, pp.
2-158].

If that is the case, the top association should target a CompositeState, not
the more general State.

Note: of course this is not an error as such, but if a wellformedness rule
can be expressed just as easily in UML, there is no reason to complicate
matters
Resolution: 
Revised Text: 
Actions taken:
December 6, 2001: received issue
March 9, 2005: closed issue
Discussion: 
The metamodel for state machines has completely changed in this area in UML
2.0, so this issue is no longer relevant.
Disposition: Closed, no change
End of Annotations:=====
From: Thomas Schaumburg <thomas.schaumburg@hiq.dk>
To: "'issues@omg.org'" <issues@omg.org>
Subject: UML 1.4: Wrong target for StateMachine.top association
Date: Thu, 6 Dec 2001 15:56:58 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-UIDL: Sdf!!D+Qd9&0Zd9J4C!!

A StateMachine compositely contains a State through the "top"
association
[UML 1.4, pp. 2-147, fig. 2-24].

However, the wellformedness rules for StateMachine state that "A top
state
is always a composite: self.top.oclIsTypeOf(CompositeState)" [UML 1.4,
pp.
2-158].

If that is the case, the top association should target a
CompositeState, not
the more general State.

Note: of course this is not an error as such, but if a wellformedness
rule
can be expressed just as easily in UML, there is no reason to
complicate
matters