-
Key: UML22-355
-
Legacy Issue Number: 11646
-
Status: closed
-
Source: The MathWorks ( Mr. Alan Moore)
-
Summary:
StructuredActivityNode, based on both common sense and its semantics, requires input and output pins. However StructuredActivityNode::input and StructuredActivityNode::output, both inherited from Action are derived unions and so cannot be used directly. StructuredActivityNode::result is a concrete property but has a special meaning.
What is needed is some solution that subsets StructuredActivityNode::input and StructuredActivityNode::output but can be used to describe input and output pins of StructuredActivityNode.
-
Reported: UML 2.1.2 — Thu, 8 Nov 2007 05:00 GMT
-
Disposition: Resolved — UML 2.2
-
Disposition Summary:
The semantics of StructuredActivityNode does, indeed, talk specifically about pins on such nodes. Further, having pins on StructuredActivityNodes is assumed as being allowed in and is required by the Java to UML activity model mapping in the Foundational UML specification. The submitter is correct, however, that the abstract syntax model itself does not seem to explicitly support this.
-
Updated: Fri, 6 Mar 2015 20:58 GMT