Collect and specify further model constraints

eichelbe commented 8 years ago

Please review the configuration model thoroughly and suggest new required constraints.

flow/node names within a pipeline must not be empty and must be unique
parameters within an algorithm/node must be unique
source and sink shall have implementation data assigned
unconnected source / sink do not make sense
data source/sink/element storageLocation must be unique
tuple type for pipeline flows: if predecessor has one output type, propagate that one. Else it must be one of the predecessor output types.
initialization of tasks/parallelization for HardwareAlgorithm (Cui)
ReplaySink: one field must be of type TimeStampType, at least one filed must be a keyPart

Hint: Do not forget to define the constraints as Constraint variables and to provide a useful description in the respective .text file.

eichelbe commented 8 years ago

See also #14

eichelbe commented 8 years ago

Cui + Holger: Added constraints for mandatory settings ...

eichelbe commented 7 years ago

Added the ReplaySink constraint description based on communication with Tuan-Anh

Elscha commented 7 years ago

Added tupleType constraint as demanded by @cuiqin. However, this constraint does only work for Sources and FamilyElements. For some reason the constraint creates a false positive result for DataManagementElements. For this reason it is disabled for DataManagementElements.

I assume a modelling failure by me as a reason for the wrong reasoner output.

QualiMaster / QM-IConf

Collect and specify further model constraints #13