FunctionModeling::FunctionFlowPort

Header Image
Content:
FunctionFlowPort : Public Class FunctionPort, EventFunctionFlowPort, FunctionEvents
The FunctionFlowPort is a metaclass for flowports, inspired by the SysML FlowPort.<br/><br/>Semantics:<br/>FunctionFlowPorts are single buffer overwrite and nonconsumable.<br/><br/>FunctionFlowPorts can be connected if their FunctionPort signatures match; i.e.:<br/><br/>EADatatypes that are RangeableValueTypes or EANumericals are compatible if<br/>* They have the same Quantity <br/>* They have the same Unit.<br/>* The source has a max that is the same or smaller than the destination<br/>* The source has a min that is the same or larger than the destination<br/><br/>EADatatypes that are RangeableValueTypes are compatible if<br/>* The source has accuracy value that is smaller than the destination<br/>* The source has resolution value that is smaller than the destination<br/>* The source has more significant digits than the destination<br/><br/>EADatatypes that are Enumerations are compatible if<br/>* The source Enumeration has EnumerationLiterals that are a subset of the destination Enumeration's EnumerationLiterals.<br/><br/>A FunctionFlowPort with direction=in is called an input FunctionFlowPort:<br/>The input FunctionFlowPort indicates that the containing Function requires input data. The type of this data is defined by the associated EADatatype. The data is sampled at the invocation of the containing entity for discrete Functions. For continuous Functions, the input FunctionFlowPort represents a continuous input connection point.<br/>The input FunctionFlowPort declares a reception point of data. It represents a single element buffer, which is overridden with the latest data. The type of the data is defined by the associated EADatatype.<br/><br/>A FunctionFlowPort with direction=out is called an output FunctionFlowPort:<br/>The output FunctionFlowPort indicates that the containing Function provides output data. The type of this data is defined by the associated EADatatype. The data is sent at the completion of the containing entity for discrete Functions. For continuous Functions, the output FunctionFlowPort represents a (time-)continuous output connection point.<br/><br/>The output FunctionFlowPort declares a transmission point of data. The type of the data is defined by the associated EADatatype.<br/><br/>A FunctionFlowPort with direction=inout is called an input/output FunctionFlowPort: Its semantics is the union of both the input and output FunctionFlowPort, described above.<br/><br/>Extension: UML Port, specialization of SysML::FlowPort<br/>
  • Attributes
  • Associations
  • Associations From
  • Advanced
  • Other Links
Attribute Scope Type
direction Public EADirectionKind
 
Element Source Role Target Role
«atpType» EADatatype
Class «isOfType»
Name:  
 
Name: type
The single EADatatype for this port.
Details:
 
Element Source Role Target Role
«atpPrototype» EAValue
Class  
Name: defaultValue
 
Name:  
 
Details:
 
«instanceRef» EventFunctionFlowPort_port
Class «instanceRef.target»
Name:  
 
Name: functionFlowPort
 
Details:
 
Property Value
isFinalSpecialization: 0
Object Type Connection Direction Notes
«atpPrototype» FunctionPort Class Generalization To  
«atpPrototype» EAValue Class Strong From  
EventFunctionFlowPort Class Dependency From