Common use of Concept Mapping Clause in Contracts

Concept Mapping. The general mapping between EAST-ADL modeling constructs and the selected construct in SystemWeaver is described below. Attribute Attribute In SystemWeaver the attribute name and the attribute type are the same. Therefore is the attribute type and name the same in the SystemWeaverExplorer (GUI for user models). One alternative solution is to prefix the attribute name to the attribute type: <name>:<type> Attribute type Attribute type Since SystemWeaver does not distinguish between attribute names and attribute types, different attributes cannot share the same type definition (apart from sharing the same basic type) but separate types must be defined for such cases. Optional attributes - Attributes with a multiplicity of 0..1 are not supported in Systemweaver, only mandatory attributes, with a multiplicity of 1 EAElement Item In SystemWeaver items have names as a property. Not an attribute as in EA. «atpType» Item, DefObj of a Part The semantics of atpTypes are supported by SystemWeaver Item Types «atpPrototype» Part types, suffixed with a The semantics of atpPrototypes are supported by EAST-ADL concept SystemWeaver concept Comment “«atpPrototype»” SystemWeaver Part types «atpPrototype» + ports Parts + ports. A Part owns ports. Parts inherit its ports from its defining type (Item). «atpStructureElement» Items and parts in combination with its node tree. For Items see «atpType» and for parts «atpPrototype» atpStructureElement which combines «atpType» + «atpPrototype» and have the property of “unique existential quantification” or “disambiguation” is in SystemWeaver solved with the node tree. Where Items and parts uses the node tree/instance tree. Short description for Nodes: In SystemWeaver there is an instance tree that is created automatically for each atpStuctureElement and all included prototypes. In the tree there is a unique instance node created and linked to each such element. Whenever there is a need for a reference to an element in the structure the reference is made to the corresponding node. Also keep in mind that the Item solution means that reusability is mandatory, even when not wanted. No significant drawbacks can be seen for this exception. Note that In a fine-grained versioning system like SystemWeaver even an atpStructureElement will be reused by different versions. «instanceRef» (“Dependencies”) Nodes Supported by SystemWeaver, with nodes and node references. SystemWeaver does not support type constraints on node references «isOfType» Meta model: DefType Model: DefObj IsOfType is implemented as a standard DefType construct. “ Allocation See comment Maps to a node to node relation in SystemWeaver.

Concept Mapping. The general mapping between EAST-ADL modeling constructs and the selected construct in SystemWeaver is described below. Attribute Attribute In SystemWeaver the attribute name and the attribute type are the same. Therefore is the attribute type and name the same in the SystemWeaverExplorer (GUI for user models). One alternative solution is to prefix the attribute name to the attribute type: <name>:<type> Attribute type Attribute type Since SystemWeaver does not distinguish between attribute names and attribute types, different attributes cannot share the same type definition (apart from sharing the same basic type) but separate types must be defined for such cases. Optional attributes - Attributes with a multiplicity of 0..1 are not supported in Systemweaver, only mandatory attributes, with a multiplicity of 1 EAElement Item In SystemWeaver items have names as a property. Not an attribute as in EA. «atpType» Item, DefObj of a Part The semantics of atpTypes are supported by SystemWeaver Item Types «atpPrototype» Part types, suffixed with a “«atpPrototype»” The semantics of atpPrototypes are supported by EAST-ADL concept SystemWeaver concept Comment “«atpPrototype»” SystemWeaver Part types «atpPrototype» + ports Parts + ports. A Part owns ports. Parts inherit its ports from its defining type (Item). «atpStructureElement» Items and parts in combination with its node tree. For Items see «atpType» and for parts «atpPrototype» atpStructureElement which combines «atpType» + «atpPrototype» and have the property of “unique existential quantification” or “disambiguation” is in EAST-ADL concept SystemWeaver concept Comment SystemWeaver solved with the node tree. Where Items and parts uses the node tree/instance tree. Short description for Nodes: In SystemWeaver there is an instance tree that is created automatically for each atpStuctureElement and all included prototypes. In the tree there is a unique instance node created and linked to each such element. Whenever there is a need for a reference to an element in the structure the reference is made to the corresponding node. Also keep in mind that the Item solution means that reusability is mandatory, even when not wanted. No significant drawbacks can be seen for this exception. Note that In a fine-grained versioning system like SystemWeaver even an atpStructureElement will be reused by different versions. «instanceRef» (“Dependencies”) Nodes Supported by SystemWeaver, with nodes and node referencesit´s reference. SystemWeaver does not support type constraints on The problem is that node references «isOfType» Meta model: DefType Model: DefObj IsOfType is implemented as a standard DefType construct. “ Allocation See comment Maps to a node to node relation in SystemWeavercan only point out the specific node, but not the Item type.