Difference between revisions of "MotoHawk:Model-Based Design"
(Created page with "== 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 speci...") |
|||
| Line 1: | Line 1: | ||
== Why Model Based Design? == | == Why Model Based Design? == | ||
| + | |||
| + | '''Model Based Design can save Time and Cost'''. | ||
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. | 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. | ||
| Line 5: | Line 7: | ||
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. | 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. | ||
| − | [[File:v_diagram.jpg|center| | + | [[File:v_diagram.jpg|center]] |
| + | |||
| + | |||
| + | '''Further, Model Based Design allows for Flexibility to Unexpected Changes.''' The Design Process is often shown as linear. One develops a set of Requirements, Designs to meet the requirements, Implements the Design, Verifies the implementation, and the Produces the product. | ||
| + | |||
| + | [[File:linear_process.jpg|center]] | ||
| + | |||
| + | But, in reality this is rarely the case! Unexpected changes to the requirements creep in. The scope may change. Unexpected issues may arise in verification. The Process is in reality more like a circle. Model Based Design allows the project to progress easily between the various stages of the design process. | ||
| + | |||
| + | [[File:circular_process.jpg|center]] | ||
Revision as of 15:04, 1 February 2013
Why Model Based Design?
Model Based Design can save Time and Cost.
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.
Further, Model Based Design allows for Flexibility to Unexpected Changes. The Design Process is often shown as linear. One develops a set of Requirements, Designs to meet the requirements, Implements the Design, Verifies the implementation, and the Produces the product.
But, in reality this is rarely the case! Unexpected changes to the requirements creep in. The scope may change. Unexpected issues may arise in verification. The Process is in reality more like a circle. Model Based Design allows the project to progress easily between the various stages of the design process.
