-
Key: FUML13-19
-
Status: closed
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
This use of "new" is not defined or explained. It is not used in any of the normative references. Though I can guess what it means, it should be formally defined in for fUML to be a formal document.
If you are using "new" in some sort of Java way, the Java definition needs to be normative, or "new" needs to be defined explicitly.
-
Reported: FUML 1.2 — Thu, 28 Jul 2016 01:04 GMT
-
Disposition: Resolved — FUML 1.3
-
Disposition Summary:
Fix incorrect notation for unlimited natural values
The issue is referring to the notation new UnlimitedNatural(1) used as the default value for the attribute MultiplicityElement::upper in Figure 7.4 and new UnlimitedNatural(0) used as the default value for the attribute LiteralUnlimitedNatural::value in Figure 7.6. This is, indeed, not standard UML notation. The values should be changed to simply 1 and 0, respectively, in the two diagrams. (Note that the default values are already notated correctly in the class descriptions 7.2.2.2.22 MultiplicityElement and 7.2.2.2.21 LiteralUnlimitedNatural.)
-
Updated: Thu, 22 Jun 2017 16:38 GMT
FUML13 — The fUML spec uses "new" in diagrams and text in a specialized manner that is not defined.
- Key: FUML13-19
- OMG Task Force: fUML 1.3 RTF