Issue 6105: Pin/parameter matching 3 (uml2-superstructure-ftf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Significant
Summary: If the multiplicity of a parameter has zero lower bound, how does that
affect the execution semantics of an invocation action on the
behavior/operation?  If the pin value is optional in this case, then it
violates the current semantics.

Resolution: see above
Revised Text: 
Actions taken:
August 30, 2003: received issue
March 8, 2005: closed issue
Discussion: 
Behavior parameters with minimum multiplicity of zero are optional, by the definition of
multiplicity. There is no violation of activity semantics.
To clarify, in the Semantics section of Parameter (as specialized), p 353, add this
sentence at the end of the section, in the same paragraph as "See semantics of Action and
ActivityParameterNode.":
"Also see MultiplicityElement, which inherits to Parameter. It defines a lower
and upper bound on the values passed to parameter at runtime. A lower bound of
zero means the parameter is optional. Actions using the parameter may execute
without having a value for optional parameters. A lower bound greater than zero
means values for the parameter are required to arrive sometime during the
execution of the action."
In the Semantics section of Action, p 281, replace the sentence just after the numbered
list "See ValuePin for exception to rule for starting action execution." with:
"See ValuePin and Parameter for exceptions to rule for starting action execution."
End of Annotations:=====
Name: Conrad Bock
Company: NIST
mailFrom: conrad.bock@nist.gov
Nature: Revision
Severity: Significant
Subject: Pin/parameter matching 3


If the multiplicity of a parameter has zero lower bound, how does that
affect the execution semantics of an invocation action on the
behavior/operation?  If the pin value is optional in this case, then it

Reply-To: <conrad.bock@nist.gov> 
From: "Conrad Bock" <conrad.bock@nist.gov> 
To: "uml2ftf" <uml2-superstructure-ftf@omg.org> 
Subject: ,av,,ac, Activity/Action issues, the easy ones, 6105, 6121 
Date: Thu, 8 Jan 2004 17:13:01 -0500 
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) 
Importance: Normal 


Activity/Action WG,


I added clarifications to the following proposals in the the "easy"
list.


Conrad




****************************************************************************
*****************
Issue 6105: Pin/parameter matching 3            Activities      Conrad B.
http://www.omg.org/issues/issue6105.txt
yourdirectory/uml2-superstructure-ftf.open.html#Issue6105


Resolved


Behavior parameters with minimum multiplicity of zero are optional, by
the definition of multiplicity.  There is no violation of activity
semantics.


To clarify, in the Semantics section of Parameter (as specialized), p
353, add this sentence at the end of the section, in the same paragraph
as "See semantics of Action and ActivityParameterNode.":


  "Also see MultiplicityElement, which inherits to Parameter.  It
   defines a lower and upper bound on the values passed to parameter at
   runtime.  A lower bound of zero means the parameter is optional.
   Actions using the parameter may execute without having a value for
   optional parameters.  A lower bound greater than zero means values
   for the parameter are required to arrive sometime during the
   execution of the action."


In the Semantics section of Action, p 281, replace the sentence just
after the numbered list "See ValuePin for exception to rule for starting
action execution." with:


  "See ValuePin and Parameter for exceptions to rule for starting action
  execution."




Issue 6105: Pin/parameter matching 3            Activities      Conrad B.
http://www.omg.org/issues/issue6105.txt
yourdirectory/uml2-superstructure-ftf.open.html#Issue6105


Resolved


Behavior parameters with minimum multiplicity of zero are optional, by
the definition of multiplicity.  There is no violation of activity
semantics.


To clarify, in the Semantics section of Parameter (as specialized), p
353, add this sentence at the end of the section, in the same paragraph
as "See semantics of Action and ActivityParameterNode.":


  "Also see MultiplicityElement, which inherits to Parameter.  It
   defines a lower and upper bound on the values passed to parameter at
   runtime.  A lower bound of zero means the parameter is optional.
   Actions using the parameter may execute without having a value for
   optional parameters.  A lower bound greater than zero means values
   for the parameter are required to arrive sometime during the
   execution of the action."


In the Semantics section of Action, p 281, replace the sentence just
after the numbered list "See ValuePin for exception to rule for starting
action execution." with:


  "See ValuePin and Parameter for exceptions to rule for starting action
  execution."
violates the current semantics.