Issue 19122: About prescribed port implementation (uml2-rtf)
Source: Airbus Group (Mr. Yves Bernard, yves.bernard(at)airbus.com)
Nature: Uncategorized Issue
Severity: 
Summary: Description:

The prescription made in the §11.3.3 about the implementation of Port seems to be overly restrictive:  

“When an instance of an EncapsulatedClassifier is created, instances corresponding to each of its Ports are created and held in the slots specified by each Port, in accordance with its type and multiplicity. These instances are referred to as “interaction points” and provide unique references.”

 

As long as port is defined as “a distinct interaction point”, of which the primary purpose is: “enabling different communications to be distinguished based on the Port through which they occur”, the implementation described by the text quoted above, and which based on the instantiation of a separate object, is actually a possible implementation but it is not the only one.

 

An alternative valuable implementation is to make them pure routing information that does not required any structural part instance (cf. SDL port semantics). UML should not prevent implementations of that kind.

 


Resolution: 
Revised Text: 
Actions taken:
November 22, 2013: received issue
Discussion: 

End of Annotations:=====

m: "BERNARD, Yves" <Yves.Bernard@airbus.com>
To: "issues@omg.org" <issues@omg.org>
Date: Fri, 22 Nov 2013 17:27:47 +0100
Subject: About prescribed port implementation
Thread-Topic: About prescribed port implementation
Thread-Index: Ac7nla3BjEidh7K5R169r7vuE1BrYg==
Accept-Language: fr-FR, en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR, en-US
X-Virus-Scanned: amavisd-new at omg.org


Hi Juergen,

 

Would you creat the following issue for UML, please?

 

Description:

The prescription made in the §11.3.3 about the implementation of Port seems to be overly restrictive:  

.When an instance of an EncapsulatedClassifier is created, instances corresponding to each of its Ports are created and held in the slots specified by each Port, in accordance with its type and multiplicity. These instances are referred to as .interaction points. and provide unique references..

 

As long as port is defined as .a distinct interaction point., of which the primary purpose is: .enabling different communications to be distinguished based on the Port through which they occur., the implementation described by the text quoted above, and which based on the instantiation of a separate object, is actually a possible implementation but it is not the only one.

 

An alternative valuable implementation is to make them pure routing information that does not required any structural part instance (cf. SDL port semantics). UML should not prevent implementations of that kind.

 

Thanks,

 

Yves

 

The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.