-
Key: UML22-36
-
Legacy Issue Number: 7247
-
Status: closed
-
Source: PostFinance ( Karl Guggisberg)
-
Summary:
Connector - "provided Port" and "required Port" not defined Constraint 1, "[1] A delegation connector must only be defined between used Interfaces or Ports of the same kind, e.g. between two provided Ports or between two required Ports." uses the concepts "provided Port" and "required Port". Neither of them is defined in the spec. Furthermore, a Connector is not expected to be defined between Interfaces, but an Association is. A Connector is defined between ConnectableElements whose specializations are Property, Port, Parameter, and Variable, but not Interface. I suggest to replace Constraint [1] with "[1] A delegation connector must only be defined between a ConnectableElement (i.e. a Port) of the component and a ConnectableElement (i.e. a Property or a Port) of one of its internal parts."
-
Reported: UML 2.0 — Thu, 15 Apr 2004 04:00 GMT
-
Disposition: Resolved — UML 2.2
-
Disposition Summary:
The proposed resolution is still incorrect because a connector in general is n-ary not binary. Also the need for such a constraint is altered because of the resolution of 7364 which makes Connector::kind derived. Instead we need a constraint that ensures that a delegation connector only delegates from one port: it would make no sense to have an n-ary connector that delegated from more than one port. Furthermore the entire Semantics section for Connector in this chapter needs rewriting because of this issue.
-
Updated: Fri, 6 Mar 2015 20:58 GMT
UML22 — Connector - "provided Port" and "required Port" not defined Constraint 1
- Key: UML22-36
- OMG Task Force: UML 2.2 RTF