-
Key: UML25-602
-
Legacy Issue Number: 7777
-
Status: closed
-
Source: NIST ( Mr. Conrad Bock)
-
Summary:
The caption of Figure 63 of the FAS (Figure 56 of the 040814 PDF) shows
an association between example interfaces IAlarm, ISensor, and has this
caption:IAlarm is the required interface for any classifier implementing
Isensor; conversely, Isensor is the required interface for any
classifier implementing IAlarm.The text description says:
A set of interfaces constituting a protocol may be depicted as
interfaces with associations between themIs this just notation, or are associations really in the model?
- If it is just notation, what is the model?
- If it is the model, isn't it overly restrictive? The modeler's
intention might be that these are both required interfaces,
declaring that the two support classes will include an association
between them. I thought interface were extended in UML 2 to include
associations generally.
-
Reported: UML 1.4.2 — Fri, 27 Aug 2004 04:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
Discussion
This issue has already been resolved by, or no longer applies to, the UML 2.5 Beta 1 specification.
Disposition: Closed - No Change -
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — Associations between interfaces
- Key: UML25-602
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF