Value Range Conflict 

Definition

A conflict that occurs when the value range of a characteristic is statically restricted and the dependency has to assign a value to it that does not lie within this value range.

A value range is described as statically restricted if it has been already defined in the product model as a subset of all available values – in contrast to constraints that were determined dynamically from dependencies during the configuration process.

This type of conflict is undesired in most cases, and should be avoided during modeling.

Information

By determining and analyzing the configuration conflict, the Configuration Engine can provide information about the conflict and possible actions you can take to resolve it.

Conflict Explanation

Delivery of the technical name for identifying the value range conflict: CONFLICT_STATIC_DOMAIN

Conflict Solution

Delivery of the characteristic value that was set by the user and caused the conflict.

Example

A configurable computer (see Typical Product Model).

The P800 processor requires a size 7 memory that has not yet been released for this class.

Causing the Conflict

...

       1.      User selection: Processor → P800

       2.      Dependency set_Mem_P8 sets the value Size 7 for Memory

       3.      The value Memory: Size 7 does not lie within the value range

Conflict Explanation

·        Technical name: CONFLICT_STATIC_DOMAIN

·        No more information is available

Conflict Solution

The name of the characteristic value that was set by the user and caused the conflict:

·        Processor → P800