-
Key: UML14-133
-
Legacy Issue Number: 5976
-
Status: closed
-
Source: Google ( Don Baisley)
-
Summary:
UML's use of the word "unique" for multiplicity is ambiguous. It means
{unique}
"distinct", but it could be mistaken to mean "unique across all instances".
For example, if someone says that the employee-number attribute of employee
is unique, it would likely be understood to mean that each employee has an
employee-number that is different from every other employee. But that's not
what UML defines "unique" to mean. I recommend that the FTF change
"" to "
{distinct}" or "
{set}".
-
Reported: UML 1.5 — Thu, 19 Jun 2003 04:00 GMT
-
Disposition: Resolved — UML 1.4.2
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
UML14 — UML's use of the word "unique" for multiplicity is ambiguous
- Key: UML14-133
- OMG Task Force: UML 1.4 RTF