Order constraint conflict

ROCKFlows / FromMLWFConfigurationToBPMN

This project aims (i) to record workflows (meta and instance) defined in BPMN (XML parking) extended by a small constraint language, (ii) to merge and verify the knowledge contained and (iii) to transform them into a system of constraints (Feature model) in order to facilitate the selection of a workflow adapted to a new problem.

GNU General Public License v3.0

1 stars 1 forks source link

Order constraint conflict #87

Open NicolasLacroix opened 4 years ago

NicolasLacroix commented 4 years ago

How to manage order constraint conflicts that are not considered in the FeatureModel ?

e.g. tA >> tB and tB >> tA

NicolasLacroix commented 4 years ago

There are 2 different warnings :

conflict involving only one user's choice (can be resolved immediatly by the user)
conflict involving different users' choices (how to solve the conflict ?)

yaelamraou commented 4 years ago

we could think about applying constraints accordingly to workflow type ( feature-based / raw data )

NicolasLacroix commented 4 years ago

* we could think about applying constraints accordingly to workflow type ( feature-based / raw data )

Consider constraints related to the workflow/data type.

This implies having datasets grouped under different data types.

NicolasLacroix commented 4 years ago

For resolution,

Ask discriminant informations
Inform the user about who is involved by this constraint (and how many times it has been confirmed)