Legacy Issue Number: 15399
Source: NASA ( Maged Elaasar)
Since the "isUnique" and "isOrdered" properties have default values, do we need to have both 'unique'/'nonunique' and 'ordered'/'unordered' textual annotations? or do we only need ones for non-default values?
I noticed that in some presentation option sections in the spec both annotation values are mentioned, while in other sections only one value is mentioned (diagrams in the spec also use them inconsistently):
7.3.3 Association has 'nonunique' and 'ordered <= This seems to be the most correct
7.3.32 MultiplicityElement has 'unique'/'nonunique' and 'ordered'/'unordered'
7.3.36 Operation has 'unique' and 'ordered'
7.3.44 Property have 'unique'/ 'nonunique' and 'ordered'
9.12.1 MultiplicityElement has 'unique'/'nonunique' and 'ordered'/'unordered'
11.8.2 Operation has 'unique' and 'ordered'
11.3.5 Property have 'unique' and 'ordered'
What made me notice that is the addition of 'id' by resolution 15369, do we need to log an issue to fix this later?
Reported: UML 2.3 — Thu, 5 Aug 2010 04:00 GMT
Disposition: Resolved — UML 2.4
The inconsistency is still there as specified in the issue. The general notation is defined in MultiplicityElement.
It does have to be repeated for Property because the syntax allows the insertion of ‘=’ <default>
between the multiplicity and prop-modifiers, and for Operation because the <oper-property> can be intermingled
with others. The ‘sequence’ option is present for Property but inconsistently absent for Operation.
The <parm-property> term is currently undefined and needs to have the same options.
Updated: Fri, 6 Mar 2015 20:58 GMT