-
Key: UMLR-239
-
Legacy Issue Number: 15763
-
Status: open
-
Source: Oracle ( Antonio Petri)
-
Summary:
There isn't a constraint that prevents multiple associations from being specified between the same Actor and Use Case. Multiplicity is handled already by the multiplicity at the association's ends, so having two or more different associations seems to be redundant.
-
Reported: UML 2.3b1 — Tue, 19 Oct 2010 04:00 GMT
-
Updated: Fri, 6 Mar 2015 20:57 GMT