Issue 8495: Add constraints on ConditionalNode (uml2-rtf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Clarification
Severity: Minor
Summary: Add constraints on ConditionalNode to ensure the test and body are owned by the conditional node (or have them owned by the clause with body outputs being referred to by a single clause. This would prevent sharing bodies across clauses It is unclear if this is much of a benefit, since changing the body of one clause will change another, which may not be the intention.). 

Resolution: Agreed that nodes in the test and body part of the clauses of a conditional node must be owned by the conditional node and that these parts should be disjoint.
Revised Text: In Section 12.3.17 (Clause), under Constraints (Package StructuredActivities) add:
	[2] The test and body parts must be disjoint.
In Section 12.3.18 (ConditionalNode), under Constraints, before the existing constraint, add:
Package StructuredActivities
[1] The union of the ExecutabledNodes in the test and body parts of all clauses must be the same as the subset of nodes contained in the ConditionalNode (considered as a StructuredActivityNode) that are ExecutableNodes.
[2] No ExecutableNode may appear in the test or body part of more than one clause of a conditional node.
Package CompleteStructuredActivities

Actions taken:
March 6, 2005: received issue
Discussion: 
Disposition:	Deferred to UML 2.4 RTF
End of Annotations:=====

m: webmaster@omg.org 
Date: 06 Mar 2005 10:21:59 -0500 
To: <issues@omg.org> 
Subject: Issue/Bug Report 



--------------------------------------------------------------------------------

Name: Conrad Bock
Company: NIST
mailFrom: conrad.bock@nist.gov
Notification: No
Specification: UML 2 Superstructure
Section: Activities
FormalNumber: ptc/04-10-02
Version: 
RevisionDate: 
Page: 
Nature: Clarification
Severity: Minor
HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)
Description
Add constraints on ConditionalNode to ensure the test and body are owned by the conditional node (or have them owned by the clause with body outputs being referred to by a single clause. This would prevent sharing bodies across clauses It is unclear if this is much of a benefit, since changing the body of one clause will change another, which may not be the intention.). 

Subject: Proposed issue resolutions, Set 2: Activities -- Low and trivial effort changes
Date: Sun, 1 Feb 2009 23:25:51 -0500
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Proposed issue resolutions, Set 2: Activities -- Low and trivial effort changes
thread-index: AcmE7lQ9kq9LsV5zRgKwNovhcAlo8A==
From: "Ed Seidewitz" <ed-s@modeldriven.com>
To: <uml2-rtf@omg.org>


Attached are proposed resolutions to 21 additional Activity issues that only required low or trivial effort changes (though there are a few that, on further analysis, I decided to propose to close or identified as duplicate).

 

-- Ed



 UML 2.3 Resolutions 090201 Seidewitz 2.doc 

OMG Issue No:  8495
Title:	Add constraints on ConditionalNode
Source:
NIST (Mr. Conrad Bock, conrad.bock@nist.gov conradb@nist.gov)
Summary:
Add constraints on ConditionalNode to ensure the test and body are owned by the conditional node (or have them owned by the clause with body outputs being referred to by a single clause. This would prevent sharing bodies across clauses It is unclear if this is much of a benefit, since changing the body of one clause will change another, which may not be the intention.).
Resolution:
Agreed that nodes in the test and body part of the clauses of a conditional node must be owned by the conditional node and that these parts should be disjoint.
Revised Text:
In Section 12.3.17 (Clause), under Constraints (Package StructuredActivities) add:
	[2] The test and body parts must be disjoint.
In Section 12.3.18 (ConditionalNode), under Constraints, before the existing constraint, add:
Package StructuredActivities
[1] The ExecutabledNodes in the test and body parts of each clause must be nodes contained in the ConditionalNode (considered as a StructuredActivityNode).
[2] No ExecutableNode may appear in the test or body part of more than one clause of a conditional node.
Package CompleteStructuredActivities
Disposition:	Resolved