Issue 19866: Prose for semantics of AddStructuralFeatureValueAction required (fuml-rtf) Source: Fraunhofer FOKUS (Mr. Marc-Florian Wendland, marc-florian.wendland(at)fokus.fraunhofer.de) Nature: Clarification Severity: Minor Summary: UML 2.5, section 16.8.3.3 Add Structural Feature Value Actions says: "The semantics are undefined for adding a value that violates the upper multiplicity of the StructuralFeature, and for adding a new value to a StructuralFeature with isReadonly=true after initialization of the object that would have the value." In fUML, this undefined semantics is resolved. Values are simply added to the StrucutalFeature of the target object. This semantics is also described in the implementation of AddStructuralFeatureValueActionActivation.doAction() (section 8.6.3.2.1, pp. 298). Since this implementation represents the resolution of an undefined semantics of the UML specification, section 7.5.3.2.1 AddStructuralFeatureValueAction should add a prose description of this resolution to its "semantics" clause. It would increase the readability and comprehensibility of the spec. Resolution: Add note on AddStructuralFeatureValueAction Agreed, in principle. However, 7.5.3.2.1 in the fUML specification does not have a "semantics clause", because it is in the clause on abstract syntax, not semantics. Instead, a note should be added under "Structural Feature Actions" in 8.6.3.1, the Overview for Intermediate Actions. Also, currently, the UML specification reference still needs to be to the UML 2.4.1 Superstucture Specification. Revised Text: In 8.6.3.1, under "Structural Feature Actions", after the first paragraph, add: Note: The UML Superstructure Specification (subclause 11.3.5) states that, for an add structural feature value action, "The semantics is undefined for adding a value that violates the upper multiplicity of the structural feature." Nevertheless, the fUML semantics are defined in this case, such that the given value is always added, even though it violates the upper multiplicity of the structural feature. Actions taken: December 3, 2015: received issue April 6, 2017: Resolved June 22, 2017: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 03 Dec 2015 02:38:28 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Marc-Florian Wendland Employer: Fraunhofer FOKUS mailFrom: marc-florian.wendland@fokus.fraunhofer.de Terms_Agreement: Specification: Semantics of a Foundational Subset for Executable UML Models (fUML) Section: 7.5.3.2.1 FormalNumber: ptc/2015-09-08 Version: 1.2 Doc_Year: 2015 Doc_Month: September Doc_Day: 08 Page: 75 Title: Prose for semantics of AddStructuralFeatureValueAction required Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Remote Name: fokus169084.fokus.fraunhofer.de Remote User: HTTP User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 Time: 02:38 AM Description: UML 2.5, section 16.8.3.3 Add Structural Feature Value Actions says: "The semantics are undefined for adding a value that violates the upper multiplicity of the StructuralFeature, and for adding a new value to a StructuralFeature with isReadonly=true after initialization of the object that would have the value." In fUML, this undefined semantics is resolved. Values are simply added to the StrucutalFeature of the target object. This semantics is also described in the implementation of AddStructuralFeatureValueActionActivation.doAction() (section 8.6.3.2.1, pp. 298). Since this implementation represents the resolution of an undefined semantics of the UML specification, section 7.5.3.2.1 AddStructuralFeatureValueAction should add a prose description of this resolution to its "semantics" clause. It would increase the readability and comprehensibility of the spec.