-
Key: UML25-431
-
Legacy Issue Number: 18072
-
Status: closed
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
Please explain the multiplicity as used on this Figure 18-2. Without a good explanation, an example doesn’t really help
Something like this.
In this example, a Customer or Administrator may or may not participate in any of their associated Use Cases (hence the 0..1 multiplicity). From the Use Case perspective, it must have an Actor to initiate it (hence the 1 multiplicity). The Deposit and Register ATM use cases require participation by the Bank, while the bank can participate with many Deposit and Register ATM use cases at the same time.This description will address open UML 2.4 issue 8854
-
Reported: UML 2.4.1 — Fri, 28 Sep 2012 04:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
Accept the proposal. This also resolves issue 8854
-
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — Location: 18.1.5 Examples Figure 18-2. 689 - Explain about multiplicity
- Key: UML25-431
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF