Verification and Validation According to ISO 26262: A Workflow to Facilitate the Development of High-Integrity Software

International audienceModel-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 functional safety standards such as ISO 26262. For the development of high-integrity in-vehicle software, ISO 26262 is considered state-of-the-art or generally accepted rules of technology (GART) [Fal02, Lov06]. Developers of in-vehicle software need to understand and implement the standard's requirements pertaining to software development. Due to the widespread utilization of Model-Based Design to develop automotive E/E systems, it is of particular importance to setup ISO 26262 compliant Model-Based Design processes and tool chains. This paper discusses a verification and validation workflow for developing in-vehicle software components which need to comply with ISO 26262-6 using Model-Based Design. It discusses tool support by using a Simulink® family tool chain for Model-Based Design as an example