Mapping correspondance between a block and an ElementDefinition
SysML
COMET
ValueProperty
Parameter
PartProperty
ElementUsage
Port
ElementUsage
Usage/Realization Relations of Port to interface
BinaryRelationship with “interface” Category
Trace/Satisfy Relations
BinaryRelationship with “trace” or “satisfy” Category
Dependency Relations of ValueProperty to State
Parameter will be State Dependent
Mapping correspondence between a requirement and an E-TM-10-25 Requirement
SysML
COMET
Name
Name
Id
Shortname
Text
Definition
DeriveRqt Relations
BinaryRelationship with “requirement” Category
Mapping correspondence between a state and a PossibleFiniteStateList
SysML
COMET
Name
Name
Region
PossibleFiniteState
Mapping of interfaces
An interface will be mapped to a BinaryRelationship between two ElementUsage that represents Port and this BinaryRelationship will be mapped to an interface. The BinaryRelationship will be named by the name of the interface and will have the “interface” Category applied.
Mapping correspondence between a ValueProperty and a Parameter
SysML
COMET
Name
Name
ValueType
ParameterType
Unit of ValueType
MeasurementUnit and MeasurementScale
Default Value
Manual ValueSet
Mapping of stereotype
When mapping from the SysML model, all the applied stereotype to one Block or one Requirement are mapped to one Category into E-TM-10-25. The mapped Category is then created or retrieved from the loaded chain of Reference Data Library. When mapping from a E-TM-10-25 model, all the categories currently assigned to one ElementDefinition or one Requirement are looped through, if any one of them has a name that matches one Stereotype name (case unsensitive) that exists among all available Stereotype from the loaded Profiles, the found Stereotype is then applied to the current mapped Block or Requirement.