A port belongs to exactly one Software Component (SW-C) and is the interaction point between a SW-C and other SW-Cs. The interaction between specific ports of specific components is modeled using connectors. A port can either be a Provide Port (p-port, PPort) or a Require Port (r-port, RPort). A port of a SW-C is associated with a port-interface.

The occurrence of an unconnected port is not per se a design mistake. It can be valid when an application provider for the data element is absent and the default init value is good enough to operate with or it could be that an end point was removed from the system because it is subjected to variability (See Variant Handling).

Ports are the interconnection points between software components. Ports of different SWC can be connected to indicate a data flow between them. The details, i.e. the kind of information that is actually transported between the ports, are defined by port-interfaces.

A port is a part of a software component that is an interaction point between that component and other software components. The interaction between ports is modeled via interfaces.


Port Types

Provide Port

Specific Port providing data or providing a service of a server as defined in the Port Interface. The Provide Port is sometimes abbreviated as PPort or P-Port.

Require Port

Specific Port requiring data or requiring a service of a server as defined in the Port Interface. The Require Port is sometimes abbreviated as RPort or R-Port.

Unconnected Ports

Unconnected Sender Ports

Data of the sender will not appear on VFB. Generated RTE might simply call empty function or even optimize function call to zero code.

Unconnected Synchronous Receiver Ports

The RPort will always read the initial value specified for this RPort.

Unconnected Asynchronous Receiver Ports

The RPort will receive a time-out like the Sender is not providing data.

Unconnected Server Ports

The operations (functions) of the PPort interface will never be called. Generated RTE (or finally the compiler) might even optimize operation to zero code.

Unconnected Client Ports

According to AUTOSAR specification the operations (functions) on the RPort will TIME_OUT. But more likely the RTE-Generator will generate a return code RTE_E_UNCONNECTED for any unconnected client interface operation.

Initial (default) values of a port