MotoHawk:Model-Based Design

Why Model Based Design?

The V diagram below compares hand coding with Model Based Design. The process starts at the upper left with Specifications. Often, these specifications are in the form of graphical representations such as a flow chart. The process continues downward along the left to modeling of the system and then Designing and Implementing Software to meet the requirement. Once the software is written, then the process continues up along the right of the V, towards debugging the software, SW verification, and then to verification on hardware. This is in low level code.

Model Based design allows the Application Designer to work at the Model Level, cutting out the time and expense involved in SW Design, Implementation, SW Debugging, and SW verification. The low level software for drivers, communication links, RTOS is done upfront.