The application I am working on requires complex parameterization and configuration to model custom parts. There are various interdependencies between different parameters, for example, this parameter of parameter βAβ invalidates certain values ββfor βBβ and βCβ or adds additional restrictions to the values ββof parameter βDβ.
Currently, this is being solved by storing all the parameters in the lookup tables and executing the rules on them. Rules are written manually in XML, loaded and converted to some intermediate format, which is used for the rule engine. Each time a parameter changes, all the rules are repeated.
It is at the same time very slow and error prone.
I believe that it would be useful to use the DAG-based approach, where we can only do updates on subsets of the graph.
Is that a good idea? Do you know any better approaches? If you have experience with similar problems, how do you solve them?
Edit: I am trying to create a construct in which only changes to dependent subsets of a parameter should be changed when changing. Currently, the rules are repeated globally with every change. Parameters are set by default, but can be changed by the user. Depending on the parameter value, the default values ββfor others may differ.
source share