Issue 18716: UML 2.5 issue. AssociationClasses should have isUnique property (uml25-ftf)
Source: Microsoft (Mr. Steve Cook, stcook(at)microsoft.com)
Nature: Uncategorized Issue
Severity: 
Summary: Dragan Milicev’s paper at http://afrodita.rcub.bg.ac.rs/~dmilicev/pubs/mdd/trumlassoc.zip points out that AssociationClasses can be multiply instantiated between the same set of end instances, even when all the ends are marked as unique.  He proposes adding an isUnique property to AssociationClass to distinguish between circumstances where this is allowed and those where it is not.

Resolution: 
Revised Text: 
Actions taken:
May 15, 2013: received issue
Discussion: 

End of Annotations:=====

m: Steve Cook <Steve.Cook@microsoft.com>
To: "issues@omg.org" <issues@omg.org>
Subject: UML 2.5 issue. AssociationClasses should have isUnique property
Thread-Topic: UML 2.5 issue. AssociationClasses should have isUnique property
Thread-Index: Ac5RU3nLJik9ILgOR7SkFVnsAPjpTg==
Date: Wed, 15 May 2013 10:06:21 +0000
Accept-Language: en-GB, en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.166.18.100]
X-Forefront-Antispam-Report: 
 CIP:131.107.125.37;CTRY:US;IPV:CAL;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(199002)(189002)(16406001)(16297215003)(44976003)(512954002)(33656001)(74502001)(81342001)(55846006)(76482001)(81542001)(47446002)(16236675002)(15202345002)(54356001)(65816001)(8558605002)(56776001)(77982001)(59766001)(80022001)(74366001)(20776003)(53806001)(74662001)(31966008)(74706001)(56816002)(51856001)(47976001)(47736001)(74876001)(50986001)(4396001)(54316002)(6806003)(79102001)(49866001)(46102001)(69226001)(71186001)(63696002);DIR:OUT;SFP:;SCL:1;SRVR:BY2FFO11HUB023;H:TK5EX14HUBC105.redmond.corp.microsoft.com;RD:InfoDomainNonexistent;A:1;MX:1;LANG:en;
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 08476BC6EF
X-Virus-Scanned: amavisd-new at omg.org


Dragan Milicev.s paper at http://afrodita.rcub.bg.ac.rs/~dmilicev/pubs/mdd/trumlassoc.zip points out that AssociationClasses can be multiply instantiated between the same set of end instances, even when all the ends are marked as unique.  He proposes adding an isUnique property to AssociationClass to distinguish between circumstances where this is allowed and those where it is not.