Issue 14962: loopVariable ownership (uml2-rtf)
Source: Model Driven Solutions (Mr. Ed Seidewitz, ed-s(at)modeldriven.com)
Nature: Uncategorized Issue
Severity: 
Summary: Specification: OMG UML Superstructure, Version 2.3 (ptc/2009-09-09)

Subclause: 12.3.35 LoopNode

 

The loopVariables of a LoopNode are OutputNodes, but they are not part of the outputs of the LoopNode. Therefore, they need to be independently owned by the LoopNode.

 

The propery LoopNode::loopVariable should subset Element::ownedElement, and the association should be shown as composite on Figure 12.22. Otherwise the mustBeOwned constraint will be violated for loopVariables.

 

 

Resolution: 
Revised Text: 
Actions taken:
January 12, 2010: received issue
Discussion: 

End of Annotations:=====
ubject: loopVariable ownership
Date: Tue, 12 Jan 2010 17:55:54 -0500
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: loopVariable ownership
thread-index: AcqT2mVDmWnW3xVASzegh8WH6KZPPA==
From: "Ed Seidewitz" <ed-s@modeldriven.com>
To: <issue@omg.org>


Specification: OMG UML Superstructure, Version 2.3 (ptc/2009-09-09)

Subclause: 12.3.35 LoopNode

 

The loopVariables of a LoopNode are OutputNodes, but they are not part of the outputs of the LoopNode. Therefore, they need to be independently owned by the LoopNode.

 

The propery LoopNode::loopVariable should subset Element::ownedElement, and the association should be shown as composite on Figure 12.22. Otherwise the mustBeOwned constraint will be violated for loopVariables.