Conventional Process compared to the
KEEL Process
could result in 90% (or more) reduction in
development time
Development process without KEEL (Conventional Process):
 Domain expert describes the problem
 Mathematician writes formulas (differential
equations…)
 Software engineer translates the formulas to
computer code
 Software engineer debugs the code
 Software engineer writes a wrapper around the
algorithm for testing by mathematician
 Mathematician changes the formula  Go back to
step 3
 Software engineer documents the design (maybe)
 Algorithm is integrated in a simulator for further
testing by domain expert
 Domain expert changes the description of the
solution  go back to step 2
 Environment changes  go back to step 1
Development process with KEEL:
 Domain expert models and tests a solution to the
dynamic problem from within the KEEL Toolkit using the dynamic graphical
language
 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.
 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 NonLinear
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".
Copyright , Compsim LLC, All rights reserved
