Most of us engineers are probably familiar with aspects of Model-driven Development (MDD) in one way or the other. We may not use this specific term, but using models to create and evaluate parts of our design is fairly common. Electronic engineers have been using SPICE modeling and simulation for decades and the use of simulation tools that help evaluate and optimize signal and power integrity for high speed designs is becoming more and more common nowadays.
These parts of MDD usually focus on one specific aspect of the system being designed. A possible next step of MDD is to try and create a model of a (mechatronic) system as a whole and use that to design, verify and optimize the behavior on a much higher level, often covering multiple disciplines. This is what 3T has done for several customer projects.
In this presentation we talk about one of these projects where we’ve successfully used Model-driven Development to enhance the usual development process. We’ll discuss the overall design approach for this specific project, how it was applied in different phases of the design process and how this helped us reduce project risks and cut back on overall development time.
Jasper Keuning, 3T
Click here for the PDF version of the presentation