|
|
||
|
|||
|
|||
|
|||
|
|||
|
MATT History Part 1 In the early 1990’s, a company named Integrated Systems developed a program called SystemBuild which ran on top of their MatrixX development environment (MatrixX is a tool much like MATLAB used for evaluating large systems of equations). SystemBuild was a GUI/API that allowed engineers to visually specify control system parameters, then simulate their mock system using a built-in simulator. The product was well received by engineers in the industry, but was lacking two crucial features:The SystemBuild environment was poor in specifying dynamic tests to run through models. The SystemBuild environment was interpreted and had no facilities for producing actual system source code (E.g. Compiling a system to C object code). Time passed to 1998, and the bigger fish in the linear equation industry, MathWorks, the developer of MATLAB, merged Integrated Systems. MathWorks had also been developing a control system specification environment since the early 1990’s, Simulink (Simulink had less of an audience do to the price of the software). With the completion of the merger, MathWorks took control of updating and standardizing the MatrixX/SystemBuild environment. This did not last long as MathWorks real intention was to eliminate the competition… During this same time, 1997 - 2000, Dr. Joel Henry was working with NASA engineers producing a great deal of control system testing strategies. NASA Goddard was currently using SystemBuild as their control system specification environment. It was proposed by Dr. Henry to develop at tool that could run on top of the SystemBuild engine; one that could dynamically specify testing inputs for the SystemBuild models that NASA engineers were developing. This lead to the creation of a grant proposal that contracted East Tennessee State University, where Dr. Henry was employed, to develop a tool called MATT (MatrixX Automated Testing Tool). |
|||
|
|||
| If you have any questions
or comments, we can be reached at the following addresses: Project Leader: Joel Henry MATT Customer Support Web Support: Spencer Wolny |
|
|
|
|
|||
