User Tools

Site Tools


tutorials:vec_v1_4:documentation:8_1_variant_management_for_ecus

 Index - Previous - Next

8.1 Variant Management for ECUs

PartUsagePartUsagePartOccurrenceEEComponentRoleEEComponentRoleEEComponentRolePartOccurrenceEEComponentRoleEEComponentSpecificationEEComponentSpecificationEEComponentSpecificationEEComponentRolePartVersionPartVersionPartVersionUsageNodePartOccurrenceComponentNodeComponentNode

This example demonstrates how the variant management can be handled in the systems schematic on different levels of abstraction.

The top most element is the usage node. It defines an abstract position / function in the vehicle. In the example it is the back light on the left hand side (named “MX3”). This function can be realized by two different electrological variants (interfaces). These variants are represented by ComponentNodes. In the example there is one variant with two pins (MX3.1) and one variant with three pins (MX3.2). On a more concrete level these interfaces can be satisfied by one or more EE-components (alternatives). These EE-Components are defined by PartVersion with a EEComponentSpecification. In order to define restrictions a corresponding PartOccurrence with a VariantConfiguration can be defined.

The PartUsages in the example are needed for to reasons:

  1. They serve as a container to group the different possible alternatives (“realizedPartUsage”).
  2. It is necessary to declare one of the EEComponents as the representative of all alternatives of a variant. This is done by the reference between the PartUsage and the corresponding EEComponentSpecification.


Index - Previous - Next

tutorials/vec_v1_4/documentation/8_1_variant_management_for_ecus.txt · Last modified: 2016/05/12 14:27 (external edit)