Issue 6109: ObjectFlowEffect (uml2-superstructure-ftf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Significant
Summary: ObjectFlowEffect requires edges from pins to actions.
Resolution: see above
Revised Text: 
Actions taken:
August 30, 2003: received issue
March 8, 2005: closed issue
Discussion: 
Rather than reintroduce edges from pins to actions, move effect to parameters,
as specified below.
In Figure 186:
move the effect attribute on ObjectFlow to Parameter in Figure 189.
move ObjectFlowEffectKind to Figure 189 and rename it
ParameterEffectKind.
Updated Figure 186 shown below.   Updated Figure 189 shown below, with changes from Issue 6115
included.    In ObjectFlow class:
In Description section, after (CompleteActivities), change the first
sentence to: "Object flows add support for multicast/receive, token
selection from object nodes, and transformation of tokens."
In Attributes (CompleteActivities) section, delete the entry for effect.
In Constraints section: delete constraint [6].
In Notation section:
delete the paragraph above Figure 269.
move Figure 269 to the Notation section for Pin, above the last
sentence.
In Example section:
in the paragraph above Figure 273, delete the last sentence.
move the lower part of Figure 273 to a new figure at the end of the
Example section fo r Pin. In the ObjectFlowEffectKind class:
Rename the class to ParameterEffectKind and realphabetize with the
other classes.
Change the description to
"The datatype ParameterEffectKind is an enumeration that
indicates the effect of a behavior on values passed in or out of its
parameters. See Parameter."
In Parameter class:
In Attributes section, add this entry in alphabetical order with the others:
effect : ParameterEffectKind [0..*] Specifies the effect that the
owner of the parameter has on values passed in or out of the
parameter.
In Constraints section, add this constraint:
“Only in and inout parameters may have a delete effect. Only out, inout,
and return parameters may have create effect.”
In Semantics section, in a new paragraph before the last one, add:
“The effect of a parameter is a declaration of the modeler's intent, and
does not have execution semantics. The modeler must ensure that the
owner of the parameter has the stated effect.”
In the Pin class,
In the Notation section
before the last sentence, put Figure 269 from the Notation section
for ObjectFlow, and remove it from ObjectFlow.
above the figure just inserted, add this paragraph:
“(CompleteActivities) Specifying the effect that the behavior
of actions have on the objects passed in and out of their
parameters can be represented by placing the effect in
braces near the edge leading to or from the pin for the
parameter.” In the Examples section:
at the end, insert a new figure by moving in the lower part of Figure
273 to here.
above the figure just inserted, add this paragraph:
“In the figure below, an example depicts a Place Order
activity which creates orders and Fill Order activity which
reads these placed orders for the purpose of filling them.”
End of Annotations:=====
Name: Conrad Bock
Company: NIST
mailFrom: conrad.bock@nist.gov
Nature: Revision
Severity: Significant
Subject: ObjectFlowEffect


OMG Issue No: 6109
Title:	ObjectFlowEffect
Source:
Kabira Technologies, Inc. (Mr. Conrad Bock, conrad.bock@nist.gov)
Summary:
ObjectFlowEffect requires edges from pins to actions.
Discussion:
Rather than reintroduce edges from pins to actions, move effect to parameters, as specified below.
In Figure 186:
move the effect attribute on ObjectFlow to Parameter in Figure 189.
move ObjectFlowEffectKind to Figure 189 and rename it ParameterEffectKind.
Updated Figure 186 shown below. 

Updated Figure 189 shown below, with changes from Issue 6115 included.

In ObjectFlow class:
In Description section, after (CompleteActivities), change the first sentence to: "Object flows add support for multicast/receive, token selection from object nodes, and transformation of tokens."
In Attributes (CompleteActivities) section, delete the entry for effect.
In Constraints section: delete constraint [6].
In Notation section:
delete the paragraph above Figure 269.
move Figure 269 to the Notation section for Pin, above the last sentence.
In Example section:
in the paragraph above Figure 273, delete the last sentence.
move the lower part of Figure 273 to a new figure at the end of the Example section for Pin.

In the ObjectFlowEffectKind class:
Rename the class to ParameterEffectKind and realphabetize with the other classes.
Change the description to 
"The datatype ParameterEffectKind is an enumeration that indicates the effect of a behavior on values passed in or out of its parameters.  See Parameter."

In Parameter class:
In Attributes section, add this entry in alphabetical order with the others:
effect : ParameterEffectKind [0..*]  Specifies the effect that the owner of the parameter has on values passed in or out of the parameter.

In Constraints section, add this constraint:
.Only in and inout parameters may have a delete effect.  Only out, inout, and return parameters may have create effect..

In Semantics section, in a new paragraph before the last one, add:
.The effect of a parameter is a declaration of the modeler's intent, and does not have execution semantics.  The modeler must ensure that the owner of the parameter has the stated effect..

In the Pin class,
In the Notation section
before the last sentence, put Figure 269 from the Notation section for ObjectFlow, and remove it from ObjectFlow.
above the figure just inserted, add this paragraph:
.(CompleteActivities) Specifying the effect that the behavior of actions have on the objects passed in and out of their parameters can be represented by placing the effect in braces near the edge leading to or from the pin for the parameter..
In the Examples section:
at the end, insert a new figure by moving in the lower part of Figure 273 to here.
above the figure just inserted, add this paragraph:
.In the figure below, an example depicts a Place Order activity which creates orders and Fill Order activity which reads these placed orders for the purpose of filling them..
Disposition:	Resolved
ObjectFlowEffect requires edges from pins to actions.