-
Key: UML22-456
-
Legacy Issue Number: 12985
-
Status: closed
-
Source: Anonymous
-
Summary:
Could you please clarify what does the UML2 specifications intend for "provided port" and "required port"? Intuitively, it seems that a port could provide (respectively require) the interface which types it. This is in contradiction with the UML2 definition of port. Nevertheless, I belive a port should be able to require the interface tpeing it: the type of a port and its role (provide/require) should be decoupled. This is basically what the graphical front-end of Rhapsody does. It is also the same approach used for SysML ports, where direction is decoupled from the type of the port.
-
Reported: UML 2.1.2 — Thu, 23 Oct 2008 04:00 GMT
-
Disposition: Resolved — UML 2.2
-
Disposition Summary:
The idea of decoupling the type from the interface is addressed by 13080. The clarification is addressed here by the text revisions below.
-
Updated: Fri, 6 Mar 2015 20:58 GMT
UML22 — Could you please clarify what does the UML2 specifications intend for "provided port" and "required port"?
- Key: UML22-456
- OMG Task Force: UML 2.2 RTF