Search Results

Model-Based Design with production code generation has been extensively utilized throughout the automotive software engineering community because of its ability to address complexity, productivity, and quality challenges. With new applications such as lane departure warning or electromechanical steering, engineers have begun to consider Model-Based Design to develop embedded software for applications that need to comply with safety standards such as IEC 61508. For in-vehicle applications, IEC 61508 is often considered state-of-the-art or generally accepted rules of technology (GART) for development of high-integrity software [6, 11]. In order to demonstrate standards compliance, the objectives and recommendations outlined in IEC 61508-3 [8] must be mapped onto processes and tools for Model-Based Design. This paper discusses a verification and validation workflow for developing in-vehicle software components which need to comply with IEC 61508-3 using Model-Based Design.

Today, many leading automotive OEMs and Suppliers are adopting Model-Based Design for the development of embedded systems applications. In this paper, the authors review the challenges of performing configuration management that is adequate for use in a production environment of the models and associated files central to Model-Based Design.

Model-Based Design is no longer limited to R&D and pilot programs; it is frequently used for production programs at automotive companies around the world. The demands of production programs drive an even greater need for tools and practices that enable automation and rigor in the area of verification, validation, and test. Without these tools and practices, achieving the quality demanded by the automotive market is not possible. This paper presents best practices in verification, validation, and test that are applicable to any program, but are critical when applying Model-Based Design in production programs.