Development Process Comparisons

Conventional Process compared to the KEEL Process

could result in 90% (or more) reduction in development time

Development process without KEEL (Conventional Process):

1. Domain expert describes the problem
2. Mathematician writes formulas (differential equations…)
3. Software engineer translates the formulas to computer code
4. Software engineer debugs the code
5. Software engineer writes a wrapper around the algorithm for testing by mathematician
6. Mathematician changes the formula - Go back to step 3
7. Software engineer documents the design (maybe)
8. Algorithm is integrated in a simulator for further testing by domain expert
9. Domain expert changes the description of the solution - go back to step 2
10. Environment changes - go back to step 1

Development process with KEEL:

1. Domain expert models and tests a solution to the dynamic problem from within the KEEL Toolkit using the dynamic graphical language
2. When testing is complete, the domain expert gives automatically created code (conventional computer language: C, C++, C#, Flash, Jave, JavaScript, Octave, Python, VB,…) to software engineer for integration in application.
3. Environment changes - go back to step 1

Watch the creation of executable functionality in < 10 Seconds: 10 second video

Watch the creation of a Configurable Non-Linear System in < 30 Seconds: 30 second video

Summary:

These results can be achieved using the KEEL Dynamic Graphical Language, because the models can be developed and tested by the domain expert without requiring the use of complex mathematical formulas (propositional calculus, etc) and attempting to transfer concepts to code through multiple translations. The computer code is automatically generated resulting in the elimination of "typographical coding errors".