Issue 8295: Section: 13.3.2 (uml2-rtf) Source: (, ) Nature: Revision Severity: Significant Summary: Specialization mentioned for the association context:BehavioredClassifier[0..1] is not shown on figure 311. Multiplicities for ownedParameter:Parameter in the text do not agree with fig. 311. According to the text the ownedParameter:Parameter references a list of parameters "that can be given" which implies that no parameters may be given and therefore the multiplicity should be [0..*]. This is not what is shown in fig. 311. Multiplicities for remaining associations listed do not agree between the text and the diagrams (fig. 311 & 313). Multiplicities should probably be [0..*] which are not what are shown in figs. 311 & 313. Add the specialization for the association redefinedBehavior:Behavior in the text to agree with fig. 311. Specializations listed for the associations precondition:Constraint and postcondition:Constraint do not agree with fig. 313. Figure 313 shows that these associations subset ownedRule. Add OCL notation to the constraints where possible or indicate that OCL notation is not available. Resolution: In the recent version of the specification, the specialization for context:BehavioredClassifier has already been added. The multiplicities mentioned above are all “*” which is equivalent to “0..*”. To correct the remaining mismatch between text and diagram: Revised Text: In section 13.3.2, subsection “Associations”, add to the end of the text following bullet “redefinedBehavior: Behavior” the following: “(Subsets redefinedElement)” At the end of bullet “precondition: Constraint” replace “(Subsets Namespace::constraint and Constraint::context)” by “(Subsets Namespace::ownedRule)” At the end of bullet “postcondition: Constraint” replace “(Subsets Namespace::constraint and Constraint::context)” by “(Subsets Namespace::ownedRule)” Actions taken: February 17, 2005: received issue October 27, 2008: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 17 Feb 2005 16:54:16 -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.2 FormalNumber: ptc/04-10-02 Version: 2.0 Draft Adopted RevisionDate: 10/08/2004 Page: 465-466 Nature: Revision Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461) Description Specialization mentioned for the association context:BehavioredClassifier[0..1] is not shown on figure 311. Multiplicities for ownedParameter:Parameter in the text do not agree with fig. 311. According to the text the ownedParameter:Parameter references a list of parameters "that can be given" which implies that no parameters may be given and therefore the multiplicity should be [0..*]. This is not what is shown in fig. 311. Multiplicities for remaining associations listed do not agree between the text and the diagrams (fig. 311 & 313). Multiplicities should probably be [0..*] which are not what are shown in figs. 311 & 313. Add the specialization for the association redefinedBehavior:Behavior in the text to agree with fig. 311. Specializations listed for the associations precondition:Constraint and postcondition:Constraint do not agree with fig. 313. Figure 313 shows that these associations subset ownedRule. Add OCL notation to the constraints where possible or indicate that OCL notation is not available. Issue 8295: Section: 13.3.2 Issue summary Specialization mentioned for the association context:BehavioredClassifier[0..1] is not shown on figure 311. Multiplicities for ownedParameter:Parameter in the text do not agree with fig. 311. According to the text the ownedParameter:Parameter references a list of parameters 'that can be given' which implies that no parameters may be given and therefore the multiplicity should be [0..*]. This is not what is shown in fig. 311. Multiplicities for remaining associations listed do not agree between the text and the diagrams (fig. 311 & 313). Multiplicities should probably be [0..*] which are not what are shown in figs. 311 & 313. Add the specialization for the association redefinedBehavior:Behavior in the text to agree with fig. 311. Specializations listed for the associations precondition:Constraint and postcondition:Constraint do not agree with fig. 313. Figure 313 shows that these associations subset ownedRule. Add OCL notation to the constraints where possible or indicate that OCL notation is not available. Discussion With respect to the multiplicity .*., this is the same as .0..*.. The default rule when writing this specification was that association have multiplicity .*. when omitted. However, it is probably better to list these multiplicities explicitly. -- ThomasWeigert - 26 May 2005 Resolved, with the exception of OCL. -- ThomasWeigert - 26 May 2005 Revised Test In Section 13.3.2., context, mark context as derived. Delete the phrase .(Specializes Redefinable Element?.redefinitionContext.). In Figure 311, mark Behavior.context as derived. For all omitted multiplicities in the text of this section, add multiplicity .*.. For consistency, change the use of .0..*. in this section to .*.. For precondition and postcondition, change the parenthetical section to .(Specializes Namespace.ownedRule.). Resolution