The abstract metaclass FunctionType abstracts the function component types that are used to model the functional structure, which is distinguished from the implementation of component types using AUTOSAR. The syntax of FunctionTypes is inspired from the concept of Block from SysML.<br/><br/>FunctionBehavior and FunctionTrigger in the Behavior package are associated to a FunctionType.<br/><br/><br/>Semantics:<br/>The FunctionType abstracts the function component types that are used to model the functional structure on AnalysisLevel and DesignLevel.<br/>Leaf functions of an EAST-ADL function hierarchy are called elementary Functions.<br/>Elementary Functions have synchronous execution semantics:<br/>1. Read inputs<br/>2. Execute (duration: Execution time)<br/>3. Write outputs<br/>Execution is defined by a behavior that acts as a transfer function.<br/>Subclasses of the abstract class FunctionType add their own semantics.<br/><br/>If a behavior is attached to the FunctionType, the execution semantic for a discrete elementary FunctionType complies with the run-to-completion semantic. This has the following implications:<br/><br/>1. Input that arrives at the input FunctionPorts after execution begins will be ignored until the next execution cycle.<br/><br/>2. If more than one input value arrives per FunctionPort before execution begins, the last value will override all previous ones in the public part of the input FunctionPort (single element buffers for input).<br/><br/>3. The local part of a FunctionPort does not change its value during execution of the behavior.<br/><br/>4. During an execution cycle, only one output value can be sent per FunctionPort. If consecutive output values are produced on the same FunctionPort during a single execution cycle, the last value will override all previous ones on the output FunctionPort (single element buffers for output).<br/><br/>5. Output will not be available at an output FunctionPort before execution ends.<br/><br/>6. Elementary FunctionTypes may not produce any side effects (i.e., all data passes the FunctionPorts).<br/><br/><br/>Constraints:<br/>[1] Elementary FunctionTypes shall not have parts.<br/><br/><br/>Notation:<br/>The FunctionType is shown as a solid-outline rectangle containing the name, with its FunctionPorts or PortGroups on the perimeter. Contained entities may be shown with their FunctionConnectors (White-box view).<br/><br/><br/>Extension: UML Class, specialization of SysML::Block<br/>
