-
Key: UML22-453
-
Legacy Issue Number: 12855
-
Status: closed
-
Source: NASA ( Alexander Murray)
-
Summary:
The specificMachine association of metaclass ProtocolConformance is of type ProtocolStateMachine, which would seem to prohibit the specificMachine from being a BehaviorStateMachines::StateMachine. However, the text sections of section 15.3.5, including the Description and Semantics sections, are very clear that the conforming StateMachine may be a BehavioralStateMachine::StateMachine, which make sense. So the specificMachine association should be changed to be type StateMachine. Also, Figure 15.5 should be similarly changed.
-
Reported: UML 2.1.2 — Wed, 17 Sep 2008 04:00 GMT
-
Disposition: Resolved — UML 2.2
-
Disposition Summary:
The protocol conformance relationship was explicitly intended to model relationships between protocol state machines
(this is clearly stated in the spec). It is unclear what would be the precise meaning of that type of relationship between
different kinds of state machines, but, whatever it might be, it is likely to be complex, dealing with issues such as
behavioral equivalence. This is still an open research topic with many different approaches and not something one
should standardize as yet.
Disposition: Closed - No Change -
Updated: Fri, 6 Mar 2015 20:58 GMT
UML22 — specificMachine association should be changed to be type StateMachine
- Key: UML22-453
- OMG Task Force: UML 2.2 RTF