Search Results

The auto industry has had decades of experience with designing safe vehicles. The introduction of highly integrated features brings new challenges that require innovative adaptations of existing safety methodologies and perhaps even some completely new concepts. In this paper, we describe some of the new challenges that will be faced by all OEMs and suppliers. We also describe a set of generic top-level potential hazards that can be used as a starting point for the Preliminary Hazard Analysis (PHA) of a vehicle software-intensive motion control system. Based on our experience with the safety analysis of a system of this kind, we describe some general categories of hazard causes that are considered for software-intensive systems and can be used systematically in developing the PHA.

Execution of a software safety program is an accepted best practice to help verify that potential software hazards are identified and their associated risks are mitigated. Successful execution of a software safety program involves selecting and applying effective analysis methods and tasks that are appropriate for the specific needs of the development project and that satisfy software safety program requirements. This paper describes the effective application of a set of software safety methods and tasks that satisfy software safety program requirements for many applications. A key element of this approach is a tightly coupled fault tree analysis and failure modes and effects analysis. The approach has been successfully applied to several automotive embedded control systems with positive results.