Issue 14561: Attributes introduced in CompleteActivities should not be included in the fUML subset (fuml-ftf) Source: Model Driven Solutions (Mr. Ed Seidewitz, ed-s(at)modeldriven.com) Nature: Uncategorized Issue Severity: Summary: Specification: Semantics of a Foundational Subset for Executable UML Models (ptc/2008-11-03) Subclause: 7.4 Activities In Subclause 7.4.1, it says that “The UML 2 Superstructure package CompleteActivities is excluded in its entirety from fUML”. However, there are several Activities metaclasses in the fUML subset that currently include attributes that are only introduced in CompleteActivities. These are: Activity::isSingleExecution ObjectFlow::isMulticast ObjectFlow::isMultiReceive ObjectNode::ordering ObjectNode::isControlType Pin::isControl JoinNode::isCombineDuplicate Parameter::isException Parameter::isStream Parameter::effect These attributes should be removed from the fUML abstract syntax, along with any constraints that currently reference them. Note that metaclass properties that are the ends of associations introduced in CompleteActivities have already been excluded from the fUML subset. Resolution: Agreed. This is consistent with exclusions made in other areas of the fUML subset. In addition, once the attributes ObjectNode::ordering and Parameter::effect are removed, it is no longer necessary to include the enumerations ObjectNodeOrderingKind and ParameterEffectKind in the fUML subset. Revised Text: In Subclause 7.2.2.2.26 Parameter, under Attributes, remove the entries for "isException", "isStream" and "effect". Remove constraint [1] no_exceptions_no_streaming_in_fUML. In Subclause 7.4.2.2.1 Activity, under Attributes, remove the entry for "isSingleExecution". Remove constraint [1] fUML_single_execution. In Subclause 7.4.2.2.12 JoinNode, under Attributes, remove the entry for "isCombineDuplicate" and replace it with "None". In Subclause 7.4.2.2.14 ObjectFlow, under Attributes, remove both entries and replace them with "None". Remove constraint [1] no_multicast_or_receive. In Subclause 7.4.2.2.15 ObjectNode, under Attributes, remove both entries and replace them with "None". Remove constraint [1] fifo_ordering_no_control. In Subclause 7.5.2.2.8 Pin, under Attributes, remove both entries and replace them with "None". (Note that the entry for "multiplicityElement" is spurious.) Remove constraint [1] isControl_fUML. Also remove the relevant attributes and constraint documentation from the diagrams shown in Figure 20 – Features, Figure 31 – Nodes, Figure 33 – Control Nodes, Figure 34 – Flows and Figure 39 – Basic Pins. Remove ObjectNodeOrderingKind from Figure 31 and ParameterEffectKind from Figure 20. Actions taken: October 14, 2009: received issue July 23, 2010: closed issue Discussion: End of Annotations:===== ubject: Attributes introduced in CompleteActivities should not be included in the fUML subset Date: Wed, 14 Oct 2009 15:11:08 -0400 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Attributes introduced in CompleteActivities should not be included in the fUML subset thread-index: AcpNAhXxGAsTn440TFqu7g1sg0GQnQ== From: "Ed Seidewitz" To: Specification: Semantics of a Foundational Subset for Executable UML Models (ptc/2008-11-03) Subclause: 7.4 Activities In Subclause 7.4.1, it says that .The UML 2 Superstructure package CompleteActivities is excluded in its entirety from fUML.. However, there are several Activities metaclasses in the fUML subset that currently include attributes that are only introduced in CompleteActivities. These are: Activity::isSingleExecution ObjectFlow::isMulticast ObjectFlow::isMultiReceive ObjectNode::ordering ObjectNode::isControlType Pin::isControl JoinNode::isCombineDuplicate Parameter::isException Parameter::isStream Parameter::effect These attributes should be removed from the fUML abstract syntax, along with any constraints that currently reference them. Note that metaclass properties that are the ends of associations introduced in CompleteActivities have already been excluded from the fUML subset.