FunctionConnector : public <<atpStructureElement>> class
Created: |
2006-08-29 16:51:27 |
Modified: |
2010-06-02 14:21:08 |
|
Project: |
|
Author: |
|
Version: |
1.0 |
Phase: |
1.0 |
Status: |
Proposed |
Complexity: |
Easy |
Advanced: |
|
UUID: |
{48EF76B0-7C42-4534-A8AC-5CC55844C363} |
Appears In: |
FunctionModeling, FunctionConnector |
<p>The FunctionConnector indicates that the connected FunctionPorts exchange signals or client-server requests/responses.<br/></p><p><br/></p><p>Semantics:<br/></p><p>The FunctionConnector connects a pair of FunctionFlowPorts or FunctionClientServerPorts. If two FunctionFlowPorts are connected, data elements of the type of the output FunctionFlowPort flow from the output FunctionFlowPort to the input FunctionFlowPort. If FunctionClientServerPorts are connected, the client calls the server according to the operations of the interfaces. The occurrence of the FunctionType that specifies the occurrence of the FunctionPrototype has to be identified by the FunctionConnector as well.<br/></p><p>The FunctionConnector is normally routed according to the hardware topology and the allocation of source and destination. If there are redundant paths, a FunctionAllocation may be used to prescribe allocation.<br/></p><p><br/></p><p><br/></p><p>Constraints:<br/></p><p>[1] Can connect two FunctionFlowPorts of different directions when this is an assembly FunctionConnector.<br/></p><p><br/></p><p>[2] Can connect two FunctionFlowPorts of the same direction when this is a delegation FunctionConnector.<br/></p><p><br/></p><p>[3] Can connect two ClientServerPorts of different kinds when this is an assembly FunctionConnector.<br/></p><p><br/></p><p>[4] Can connect two ClientServerPorts of the same kind when this is a delegation FunctionConnector.<br/></p><p><br/></p><p>[5] Can connect two FunctionFlowPorts with direction inout.<br/></p><p><br/></p><p>Notation: FunctionConnector is shown as a solid line<br/></p><p><br/></p><p>Extension: UML Connector<br/></p>
- Associations From
- Other Links