Signal Processing DesignLine Blog
Yesterday I had a couple briefings touching on model-based-design. This design approach enables modeling of an entire system, typically represented at the top level in a graphical programming environment. This model can then serve as a "golden reference" to validate the system's functional blocks as they're implemented in lower level languages, or serve as a starting point for automatic code generation.
On this point, MathWorks (or "The MathWorks," as they like to be called) announced that its Simulink Verification and Validation model verification now meets the DO-178B and IEC-61508 standards and the MAAB modeling guidelines. In addition to validating completed designs, the software lets you impose modeling rules to avoid errors in the first place. (Think "No red blocks after blue blocks!" and you'll get the idea of what this does.)
I also had a chance to talk to Telelogic, a model-based-design player I wasn't so familiar with. It was announcing the latest version of its Rhapsody 7.2 solution. One particularly interesting feature was a tool for re-engineering C code. Users can input existing C code projects and Rhapsody will generate a high-level block diagram that attempts to maintain the structure, naming conventions, etc of the original code. Pretty neat.