software development for vehicle electronics has evolved from first-generation approaches based on textual specifications and manual coding, through second-generation techniques using model-based specifications, to third-generation methodologies applying automatic code generation. nevertheless, integration of those model-based components and traditionally programmed parts, such as the basic software, is still done manually, which is an extensive and error-prone process.
within the product field of instrument clusters and control/network electronics for commercial vehicles (cvs), continental automotive provides the model-based development system (mbds), a closed tool chain for software development, integration, and test that has successfully been applied in several customer projects. in contrast to existing approaches, the mbds environment provides a fully automated integration and build process, and is hence classified as a fourth-generation integrated model-based development platform.
mbds is based on matlab and simulink from the mathworks as model-based design tools and integrates several components for design (msr blockset, cv blockset, design patterns, guidelines, help), test (model rule check, test coverage analysis, mil-, sil-, pil-, back-to-back, and regression test), documentation (document generator), and integration (project structure, handling, and library concept) as well as interfaces to external tools to ensure a reliable software development process in accordance with the cv product life-cycle definition based on cmmi. a user-friendly graphical user interface summarizes and extends useful features of the matlab and simulink platform.
the session describes the mbds approach, its advantages, and the resulting business models in partitioning software development between oem and supplier. furthermore, the mbds environment and its main features based on mathworks products are introduced and the workflow is explained. finally, the benefits of using mbds are discussed.
