Search Results

When transitioning to Model-Based Design for embedded systems development, it is essential to consider an overall plan spanning people, development processes, and tools. A common sense approach when beginning any process improvement activity is to first identify the problem to be solved and then develop a plan to implement the solution. When transitioning to Model-Based Design, performing the transition in an iterative manner - do, learn, adjust, and repeat - has been shown to be most effective. The end goal is a development process where the model is the design, verification is done throughout the development process using simulation, and the implementation of the entire application onto target hardware is highly automated. Faced with design and organizational complexity, time, quality, and cost pressures, the transition is akin to changing a flat tire while moving down the highway. Choosing the right first steps are key to a successful transition.

As the demand for high-integrity and mission-critical embedded software intensifies, many organizations have adopted Model-Based Design to overcome the challenges associated with design complexity, reliability, quality, and time-to-market for embedded-systems development. The breadth and scope of projects applying Model-Based Design continues to increase rapidly, resulting in models that are exceptionally large and complex. Consequently, project teams have increased in size, thereby increasing the need for communication and collaboration. Model-Based Design facilitates parallel development in large-scale modeling projects by enabling multiple project teams to independently design models, integrate them with others, generate production code, and verify different model components within a larger collaborative infrastructure.