Search Results

AUTOSAR is on the road. Many OEMs and suppliers have established processes that are project-proven, flexible, and efficient for developing AUTOSAR-compliant applications. These development processes require a variety of tools that support requirements management, system architecture development, Model-Based Design, and verification and validation. Hence, interoperability of these tools is essential for the completion of high-quality projects on time. Building an interface from one tool to the next is often insufficient because processes for production projects are typically more complex than a top-down or bottom-up flow. However, a tool chain must support iterative development across all phases. For example, when a change in customer requirements triggers modifications to the software architecture, definitions for components, runnables, interfaces, or ports all need to be updated accordingly.

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.

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.

Because of its ability to address software complexity and productivity challenges, Model-Based Design with production code generation has been extensively used throughout the automotive software engineering community. More recently, engineers have begun to focus on compliance with external standards such as IEC 61508 and the use of Model-Based Design. For in-vehicle applications, the standard applied is typically IEC 61508-3. To demonstrate standard compliance, the objectives and recommendations outlined in IEC 61508-3 have to be mapped onto Model-Based Design processes and tools. This paper discusses a verification and validation workflow for developing in-vehicle software components that need to meet IEC 61508 using Model-Based Design.

The steady growth in the number of electronic control units on the average vehicle and the complexity of the algorithms that reside on these controllers has resulted in one of the most significant initiatives in the automotive industry in years. AUTOSAR - the Automotive Open System Architecture - has united more than 100 companies, automobile manufacturers, suppliers and tool vendors to develop a standard architecture for electronic control units. By the end of 2006 Version 2.1 was released, and now OEMs as well as suppliers have started to develop and integrate AUTOSAR-compliant functionality and components into vehicles. This paper will focus on the approach and challenges faced by engineers developing AUTOSAR-compliant production code using Model-Based Design.