-
Key: UML25-195
-
Legacy Issue Number: 17587
-
Status: closed
-
Source: THALES ( Hugues Vincent)
-
Summary:
Title: Clarification on the semantics of ports in Encapsulated Classifiers
Where: section 11.3.2
Nature of Issue: Clarification
Severity of Issue: Minor
Full Description of the Issue:
Please specify clearly that the ConnectableElements connected by a same Connector must belong to the same StructuredClassifier: this made some issues in the past (UML4DDS).- The concept of 'side' of a port is not explained enough, depending if it is a port or a port on a part.
- "if there is a Connector attached to only one side of a Port, any requests arriving this Port will be lost" does it also stand for port which are not 'on a part'? Because in that case, the Port is an external boundary and a Connector may only be inside the Encapsulated Classifiers, may it not?
-
Reported: UML 2.4.1 — Thu, 13 Sep 2012 04:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
The first part of the issue is the same as 17586, and requires no changes because the constraint Connector::
roles covers it.
The second and third parts of this issue refer to the sentence “If there is a Connector attached to only one
side of a Port, any requests arriving at this Port will be lost.” It is quite right to say that at this point in the text
the concept of “side” of a Port is not well defined. But further, if there is a Connector attached to only one
side of a Port, then it may well be the case that the model is simply silent about what happens to requests:
there is no reason to say that they shall be lost. Indeed, most of the examples in this clause have Connectors
only attached to one side of a Port. Hence the sentence should be deleted, as it adds only confusion. -
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — Clarification on the semantics of ports in Encapsulated Classifiers
- Key: UML25-195
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF