UCM11 — Connectable interfaces does not support more that one portelement per port-type

Port-type can have 1..* PortElements, as clearly shown in Figure 9.22.
So a component can provide and require a set of PortElementObjects as instances of couple PortName/PortElementName and this is correctly mapped in the component Port Mapping getter for provided portelement “get_<port_name>_<provided_port_element_name>".

When looking for REQUIRED port elements and the interface to connect them to the related provided port element object, this Port/PortElement coupling seems lost.

Infact:

• ComponentObject::get_portElement (in string provided)
• Connectable::on_connect (in string port_name, in PortElementObject required);
• Connectable::on_disconnect (in string port_name);
• Container::get_port_element (in componentId comp_instance, in string port_name)
• Container::connect (in componentId instance, in string port_name, in PortElementObject to_port)
  support only one PortElementObject for Port.

If the understanding of the UCM is correct they should be updated as

• ComponentObject::get_portElement (in string port_name, in string port_element_name);
• Connectable::on_connect (in string port_name, in string port_element_name, in PortElementObject required);
• Connectable::on_disconnect (in string port_name, in string port_element_name);
• Container::get_port_element (in componentId comp_instance, in string port_name, in string port_element_name);
• Container::connect (in componentId instance, in string port_name, in string port_element_name, in PortElementObject to_port);

update the programming model to explicitly manipulate port elements

In the programming model APIs, replace parameter “port_name” by two parameters “port_or_policy” and “port_elem”.

Document ptc/17-05-05 shall be replaced by file ucm.idl.