Issue 8402: Section: 15.3.2 (uml2-rtf) Source: (, ) Nature: Revision Severity: Minor Summary: Fig. 354 shows the association owningState:State[*]. Please add this to the sub-section or delete it from the diagram. Also, explain how a state can have multiple final states as indicated by the multiplicity in the figure. In the sub-section Semantics, the first sentence seems to contradict constraint number [4]. Please clarify more fully how a final state may be entered if there can be no entry behavior. Resolution: see above Revised Text: The following constraints of section 15.3.2 shall be modified to have OCL specifications as follows: [2] A final state cannot have regions self.region->size() = 0 [3] A final state cannot reference a submachine self.submachine->isEmpty() [4] A final state has no entry behavior self.entry->isEmpty() [5] A final state has no exit behavior self.exit->isEmpty() [6] A final state has no state (doActivity) behavior self.doActivity->isEmpty() Actions taken: February 28, 2005: received issue August 23, 2006: closed issue Discussion: The issues here are all misunderstandings of the submitter. The association owningState in fig. 354 refers to the state constraint and not to FinalState. There is no issue with a region to have more than a single FinalState instances. The fact they can be reduced to a single instance doesn’t pose any semantic problem. Also there is no contradiction between the constraint of FinalState not to be associated with entry behavior definitions, with the fact that entering a FinalState has behavioral implications. However, some of this confusion stem from the lacking of OCLs in addition to English text. Therefore the OCL shall be added. End of Annotations:===== m: webmaster@omg.org Date: 28 Feb 2005 10:33:38 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Jane Messenger Company: U. S. Geological Survey mailFrom: jmessenger@usgs.gov Notification: Yes Specification: Superstructure Section: 15.3.2 FormalNumber: ptc/04-10-02 Version: 2.0 Draft Adopted RevisionDate: 10/08/2004 Page: 581 Nature: Revision Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461) Description Fig. 354 shows the association owningState:State[*]. Please add this to the sub-section or delete it from the diagram. Also, explain how a state can have multiple final states as indicated by the multiplicity in the figure. In the sub-section Semantics, the first sentence seems to contradict constraint number [4]. Please clarify more fully how a final state may be entered if there can be no entry behavior.