UML25 — UML 2 Super/Interfaces

03-08-02 Figure 63 - firstly there ar a couple of typoes. The interface
stereotype on IAlarm is missing <<, and sensor should be ISensor. More
serious are the implications of the caption - "IAlarm is the required
interface for any classifier implementing Isensor;
conversely, Isensor is the required interface for any classifier
implementing
IAlarm."

To me the caption sounds wrong but at the very least more explanation is
needed. Firstly, does having the association to the interface imply that a
usage dependency is required to ISensor from any class that implements
IAlarm? If so a constraint is needed to enforce that. Secondly, isn't such a
usage dependency redundant, given that its existence is implied from the
presence of the association?

Discussion
This issue has already been resolved by, or no longer applies to, the UML 2.5 Beta 1 specification.
Disposition: Closed - No Change