Questions that might be answered during a KEEL Technology Review performed under an Evaluation License

Did you get a basic understanding of KEEL Technology with the 1 hour introduction via teleconference before taking the on-line training classes?

Was this a valuable 1 hour spent before taking the on-line training classes?

Did the on-line training classes provide sufficient background to start developing with the KEEL Toolkit?
Were any issues encountered installing KEEL "tools"?
Did you run through the KEEL Toolkit Training Manual? Did you find it helpful?
Did you look at the Help files in the KEEL "tools"? Did you use this as reference when developing with KEEL?
Did you benefit from the KEEL Engine "Code Walkthrough" training? Do you feel you understand how KEEL "works"?
Have you developed an evaluation project? Did you encounter any roadblocks?
Do you feel that the KEEL Dynamic Graphical Language helped you understand your problem better?

Do you feel that the KEEL Dynamic Graphical Language will be helpful in continually expanding the models you have built?

Did you get any warning messages during development about "loops" that would indicate a potential unstable situation? Did these warning messages save you time and effort that you might have encountered with conventional programming?
Did you use the Dashboard during development? Did you use the real-world values capabilities in the Dashboard so you could use the real-world sensor values rather than the normalized values used by the KEEL "engine"? Was this helpful?
Did you use the graphing capabilities to help visualize the impacts of non-linear inputs on your model? Was this helpful?
Did you use the KEEL Toolkit to autogenerate the code for the KEEL Engine? Does the code documentation satisfy your quality needs?
Have you used the KEEL Toolkit "Project Setup" documentation functions? Do you see the value in assigning a Title, Description (potentially with drawing number), Author, ...?
Did you take the KEEL Toolkit generated "code" and insert it into your development environment for M&S Testing? Was it easy to insert the code into your M&S Development Environment?
Did you use KEEL Language Animation with the KEEL Engine in your M&S Environment? Did Language Animation help you analyze the behavior of your KEEL Engine?
Did you use KEEL Language Animation with the KEEL Log Reader to review sequences of snapshots to see what led up to certain decisions and actions of your target system? Was this helpful in understanding the behavior of your system?
Did you create models of sufficient complexity that they benefited from the KEEL Function Block Tool? Was this helpful in creating models made up of multiple KEEL Engines for a single compile?
Did you repackage your KEEL evaluation model (tested in M&S) for deployment in a target environment? Was it easy to deploy the original model in a new programming language (if your M&S language was different from your production language)?

Was it easy to go from M&S to production?

Did you use "configuration" inputs in your design to support "value" settings and adjustments to test, or even to production designs? Did you keep them in the design and "Lock" them down for potential later change?

Did you see the value in using configuration inputs?
Was this helpful during the development?
Will they be retained in production?

Have you used KEEL Concept to streamline new project setup? Was it helpful in rapidly developing concepts?
Did you use KEEL Influence to create high level documentation for your evaluation project? Was this level of documentation helpful? Was it easy to use?
How long did it take to become comfortable using the KEEL Toolkit and the KEEL Dynamic Graphical Language?
Have you had the opportunity to walk a novice user (untrained in KEEL) through a decision or action by explaining how to trace wires and visualize the importance of information? How much effort was required?

Do you think the effort to explain a decision or action using the KEEL Dynamic Graphical Language is helpful?

Do you feel that the small size of the KEEL Engine is helpful to you, or is this unimportant in your application area?
Do you feel that Compsim's suggestion that KEEL Engines are platform and architecture independent will be helpful in the future?
Do you forecast significant cost and schedule savings by having a single code set (the short copyrighted KEEL Engine conventional code) solve all problems, because this code only has to be certified one time by your software quality group (if you plan to develop multiple projects using KEEL Technology)?
Do you feel the KEEL Dynamic Graphical Language makes it easier to focus on delivering solutions to complex problems, because you can focus on the solutions without continued attention to the underlying mathematics or conventional programming and debugging?

Questions that might be answered during a KEEL Technology Review performed under an Evaluation License

Did you get a basic understanding of KEEL Technology with the 1 hour introduction via teleconference before taking the on-line training classes?

Was this a valuable 1 hour spent before taking the on-line training classes?

Did the on-line training classes provide sufficient background to start developing with the KEEL Toolkit?

Were any issues encountered installing KEEL "tools"?

Did you run through the KEEL Toolkit Training Manual? Did you find it helpful?

Did you look at the Help files in the KEEL "tools"? Did you use this as reference when developing with KEEL?

Did you benefit from the KEEL Engine "Code Walkthrough" training? Do you feel you understand how KEEL "works"?

Have you developed an evaluation project? Did you encounter any roadblocks?

Do you feel that the KEEL Dynamic Graphical Language helped you understand your problem better?

Do you feel that the KEEL Dynamic Graphical Language will be helpful in continually expanding the models you have built?

Did you get any warning messages during development about "loops" that would indicate a potential unstable situation? Did these warning messages save you time and effort that you might have encountered with conventional programming?

Did you use the Dashboard during development? Did you use the real-world values capabilities in the Dashboard so you could use the real-world sensor values rather than the normalized values used by the KEEL "engine"? Was this helpful?

Did you use the graphing capabilities to help visualize the impacts of non-linear inputs on your model? Was this helpful?

Did you use the KEEL Toolkit to autogenerate the code for the KEEL Engine? Does the code documentation satisfy your quality needs?

Have you used the KEEL Toolkit "Project Setup" documentation functions? Do you see the value in assigning a Title, Description (potentially with drawing number), Author, ...?

Did you take the KEEL Toolkit generated "code" and insert it into your development environment for M&S Testing? Was it easy to insert the code into your M&S Development Environment?

Did you use KEEL Language Animation with the KEEL Engine in your M&S Environment? Did Language Animation help you analyze the behavior of your KEEL Engine?

Did you use KEEL Language Animation with the KEEL Log Reader to review sequences of snapshots to see what led up to certain decisions and actions of your target system? Was this helpful in understanding the behavior of your system?

Did you create models of sufficient complexity that they benefited from the KEEL Function Block Tool? Was this helpful in creating models made up of multiple KEEL Engines for a single compile?

Did you repackage your KEEL evaluation model (tested in M&S) for deployment in a target environment? Was it easy to deploy the original model in a new programming language (if your M&S language was different from your production language)?

Was it easy to go from M&S to production?

Did you use "configuration" inputs in your design to support "value" settings and adjustments to test, or even to production designs? Did you keep them in the design and "Lock" them down for potential later change?

Did you see the value in using configuration inputs?

Was this helpful during the development?

Will they be retained in production?

Have you used KEEL Concept to streamline new project setup? Was it helpful in rapidly developing concepts?

Did you use KEEL Influence to create high level documentation for your evaluation project? Was this level of documentation helpful? Was it easy to use?

How long did it take to become comfortable using the KEEL Toolkit and the KEEL Dynamic Graphical Language?

Have you had the opportunity to walk a novice user (untrained in KEEL) through a decision or action by explaining how to trace wires and visualize the importance of information? How much effort was required?

Do you think the effort to explain a decision or action using the KEEL Dynamic Graphical Language is helpful?

Do you feel that the small size of the KEEL Engine is helpful to you, or is this unimportant in your application area?

Do you feel that Compsim's suggestion that KEEL Engines are platform and architecture independent will be helpful in the future?

Do you feel the KEEL Dynamic Graphical Language makes it easier to focus on delivering solutions to complex problems, because you can focus on the solutions without continued attention to the underlying mathematics or conventional programming and debugging?