Issue 6677: UML 2 Super/Activities/invalid multiplicity 0 (uml2-superstructure-ftf) Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org) Nature: Uncategorized Issue Severity: Summary: InterruptibleActivityRegion::edgeContents redefines the multiplicity of ActivityGroup::edgeContents to be 0, which violates the constraint that an upper bound must be greater than 0 Resolution: see above Revised Text: Actions taken: December 4, 2003: received issue March 8, 2005: closed issue Discussion: The minimum multiplicity was set to zero because edges have no special semantics in interrupting regions, but consequently there is no effect of including them either. Remove the specialized association. In Figure 191, p 276, remove the association between InterruptibleActivityRegion to ActivityEdge. End of Annotations:===== Issue 6677: UML 2 Super/Activities/invalid multiplicity 0 http://www.omg.org/issues/issue6677.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6677 Resolved In Figure 191, p 276, remove the "0" multiplicity from the edgeContents end from InterruptibleActivityRegion to ActivityEdge. In Constraints section of InterruptibleActivityRegion, p 337, add: "[2] Interruptible regions cannot contain edges." ubject: UML 2 Super/Activities/invalid multiplicity 0 X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: Branislav Selic Date: Thu, 4 Dec 2003 15:22:39 -0500 X-MIMETrack: Serialize by Router on D25ML05/25/M/IBM(Release 6.0.2CF1|June 9, 2003) at 12/04/2003 15:22:41, Serialize complete at 12/04/2003 15:22:41 InterruptibleActivityRegion::edgeContents redefines the multiplicity of ActivityGroup::edgeContents to be 0, which violates the constraint that an upper bound must be greater than 0 Bran Selic IBM Software Group -- Rational Software 770 Palladium Drive Kanata, Ontario, Canada K2V 1C8 ph. (613) 591-7915 fax (613) 599-3912 Date: Mon, 29 Dec 2003 16:15:39 +0000 From: Guus Ramackers Organization: Oracle User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en, en-us To: conrad.bock@nist.gov CC: uml2ftf Subject: Re: ,av,,ac, Activity/Action issues, the easy ones Conrad, This set looks good. Quick questions with 3 of them: **************************************************************************** ***************** Issue 6139: Partition semantics Activities Jim O http://www.omg.org/issues/issue6139.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6139 Resolved In Semantics section of ActivityPartition, p 308, before the next-to-last paragraph, add a new paragraph saying: "Elements other than actions that have behaviors or value specifications, such as transformation behaviors on edges, adhere to the same partition rules above for actions." **************************************************************************** GR: - The issue text refers to decisions as well - these cannot be categorized as 'actions'. Apart from transformations or perhaps general action annotations, I can't see any additional behaviors in an AG - am I missing something? - Perhaps the partition semantics for "Elements other than actions that are not behaviors" should be clarified. It is not clear why "ValueSpecifications" are the only [additional] ones that are called out. **************************************************************************** ***************** Issue 6369: Clarify join specs referencing control flow edges Activities Conrad B http://www.omg.org/issues/issue6369.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6369 **************************************************************************** ***************** GR: This one has no mark ups. I think it is duplicate. Issue 6677: UML 2 Super/Activities/invalid multiplicity 0 http://www.omg.org/issues/issue6677.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6677 Resolved In Figure 191, p 276, remove the "0" multiplicity from the edgeContents end from InterruptibleActivityRegion to ActivityEdge. In Constraints section of InterruptibleActivityRegion, p 337, add: [2] Interruptible regions cannot contain edges. **************************************************************************** ***************** GR: That clarifies the semantics as intended. Quick question: why can't edges be allowed (e.g. to model a try/catch block) Thanks, Guus Conrad Bock wrote: Activity WG, I went through all the activity and action issues, regardless of assignment, and made proposals for the easiest ones. See below. To review offline, download http://www.omg.org/issues/uml2-superstructure-ftf.open.html Then globally replace the string "yourdirectory" below with wherever you downloaded to. Happy holidays, Conrad **************************************************************************** ***************** Issue 4727: UML 1.4: Action containment error Actions Ian W. http://www.omg.org/issues/issue4727.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue4727 Closed no change. This has changed since UML 1.x. Actions are owned by Activity or StructuredNode. **************************************************************************** ***************** **************************************************************************** ***************** Issue 4937: Sending a signal after a delay Actions Ian W. http://www.omg.org/issues/issue4937.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue4937 Deferred Too much of an enhancement for FTF, as indicated in the issue report. In the meantime, modelers can define actions for time delay. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6129: Notation for isSynchronous Actions Ian W. http://www.omg.org/issues/issue6129.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6129 Closed no change The usual property list notation can used for this. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6131: Clarification of insert Actions Ian W. http://www.omg.org/issues/issue6131.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6131 Resolved In semantics of AddStructuralFeatureValueAction, p 220, at end of second paragraph, add the following sentence: "The insertion point is ignored when replacing all values." **************************************************************************** ***************** **************************************************************************** ***************** Issue 6132: SendObjectAction Actions Ian W. http://www.omg.org/issues/issue6132.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6132 Resolved In the Association section of SendObjectAction, p 255, change the description of request to: "The request object, which is transmitted to the target object. The object may be copied in transmission, so identity might not be preserved. (Specialized from InvocationActon.argument)" Just below that, change the description of target to" "The target object to which the signal is sent." In the Rationale section of SendObjectAction, p 255, change the sentence to: "Sends any object to a specified target object." **************************************************************************** ***************** **************************************************************************** ***************** Issue 6606: No way to represent "uninterpreted" actions Actions Ian W http://www.omg.org/issues/issue6606.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6606 Closed no change In UML 2, uninterpreted actions are modeled as activities with no nodes. Activity has attributes for uninterpreted strings. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6092: Clarify wording on executable activity nodes Activities Jim O http://www.omg.org/issues/issue6092.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6092 Closed no change The text is fine as is. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6093: Edge constraint for control nodes Activities Karl F http://www.omg.org/issues/issue6093.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6093 Resolved Remove constraint [1] for Control Node, p 317. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6094: Action should be concrete Activities Manfred K http://www.omg.org/issues/issue6094.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6094 Resolved In Figure 176, make Action concrete. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6099: ExpansionRegions keywords Activities Jim R. http://www.omg.org/issues/issue6099.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6099 Resolved In the Notation section of ExpansionNode, p 326, first sentence, replace "concurrent" with "parallel". In the Example section of ExpansionNode, p 330, Figure 247, replace "concurrent" with "parallel". **************************************************************************** ***************** **************************************************************************** ***************** 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 begin execution without having a value for optional parameters." **************************************************************************** ***************** **************************************************************************** ***************** Issue 6106: Pin/parameter matching 4 Activities Conrad B. http://www.omg.org/issues/issue6106.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6106 Resolved In the Semantics section of CallBehaviorAction, p 225, in the paragraph labelled [3], after the second sentence, add: "Any return or out values from the invoked behavior are not passed back to the containing activity." In the Semantics section of CallOperationAction, p 228, in paragraph labelled [4], after the first sentence, add: "Any return or out values from the invoked operation are not passed back to the containing activity." **************************************************************************** ***************** **************************************************************************** ***************** Issue 6108: Optional parameters Activities Conrad B. http://www.omg.org/issues/issue6108.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6108 Duplicate Duplicate with 6105. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6110: ExecutableNode, ControlNode should be abstract Activities Michael L http://www.omg.org/issues/issue6110.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6110 Resolved In Figure 176, p 268, make ExecutableNode and ControNode abstract. The class descriptions already reflects this. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6115: Parameter set corrections 1 Activities Karl F. http://www.omg.org/issues/issue6115.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6115 Resolved In Figure 189, p 275, reverse the end names of the association between Parameter and ParameterSet. The class descriptions already reflects this. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6116: Parameter set corrections 2 Activities Manfred K. http://www.omg.org/issues/issue6116.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6116 In Constraint section of ParameterSet, p 354, add this constraint: [3] Two parameters sets cannot have exactly the same set of parameters. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6118: Parameter set corrections 4 Activities Karl F. http://www.omg.org/issues/issue6118.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6118 Closed no change. The usual property list notation can used for this. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6119: Parameter set corrections 5 Activities Michael L. http://www.omg.org/issues/issue6119.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6119 Closed no change. Parameters can be optional. See issue 6105. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6120: Parameter set corrections 6 Activities Michael L. http://www.omg.org/issues/issue6120.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6120 Resolved In Semantics section ParameterSet, p 354, add this after the second sentence: "The same is true for operation with parameter sets." **************************************************************************** ***************** **************************************************************************** ***************** Issue 6121: Streaming Activities Conrad B. http://www.omg.org/issues/issue6121.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6121 Closed no change. Streaming and optionality/multiplicity are already seperate. See issue 6105. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6122: Parameter semantics clarification Activities Conrad B. http://www.omg.org/issues/issue6122.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6122 Closed no change The requested constraint is already there. The semantics text is consistent with that. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6135: Pins on structured nodes 1 Activities Jim R. http://www.omg.org/issues/issue6135.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6135 Resolved. In Figure 193, p 278, remove generalizations from ConditionalNode and LoopNode to Action. The figure makes StructuredActivityNode an Action, and ConditionalNode and LoopNode are already subtypes of StructuredActivityNode from Figure 192. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6139: Partition semantics Activities Jim O http://www.omg.org/issues/issue6139.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6139 Resolved In Semantics section of ActivityPartition, p 308, before the next-to-last paragraph, add a new paragraph saying: "Elements other than actions that have behaviors or value specifications, such as transformation behaviors on edges, adhere to the same partition rules above for actions." **************************************************************************** ***************** **************************************************************************** ***************** Issue 6141: Activity frame and parameter nodes 2 Activities Karl F http://www.omg.org/issues/issue6141.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6141 Resolved In the Presentation Option section of Activity, p 280, seperate the title of the section from the title of the example section. Then add the following sentence to the Presentation Option section: The round-cornered border of Figure 201 may be replaced with the frame notation described in Appendix A. Activity parameter nodes are displayed on the frame. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6250: fig236 Datastore example/Datastore should not directly linked with actions Activities Jim O http://www.omg.org/issues/issue6250.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6250 Closed no change The pins are elided in the example. This notation is inherted from object nodes. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6358: Outgoing edges of initial nodes Activities Manfred K http://www.omg.org/issues/issue6358.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6358 Resolved In Constraint section of InitialNode, p 335, add this constraint: [2] Only control edges can have initial nodes as source. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6359: Guards on initial nodes Activities Conrad B http://www.omg.org/issues/issue6359.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6359 Resolved In Semantics section of initial nodes, p 335, in the first paragraph, in the next-to-last sentence, before "(see Activity)", add the words: ", for example by guards" **************************************************************************** ***************** **************************************************************************** ***************** Issue 6363: Guard evaluation Activities Conrad B http://www.omg.org/issues/issue6363.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6363 Resolved In the Semantics section of Decision Node, p 320, in the second paragraph, before the sentence beginning "For decision points", add the sentence: If the implementation can ensure that only one guard will succeed, it is not required to evaluate all guards when one is found that does. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6364: Decision behaviors on control tokens Activities Conrad B http://www.omg.org/issues/issue6364.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6364 Resolved In Constraint section of Decision Node, p 320, change the first two sentences of constraint [2] to: "A decision input behavior has zero or one input parameter and one output parameter. Any input parameter must be the same as or a supertype the type of object tokens coming along the incoming edge." In the Semantics section of Decision Node, p 320, last paragraph, change the first sentence to: If a decision input behavior is specified, then each data token is passed to the behavior before guards are evaluated on the outgoing edges. The behavior is invoked without input for control tokens. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6366: Clarify ReadSelfAction in activity behaviors Activities Conrad B http://www.omg.org/issues/issue6366.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6366 Resolved In Semantics section of ReadSelfAction, p 248, change the first sentence, before the hyphen to: Every action is part of some activity, as are behaviors invoked by actions or other elements of activities. Activities are optionally attached in some way to the specification of a classifier **************************************************************************** ***************** **************************************************************************** ***************** Issue 6369: Clarify join specs referencing control flow edges Activities Conrad B http://www.omg.org/issues/issue6369.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6369 **************************************************************************** ***************** **************************************************************************** ***************** Issue 6370: Clarify join rules Activities Conrad B http://www.omg.org/issues/issue6370.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6370 Closed no change The text is clear on this. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6361: Activity final clarification Activities Conrad B http://www.omg.org/issues/issue6361.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6361 Resolved In the Semantics section of ActivityFinalNode, p 298, in the first paragraph, add this to the next-to-last sentence: ", using the null token for object nodes that have nothing in them." **************************************************************************** ***************** **************************************************************************** ***************** Issue 6378: Questions about CentralBufferNode semantic Activities Conrad B http://www.omg.org/issues/issue6378.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6378 Resolved In the Examples section of CentralBufferNode, p 312, in the paragraph above Figure 230, change the last sentence to: All the parts that are not used will be packed as spares, and vice versa, because each token can only be drawn from the object node by one outgoing edge. The choice in this example is non-deterministic. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6400: UML 2 super / Activities / structured activity node contradiction Activities Conrad B http://www.omg.org/issues/issue6400.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6400 Closed no change Structured nodes are both nodes and groups, but this does not imply they are owned by more than one thing. Groups are owned optionally by activities or other groups. Nodes are owned optionally by activities, Structured nodes are inherit these possiblities, and extend nodes to be optionally owned by structured nodes. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6403: UML 2 Super / Activities / inconsistent naming Activities Conrad B http://www.omg.org/issues/issue6403.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6403 Duplicate This is duplicate with 6256. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6441: Integration between behavioral "sublanguages": Interactions and Activities Activities Conrad B http://www.omg.org/issues/issue6441.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6441 Defer This is more then we can do in the FTF. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6444: Activity diagram problems Activities Conrad B http://www.omg.org/issues/issue6444.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6444 Defer This is too vaguely stated to act on. Part of item a) in the issue is covered in 6348. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6486: Clarify termination of asynchronous invocations Activities Conrad B http://www.omg.org/issues/issue6486.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6486 In the Semantics section of ActivityFinalNode, p 298, in the first paragraph, add this after the first sentence: "Any behaviors invoked asynchronously by the activity are not affected." **************************************************************************** ***************** **************************************************************************** ***************** Issue 6506: concurrent vs. parallel ExpansionRegions Activities Conrad B http://www.omg.org/issues/issue6506.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6506 Duplicate Duplicate with 6099. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6510: AcitivityEdge: weight=all vs weight=null - UML2 Superstructure Activities Conrad B http://www.omg.org/issues/issue6510.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6510 Duplicate Duplicate with 6096. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6511: Token flow semantics: Implicit fork and join - UML2 Superstructure Activities Conrad B http://www.omg.org/issues/issue6511.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6511 Resolved A token can traverse only one edge coming out of an object node. To clarify, in the Semantics section of ObjectNode, p 350, add this sentence to the end of the first paragraph: "A token in an object node can traverse only one of the outgoing edges." **************************************************************************** ***************** **************************************************************************** ***************** Issue 6521: The node "Order cancel request" that appears in figure 6-86 Activities Conrad B http://www.omg.org/issues/issue6521.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6521 Closed no change The nodes "Ready to award bid" in Figure 213, and "Order Cancel Request" in Figure 260 are AcceptEventActions, p 217. The notation for object nodes with signal type is different, see Figure 275. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6522: Order cancel request Activities Conrad B http://www.omg.org/issues/issue6522.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6522 Closed no change This issue assumes that "Order Cancel Request" node in Figure 260 are object nodes. Is is actually an AcceptEventActions (see issue 6521). The Order Cancel Request node gets it token from an incoming signal. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6523: Typos Activities Conrad B http://www.omg.org/issues/issue6523.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6523 Duplicate The typos in this issue are duplicate with issue 6162. The questions are duplicate with issues 6521 and 6522. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6675: UML 2 Super/Activities/end naming consistency http://www.omg.org/issues/issue6675.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6675 Resolved In Figure 180, p 271, Figure 183, p 273, Figure 191, p 276, Figure 192, p 277, rename the association end "edgeContents" to "containedEdge" and "nodeContents" to "containedNode", including in the {redefines} constraints in Figures 183, 191, and 192. In Association section of ActivityGroup, p 301, replace "edgeContents" with "containedEdge" and "nodeContents" with "containedNode". **************************************************************************** ***************** **************************************************************************** ***************** Issue 6676: UML 2 Super/Activities/assocition end specialization consistency http://www.omg.org/issues/issue6676.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6676 Resolved In figure 180, p 271, add {union} constraint to the inGroup association ends from ActivityEdge and ActivityNode to ActivityGroup. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6677: UML 2 Super/Activities/invalid multiplicity 0 http://www.omg.org/issues/issue6677.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6677 Resolved In Figure 191, p 276, remove the "0" multiplicity from the edgeContents end from InterruptibleActivityRegion to ActivityEdge. In Constraints section of InterruptibleActivityRegion, p 337, add: [2] Interruptible regions cannot contain edges. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6678: UML 2 Super / Activities / inconsistency in representing subsetting http://www.omg.org/issues/issue6678.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6678 Resolved In Figure 191, p 276. rename association ends: - "interruptibleRegion" from ActivityNode to InterruptibleActivityRegion to "inInterruptibleRegion". - "interruptibleRegion" from ActivityEdge to InterruptibleActivityRegion to "interrupts". and remove entire "inGroup" association from ActivityEdge to InterruptibleActivityRegion. In Associations (CompleteActivties) section of ActivityEdge, p 293, replace "interruptibleRegion" with "interrupts". In Associations section of ActivityNode, replace "interruptibleRegion" with "inInterruptibleRegion". Rename "Associations" section heading of ActivityNode to "Associations (CompleteActivities)". **************************************************************************** ***************** **************************************************************************** ***************** Issue 6679: UML 2 Super / Activities / association end naming http://www.omg.org/issues/issue6679.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6679 Resolved See changes for 6678. **************************************************************************** ***************** **************************************************************************** ***************** Issue 6680: UML 2 Super / Activities / subsetting two properties http://www.omg.org/issues/issue6680.txt yourdirectory/uml2-superstructure-ftf.open.html#Issue6680 Resolved In Figure 192, p 277, make association end structuredNode from Activity to ActivityEdge derived. In Associations (StructuredActivities) section of Activity, put "/" before "structuredNode". **************************************************************************** ***************** -- _____________________________________________________________ Guus Ramackers Product Manager UML and Web Services Tools Oracle JDeveloper Tools group 520 Oracle Parkway, TVP Reading RG6 1RA, UK work: +44-(0)1189-245101 e-mail: guus.ramackers@oracle.com fax: +44-(0)1189-245148 OMG Issue No: 6677 Title: UML 2 Super/Activities/invalid multiplicity 0 Source: International Business Machines (Mr. Bran Selic, bselic@ca.ibm.com) Summary: InterruptibleActivityRegion::edgeContents redefines the multiplicity of ActivityGroup::edgeContents to be 0, which violates the constraint that an upper bound must be greater than 0 Discussion: The minimum multiplicity was set to zero because edges have no special semantics in interrupting regions, but consequently there is no effect of including them either. Remove the specialized association. In Figure 191, p 276, remove the association between InterruptibleActivityRegion to ActivityEdge. Disposition: Resolved e-mail: bselic@ca.ibm.com