UML22 — Section: Activities

Object node should be a multiplicity element, and use multiplicity upper for upperbound

Though seemingly small, this would actually be a significant change to the metamodel for activities and it would fundamentally change the current semantics for multiplicity of pins, which now only effect the execution of actions. If object node in general were made a multiplicity element, one would not only have to reconcile the current semantics of object node upper bound with the semantics of the multiplicity upper bound of a pin, one would also need to consider what the general semantics are for the multiplicity lower bound of an object node.
This issue is thus considered strategic and out of scope for an RTF.
Revised Text:
None
Disposition: Closed Out of Scope