Capella adapter - Supported elements
Table of Contents
Component
A Component (Physical or Logical) will be mapped to an ElementDefinition/ElementUsage and an ElementDefinition will be mapped to either a Physical Component or a Logical Component.
| Capella | COMET |
|---|---|
| Property | Parameter |
| Port | ElementUsage |
| Usage/Realization Relations of Port to Interface | BinaryRelationship with “interface” Category |
| Trace/Satisfy Relations | BinaryRelationship with “trace” or “satisfy” Category |
Table 3 Mapping correspondance between a Component and an ElementDefinition
Requirement Element
A Capella Requirement will be mapped to a E-TM-10-25 Requirement and a E-TM-10-25 Requirement will be mapped to a Capella Requirement.
| Capella | COMET |
|---|---|
| Name | Name |
| Id | ShortName |
| Description | Definition |
| DeriveRqt Relations | BinaryRelationship with “Requirement” Category |
Table 4 Mapping correspondence between a requirement and an E-TM-10-25 Requirement The hierarchy defined by Packages will be applied to RequirementsSpecification and RequirementsGroup.
Interface
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.
Property
A Property will be mapped to a Parameter and a Parameter will be mapped to a property.
| Capella | COMET |
|---|---|
| Name | Name |
| DataType/PhysicalQuantity | ParameterType |
| Unit of PhysicalQuantity | MeasurementUnit and MeasurementScale |
| Owned Default Value | Manual ValueSet |
Table 5 Mapping correspondence between a Property and a Parameter.