Legacy Issue Number: 13509
Source: NASA ( Nicolas Rouquette)
Specification: Semantics of a Foundation Subset for Executable UML Models, FTF Beta 1 (ptc/08-11-03)
Section: 184.108.40.206.14 (ObjectFlow)
As shown in Fig. 12.14 of the UML 2.2 Beta1 specification, an ObjectFlow can have two optional behaviors,
a transformation and a selection. No such behaviors are supported in the fUML subset.
Add a second OCL constraint on ObjectFlow:
– An ObjectFlow cannot have a transformation or a selection behavior in the fUML subset.
self.transformation->isEmpty() and self.selection->isEmpty()
Reported: FUML 1.0b1 — Wed, 18 Feb 2009 05:00 GMT
Disposition: Resolved — FUML 1.0b2
The transformation and selection properties of ObjectFlow are only introduced at the level of CompleteActivities. And, per Subclause 7.4.1 of the fUML spec, “The UML 2 Superstructure package CompleteActivities is excluded in its entirety from fUML”. Since transformation and selection are association ends, their associations simply do not appear in the fUML subset, so no constraints are necessary.
Of course, the isMulticase and isMultireceive attributes on ObjectFlow are also only in CompleteActivities, but they still appear in the fUML subset (with constraints). However, these and other similar attributes should actually be removed from the fUML subset abstract syntax (see Issue 14561).
Disposition: Closed, no change
Updated: Fri, 6 Mar 2015 20:58 GMT