SimuQuest Agile, Model-Based Design Approach

In the agile, model-based approach, THE DESIGN IS THE IMPLEMENTATION™ and R&D and production work together seamlessly using the same tools. Entire development projects are completed in a fraction of the time that it takes when using traditional methods.

Model based design involves adopting a new development process that is facilitated by a new set of tools. During this process the following artifacts are produced:

• A data dictionary that abstracts the signals, inputs and outputs of the system
• An architecture model with timing threads and event-based threads
• A plant model that simulates the physical device
• A micro-interface model that ties signals, inputs and outputs to the micro features
• A controls model which includes all the control features of the system; and
• A functional test model

These models are developed entirely inside the Matlab and Simulink environments, using the blocksets and configuration tools provided by SimuQuest.

The data dictionary and architecture model which incorporates a plant model, a controls model and functional test model make up the development environment. This development environment allows fully integrated testing to occur without a single line of code being written.

Once functional testing has been completed, the plant model inside the architecture model is then replaced with the micro-interface model through a single drag and drop action and code is generated for the complete software application.

This pre-validated, optimized code - which includes all the BIOS code and control features is then compiled and downloaded to the target microcontroller. This step, the beginning of an arduous effort using the traditional approach, takes minutes or hours using the SimuQuest tools.

The advantages:

• Work at a higher level of abstraction to increase productivity
• Eliminate effort of hand coding
• Eliminate all errors introduced by hand coding
• Find and correct requirements errors during design phase
• Reduce development time by many calendar months
• Reduce development effort by many man years
• Introduce advanced features late in the project
• React to requirements changes late in the project
• Bring products to market earlier