Issue 8297: Section: 13.3.3 (uml2-rtf) Source: (, ) Nature: Clarification Severity: Minor Summary: Multiplicities for the associations need to be added to the text for raisedException:Classifier[0..*], and changed in the associated diagrams to reflect the correct multiplicity (1 for method:Behavior (according to the text) and not * as shown in fig. 311 and 0..* for fig. 315). Unless "specializes" means the same thing as "redefines" change either the text for raisedException:Classifier from specializes to redefines or change fig 315. from redefines to specializes. Regardless, less confusion would occur if the text and the figure used the same word. Resolution: see above Revised Text: To avoid confusion, in Section 13.3.3, add “0..*” for all associations which do not have multiplicities shown. Editor’s note: I extended this fix to all associations in the entire section 13.3, not just 13.3.3 Actions taken: February 18, 2005: received issue August 23, 2006: closed issue Discussion: The issue text confuses the description of BehavioralFeature.behavior with a specificaiaton of multiplicity. End of Annotations:===== m: webmaster@omg.org Date: 18 Feb 2005 12:22:12 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Jane Messenger Company: U. S. Geological Survey mailFrom: jmessenger@usgs.gov Notification: Yes Specification: Superstructure Section: 13.3.3 FormalNumber: ptc/04-10-02 Version: 2.0 Draft Adopted RevisionDate: 10/08/2004 Page: 468 Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461) Description Multiplicities for the associations need to be added to the text for raisedException:Classifier[0..*], and changed in the associated diagrams to reflect the correct multiplicity (1 for method:Behavior (according to the text) and not * as shown in fig. 311 and 0..* for fig. 315). Unless "specializes" means the same thing as "redefines" change either the text for raisedException:Classifier from specializes to redefines or change fig 315. from redefines to specializes. Regardless, less confusion would occur if the text and the figure used the same word. Issue 8297: Section: 13.3.3 Issue summary Multiplicities for the associations need to be added to the text for raisedException:Classifier[0..*], and changed in the associated diagrams to reflect the correct multiplicity (1 for method:Behavior (according to the text) and not * as shown in fig. 311 and 0..* for fig. 315). Unless 'specializes' means the same thing as 'redefines' change either the text for raisedException:Classifier from specializes to redefines or change fig 315. from redefines to specializes. Regardless, less confusion would occur if the text and the figure used the same word. Discussion The issue text confuses the description of Behavioral Feature?.behavior with a specificaiaton of multiplicity. Revised Test To avoid confusion, in Section 13.3.3, add .0..*. for all associations which do not have multiplicities shown. Resolution