Common use of FunctionModeling Clause in Contracts

FunctionModeling. EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment shortName Attribute X n/a X • Export and import supported Used reg exp. [a-zA-Z][a-zA-Z0- 9_]{0,31} instead of ([a-zA-Z][a- zA-Z0-9_]{0,31})+ for name validation. ()+ seems strange, and complexity of evaluation grows exponentially with the length of the name. AllocateableElement {abstract} n/a n/a not In SystemWeaver only supports instance references directly from the item owning the instance/node tree, meaning that the allocation concept is not allowed in SystemWeaver. SystemWeaver also does not support multiple inheritances. AllocateableElements is therefore not implemented. Allocation Item X X X Export to EAXML supported AnalysisFunctionPrototyp e Part X X X • Import and Export Supported In SystemWeaver this is a part and a part does not support inheritance. Due to this reason the AnalysisFunctionPrototype is not inherited from the FunctionPrototype (Which is a part) AnalysisFunctionType Item X X X Import and Export supported BasicSoftwareFunctionTy pe Item X X X Import and Export supported ClientServerKind «enumeration» Attribute X X X Import and Export is supported * See section 4.2 attributes for more details. DesignFunctionPrototype Part X X X Import and Export supported DesignFunctionType Item X X X Import and Export supported EADirectionKind «enumeration» Attribute X X X • Import and Export available Native tool view in SystemWeaver use parts (prototypes) corresponding to the in/out/inout values, rather than attribute types. However, a way to solve this is to use the inout part type only for all EAST-ADL ports types, and then use the DirectionKind to decorate the model with a direction. EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment FunctionalDevice Item X X X Import and Export supported FunctionAllocation Item X X X Export to EAXML supported FunctionClientServerInter face «atpType» Item X n/a X Import and Export supported FunctionClientServerPort Item X X X Import and Export supported FunctionConnector «atpStructureElement» Part Type (EAFN and EAFO) X X X • Import and Export supported • Part types used rather than item types for best use of the SystemWeaver Platform. Separate part types are used for the assembly and the delegation type, due to different instance tree reference mechanisms (node and part respectively) FunctionFlowPort X X X Import and Export supported FunctionPort {abstract} «atpPrototype» Item {abstract} X X X Import and Export supported FunctionPowerPort X X X Import and Export supported FunctionPrototype {abstract} «atpPrototype» * X X *Not Supported or needed explicitly. See DesignFunctionPrototype and AnalysisFunctionProtoype for details. FunctionType {abstract} «atpType» Item {abstract} X X X Import and Export supported HardwareFunctionType Item X X X Import and Export supported LocalDeviceManager Item X X X Import and Export supported Operation Item X not not No transformation support PortGroup Part X not not *Since this is implemented using the Part construct in SystemWeaver, subPortGroups cannot be used. The advantage of this is to avoid ambiguity of ports (functionPorts). This means that it can be identified which port belongs to which portGroup and functionType. See ticket 50. Maybe portGroup also is in the wrong abstraction level. Should be closer to implementation level. Because the possibility of knowing group of ports is high on the less abstraction level than in the hardwareModeling. EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment Actuator Item X X X Import and Export supported AllocationTarget Part X * * *No meaning to implement, see multiple inheritance for SystemWeavereaver. In SystemWeaver HardwareComponentPrototype is a part and parts cannot be inherited, due to this reason it is not feasible to implement the AllocationTarget. Cardinality Attribute X X X Export to EAXML is supported

FunctionModeling. EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment shortName Attribute X n/a X • Export and import supported Used reg exp. [a-zA-Z][a-zA-Z0- 9_]{0,31} instead of ([a-zA-Z][a- zA-Z0-9_]{0,31})+ for name validation. ()+ seems strange, and complexity of evaluation grows exponentially with the length of the name. AllocateableElement {abstract} n/a n/a not n/y In SystemWeaver only supports instance references directly from the item owning the instance/node tree, meaning that the allocation concept is not allowed in SystemWeaver. SystemWeaver also does not support multiple inheritancesinheritance. AllocateableElements is therefore not implemented. EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment Allocation Item X X X Export to EAXML supported n/a AnalysisFunctionPrototyp e Part X X X • Import and Export Supported In SystemWeaver this is a part and a part does not support inheritance. Due to this reason the AnalysisFunctionPrototype is not inherited from the FunctionPrototype (Which is a part) AnalysisFunctionType Item X X X Import and Export supported BasicSoftwareFunctionTy pe Item X X X Import and Export supported ClientServerKind «enumeration» Attribute X X X Import and Export is supported * See section 4.2 attributes for more details. ClientServerKind «enumeration» Item X DesignFunctionPrototype Part X X X Import and Export supported Since Sdoes not support inheritance for parts. DesignFunctionType Item X X X Import and Export supported EADirectionKind «enumeration» Attribute X X X • Import and Export available Native tool view in SystemWeaver use parts (prototypes) corresponding to the in/out/inout values, rather than attribute types. However, a way to solve this is to use the inout part type only for all EAST-ADL ports types, and then use the DirectionKind to decorate the model with a direction. EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment FunctionalDevice Item X X X Import and Export supported FunctionAllocation Item X X X Export to EAXML supported FunctionClientServerInter face «atpType» Item X n/a X Import and Export supported FunctionClientServerPort Item X X X Import and Export supported FunctionConnector «atpStructureElement» Part Type (EAFN and EAFO) X X X • Import and Export supported • Part types used rather than item types for best use of the SystemWeaver Platform. Separate part types are used for the assembly and the delegation type, due to different instance tree reference mechanisms (node and part respectively) FunctionFlowPort X X X Import and Export supported FunctionPort {abstract} «atpPrototype» Item {abstract} X X X Import and Export supported FunctionPowerPort X X X Import and Export supported FunctionPrototype {abstract} «atpPrototype» * X X *Not Supported or needed explicitly. See DesignFunctionPrototype and AnalysisFunctionProtoype According to the chosen generic mapping concept for details. FunctionType {abstract} «atpType» Item {abstract} X X X Import and Export supported HardwareFunctionType Item X X X Import and Export supported LocalDeviceManager Item X X X Import and Export supported Operation Item X not not No transformation support PortGroup Part X not not *Since this is implemented using the Part construct in SystemWeaver, subPortGroups canwhere <<atpPrototype>> maps to SystemWeaver Parts, and <<isOfType>> maps to SystemWeaver Item, the FunctionPort should be a part type. However since SystemWeaver does not be used. The advantage of this is to avoid ambiguity of ports (functionPorts). This means that it can be identified which port belongs to which portGroup and functionType. See ticket 50. Maybe portGroup also is in the wrong abstraction level. Should be closer to implementation level. Because the possibility of knowing group of ports is high on the less abstraction level than in the hardwareModeling. support inheritance between part types, EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment Actuator the abstract Item X X X Import type FunctionPort is needed to manage the inheritance between the different port types. This in turn means that the different function ports (FunctionFlowPort, FunctionPowerPort and Export supported AllocationTarget Part X * * *No meaning to implementFunctionClientServerPort) must be modeled as their corresponding datatypes (EADatatype, see CompositeDatatype and FunctionClientServerInterface respectively), and the reason is that SystemWeaver not supports multiple inheritance for SystemWeavereaverinheritance?? This also means that the attributes of the different port types (EADirectionKind and ClientServerKind) are modeled as SystemWeaver part attributes rather than as item attributes. In SystemWeaver HardwareComponentPrototype is a part and parts cannot be inherited, due to this reason it is not feasible to implement the AllocationTarget. Cardinality Attribute X X X Export to EAXML is supportedFunctionPowerPort

FunctionModeling. EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment shortName Attribute X n/a X •  Export and import supported Used reg exp. [a-zA-Z][a-zA-Z0- 9_]{0,31} instead of ([a-zA-Z][a- zA-Z0-9_]{0,31})+ for name validation. ()+ seems strange, and complexity of evaluation grows exponentially with the length of the name. AllocateableElement {abstract} n/a n/a not In SystemWeaver only supports instance references directly from the item owning the instance/node tree, meaning that the allocation concept is not allowed in SystemWeaver. SystemWeaver also does not support multiple inheritances. AllocateableElements is therefore not implemented. Allocation Item X X X Export to EAXML supported AnalysisFunctionPrototyp e Part X X X •  Import and Export Supported In SystemWeaver this is a part and a part does not support inheritance. Due to this reason the AnalysisFunctionPrototype is not inherited from the FunctionPrototype (Which is a part) AnalysisFunctionType Item X X X Import and Export supported BasicSoftwareFunctionTy pe Item X X X Import and Export supported ClientServerKind «enumeration» Attribute X X X Import and Export is supported * See section 4.2 attributes for more details. DesignFunctionPrototype Part X X X Import and Export supported DesignFunctionType Item X X X Import and Export supported EADirectionKind «enumeration» Attribute X X X •  Import and Export available Native tool view in SystemWeaver use parts (prototypes) corresponding to the in/out/inout values, rather than attribute types. However, a way to solve this is to use the inout part type only for all EAST-ADL ports types, and then use the DirectionKind to decorate the model with a direction. EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment FunctionalDevice Item X X X Import and Export supported FunctionAllocation Item X X X Export to EAXML supported FunctionClientServerInter face «atpType» Item X n/a X Import and Export supported FunctionClientServerPort Item X X X Import and Export supported FunctionConnector «atpStructureElement» Part Type (EAFN and EAFO) X X X •  Import and Export supported •  Part types used rather than item types for best use of the SystemWeaver Platform. Separate part types are used for the assembly and the delegation type, due to different instance tree reference mechanisms (node and part respectively) FunctionFlowPort X X X Import and Export supported FunctionPort {abstract} «atpPrototype» Item {abstract} X X X Import and Export supported FunctionPowerPort X X X Import and Export supported FunctionPrototype {abstract} «atpPrototype» * X X *Not Supported or needed explicitly. See DesignFunctionPrototype and AnalysisFunctionProtoype for details. FunctionType {abstract} «atpType» Item {abstract} X X X Import and Export supported HardwareFunctionType Item X X X Import and Export supported LocalDeviceManager Item X X X Import and Export supported Operation Item X not not No transformation support PortGroup Part X not not *Since this is implemented using the Part construct in SystemWeaver, subPortGroups cannot be used. The advantage of this is to avoid ambiguity of ports (functionPorts). This means that it can be identified which port belongs to which portGroup and functionType. See ticket 50. Maybe portGroup also is in the wrong abstraction level. Should be closer to implementation level. Because the possibility of knowing group of ports is high on the less abstraction level than in the hardwareModeling. EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment Actuator Item X X X Import and Export supported AllocationTarget Part X * * *No meaning to implement, see multiple inheritance for SystemWeavereaver. In SystemWeaver HardwareComponentPrototype is a part and parts cannot be inherited, due to this reason it is not feasible to implement the AllocationTarget. Cardinality Attribute X X X Export to EAXML is supported

FunctionModeling. EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment shortName Attribute X n/a X • Export and import supported Used reg exp. [a-zA-Z][a-zA-Z0- 9_]{0,31} instead of ([a-zA-Z][a- zA-Z0-9_]{0,31})+ for name validation. ()+ seems strange, and complexity of evaluation grows exponentially with the length of the name. AllocateableElement {abstract} n/a n/a not n/y In SystemWeaver only supports instance references directly from the item owning the instance/node tree, meaning that the allocation concept is not allowed in SystemWeaver. SystemWeaver also does not support multiple inheritances. AllocateableElements is therefore not implemented. EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment Allocation Item X X X Export to EAXML supported AnalysisFunctionPrototyp e Part X X X • Import and Export Supported In SystemWeaver this is a part and a part does not support inheritance. Due to this reason the AnalysisFunctionPrototype is not inherited from the FunctionPrototype (Which is a part) AnalysisFunctionType Item X X X Import and Export supported BasicSoftwareFunctionTy pe Item X X X Import and Export supported ClientServerKind «enumeration» Attribute X X X Import and Export is supported * See section 4.2 attributes for more details. ClientServerKind «enumeration» Item X DesignFunctionPrototype Part X X X Import and Export supported Since Sdoes not support inheritance for parts. DesignFunctionType Item X X X Import and Export supported EADirectionKind «enumeration» Attribute X X X • Import and Export available Native tool view in SystemWeaver use parts (prototypes) corresponding to the in/out/inout values, rather than attribute types. However, a way to solve this is to use the inout part type only for all EAST-ADL ports types, and then use the DirectionKind to decorate the model with a direction. EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment FunctionalDevice Item X X X Import and Export supported FunctionAllocation Item X X X Export to EAXML supported FunctionClientServerInter face «atpType» Item X n/a X Import and Export supported FunctionClientServerPort Item X X X Import and Export supported FunctionConnector «atpStructureElement» Part Type (EAFN and EAFO) X X X • Import and Export supported • Part types used rather than item types for best use of the SystemWeaver Platform. Separate part types are used for the assembly and the delegation type, due to different instance tree reference mechanisms (node and part respectively) FunctionFlowPort X X X Import and Export supported FunctionPort {abstract} «atpPrototype» Item {abstract} X X X Import According to the chosen generic mapping concept for SystemWeaver, where <<atpPrototype>> maps to SystemWeaver Parts, and Export supported <<isOfType>> maps to SystemWeaver Item, the FunctionPort should be a part type. However since SystemWeaver does not support inheritance between part types, EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment the abstract Item type FunctionPort is needed to manage the inheritance between the different port types. This in turn means that the different function ports (FunctionFlowPort, FunctionPowerPort and FunctionClientServerPort) must be modeled as their corresponding datatypes (EADatatype, CompositeDatatype and FunctionClientServerInterface respectively), and the reason is that SystemWeaver not supports multiple inheritance?? This also means that the attributes of the different port types (EADirectionKind and ClientServerKind) are modeled as SystemWeaver part attributes rather than as item attributes. FunctionPowerPort X X X Import and Export supported FunctionPrototype {abstract} «atpPrototype» * X X *Not Supported or needed explicitlySupported. See DesignFunctionPrototype and AnalysisFunctionProtoype for details. FunctionType {abstract} «atpType» Item {abstract} X n/a X X Import and Export supported HardwareFunctionType Item X X X Import and Export supported n/a LocalDeviceManager Item X X X Import and Export supported n/a Operation Item X not not No transformation support n/a PortGroup Part X not not *Since n/a Because we in SystemWeaver implemented this is implemented using the Part construct in SystemWeaveras a part, subPortGroups we cannot be usedhave subPortGroups. The advantage of this is to avoid ambiguity of ports (functionPorts). This means that it can be identified we know which port belongs to which portGroup and functionType. See ticket 50. Maybe portGroup also is in the wrong abstraction level. Should be closer to implementation level. Because the possibility of knowing group of ports is high on the less abstraction level than in the hardwareModeling. Actuator Item X X X AllocationTarget Part X n/a No meaning to implement, see multiple inheritance for SystemWeavereaver. EAST-ADL element SystemWeaver concept Impl Meta Impl view Impl XML Comment Actuator Item X X X Import and Export supported AllocationTarget Part X * * *No meaning to implement, see multiple inheritance for SystemWeavereaver. In SystemWeaver HardwareComponentPrototype is a part and parts cannot be inherited, due to this reason it is not feasible to implement the AllocationTarget. Cardinality Attribute X X X Export Regular expression used to EAXML is supportedcover meaningful cases