Issue 17536: Specifying the multiplicity of a part with an attribute (uml2-rtf) Source: Lockheed Martin (Mr. John Watson, jcwatson(at)ieee.org) Nature: Clarification Severity: Minor Summary: This is a request to add a capability in UML to specify the upper and/or lower multiplicity value of a part (composite aggregation relationship) with a class attribute of type integer; typically this attribute is a derived attribute. When derived, a constraint can be used to define the value derivation. This capability has been found to be useful in the following applications. 1. When reference models are re-used in different contexts this capability allows some variants to be specified in the reference model and the value be automatically derived based on its use in the new context. 2. The value of the multiplicity to be used for a specific configuration may be derived through an analysis performed external to the model. A diagram is available that shows an example of the concrete syntax that could be used. In this example a constraint is defined for the attribute “numberOfPedals”. If this diagram would be helpful and I can forward it. I did not see a means of attaching a jpg diagram to this on-line form. This capability can be developed in a way that does not impact on code generation or execution, as the values can all be constant at run time (and at code-generation time). The primary purpose of this is to allow the ability to have reference models for variations without using the overhead of templates (otherwise the whole model might need to be a template of template, which would certainly be unwieldy and confusing), and to allow for a common way of specifying this for descendant languages like SysML. Resolution: Revised Text: Actions taken: August 2, 2012: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 02 Aug 2012 12:26:53 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: John Watson Employer: Lockheed Martin mailFrom: john.watson@lmco.com Terms_Agreement: I agree Specification: OMG UML Section: 9.12.1 FormalNumber: 2011-08-05 Version: 2.4.1 Doc_Year: 2011 Doc_Month: August Doc_Day: 01 Page: 65 to 68 Title: Specifying the multiplicity of a part with an attribute Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Description: This is a request to add a capability in UML to specify the upper and/or lower multiplicity value of a part (composite aggregation relationship) with a class attribute of type integer; typically this attribute is a derived attribute. When derived, a constraint can be used to define the value derivation. This capability has been found to be useful in the following applications. 1. When reference models are re-used in different contexts this capability allows some variants to be specified in the reference model and the value be automatically derived based on its use in the new context. 2. The value of the multiplicity to be used for a specific configuration may be derived through an analysis performed external to the model. A diagram is available that shows an example of the concrete syntax that could be used. In this example a constraint is defined for the attribute .numberOfPedals.. If this diagram would be helpful and I can forward it. I did not see a means of attaching a jpg diagram to this on-line form. This capability can be developed in a way that does not impact on code generation or execution, as the values can all be constant at run time (and at code-generation time). The primary purpose of this is to allow the ability to have reference models for variations without using the overhead of templates (otherwise the whole model might need to be a template of template, which would certainly be unwieldy and confusing), and to allow for a common way of specifying this for descendant languages like SysML.