Issue 15004: Diagram graphics in the fUML specification (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, v1.0 Beta 2 (ptc/2009-10-05)



All the abstract syntax diagrams in the spec should:

 

1. Use the “dot notation” to show which association ends are owned by classes rather than by the associations. Even though the fUML subset diagrams follow the same convention as in the UML Superstructure spec that all navigable ends are class owned and all non-navigable ends are association owned, it is still better make this explicitly clear. This is especially so for fUML, since, when  the abstract syntax interpreted as an fUML model itself when referenced from the execution model, the navigable ends are a always accessed as class-owned structural features and the associations themselves are ignored (since they don’t meet the fUML constraint of owning all their ends).

 

2. Show subsetting and redefinition annotations, consistent (for the fUML subset) with the similar annotations in the UML superstructure abstract syntax. Even though subsetting and redefinition are not in the fUML feature subset, the fUML abstract syntax model is supposed to itself be a proper subset of the UML abstract syntax model and, therefore, needs to include subsetting and redefinition consistent with the full model. Indeed, these relationships are in the fUML abstract syntax model as serialized in the normative XMI, they are just currently not shown on the diagrams. (Note also that Subclause 8.1 discusses the conventions on derivation and redefinition for fUML.)




Resolution: Agreed. see pages 50  - 66 of OMG document ptc/2010-03-12 for details
Revised Text: Replace the abstract syntax figures in Clause 7 as indicated below.
 
Figure 14 - Root
 
Figure 15 - Multiplicities
 
Figure 16 - Namespaces
 
Figure 17 - Expressions
 
Figure 18 - Instances
 
Figure 19 - Classifiers
 
Figure 20 - Features
 
Figure 21 - Operations
 
Figure 22 - Classes
 
Figure 23 - Data Types
 
Figure 24 - Packages
 
Figure 26 - Common Behavior
 
Figure 27 - Reception
 
Figure 28 - Triggers
 
Figure 29 - Events
 
Figure 31 - Nodes
 
Figure 32 - Object Nodes
 
Figure 33 - Control Nodes
 
Figure 34 - Flows
 
Figure 35 - Structured Nodes
 
Figure 36 - Expansion Regions
 
Figure 38 - Basic Actions
 
Figure 39 - Basic Pins
 
Figure 40 - Basic Invocation Actions
 
Figure 41 - Object Actions
 
Figure 42 - Structural Feature Actions
 
Figure 43 - Link Identification
 
Figure 44 - Read Link Actions
 
Figure 45 - Write Link Actions
 
Figure 46 - Accept Event Actions
 
Figure 47 - Object Lifecycle Actions
 
Figure 48 - Reduce Actions

Actions taken:
January 22, 2010: received issue
July 23, 2010: closed issue
Discussion: 

End of Annotations:=====
ubject: Diagram graphics in the fUML specification
Date: Fri, 22 Jan 2010 15:57:14 -0500
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Diagram graphics in the fUML specification
thread-index: AcqbpXlyXbDW14MNRbSKQOJouFXG/g==
From: "Ed Seidewitz" <ed-s@modeldriven.com>
To: <issues@omg.org>


Specification: Semantics of a Foundational Subset for Executable UML Models, v1.0 Beta 2 (ptc/2009-10-05)



All the abstract syntax diagrams in the spec should:

 

1. Use the .dot notation. to show which association ends are owned by classes rather than by the associations. Even though the fUML subset diagrams follow the same convention as in the UML Superstructure spec that all navigable ends are class owned and all non-navigable ends are association owned, it is still better make this explicitly clear. This is especially so for fUML, since, when  the abstract syntax interpreted as an fUML model itself when referenced from the execution model, the navigable ends are a always accessed as class-owned structural features and the associations themselves are ignored (since they don.t meet the fUML constraint of owning all their ends).

 

2. Show subsetting and redefinition annotations, consistent (for the fUML subset) with the similar annotations in the UML superstructure abstract syntax. Even though subsetting and redefinition are not in the fUML feature subset, the fUML abstract syntax model is supposed to itself be a proper subset of the UML abstract syntax model and, therefore, needs to include subsetting and redefinition consistent with the full model. Indeed, these relationships are in the fUML abstract syntax model as serialized in the normative XMI, they are just currently not shown on the diagrams. (Note also that Subclause 8.1 discusses the conventions on derivation and redefinition for fUML.)