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.

When developing software it is important to consider process, methods, and tools. For safety-critical software, standards such as IEC 61508 are often used to impose additional constraints on the development process and require the production of verification evidence and other artifacts. These constraints and artifacts are needed whether or not the design and code were produced manually or via tool automation. This paper discusses the usage of Production Code Generation for safety-critical software development.

International standards that define requirements for the development of safety-related systems typically also define required confidence levels for the software tools used to develop those systems. The standards define-to a greater or lesser extent- procedures to classify, validate, certify, or qualify tools. To date, there is no common approach for tool validation, certification, and qualification across safety standards. Different standards attach different levels of importance to tool validation, certification, and qualification, and suggest different approaches to gain confidence in the tools used. With ISO 26262 “Road Vehicles - Functional Safety” on the horizon, automotive software practitioners will need to understand and implement the new software tool classification and qualification requirements laid out in this standard.