Search Results

Hazard analysis plays an important role in the development of safety-critical systems. Hazard analysis techniques have been used in the development of conventional automotive systems. However, as future automotive systems become more sophisticated in functionality, design, and applied technology, the need for a more comprehensive hazard analysis approach has arisen. In this paper, we describe a comprehensive hazard analysis approach for system safety programs. This comprehensive approach involves applying a number of hazard analysis techniques and then integrating their results. This comprehensive approach attempts to overcome the narrower scope of individual techniques while obtaining the benefits of all of them.

In this paper, we review existing software safety standards, guidelines, and other software safety documents. Common software safety elements from these documents are identified. We then describe an adaptable software safety process for automotive safety-critical systems based on these common elements. The process specifies high-level requirements and recommended methods for satisfying the requirements. In addition, we describe how the proposed process may be integrated into a proposed system safety process, and how it may be integrated with an existing software development process.

Given the fast changing market demands, the growing complexity of features, the shorter time to market, and the design/development constraints, the need for efficient and effective verification and validation methods are becoming critical for vehicle manufacturers and suppliers. One such example is fault-tree analysis. While fault-tree analysis is an important hazard analysis/verification activity, the current process of translating design details (e.g., system level and software level) is manual. Current experience indicates that fault tree analysis involves both creative deductive thinking and more mechanical steps, which typically involve instantiating gates and events in fault trees following fixed patterns. Specifically for software fault tree analysis, a number of the development steps typically involve instantiating fixed patterns of gates and events based upon the structure of the code. In this work, we investigate a methodology to translate software programs to fault trees.

A requirement of many modern safety-critical automotive applications is to provide failsafe operation. Several analysis methods are available to help confirm that automotive safety-critical systems are designed properly and operate as intended to prevent potential hazards from occurring in the event of system failures. One element of safety-critical system design is to help verify that the software and microcontroller are operating correctly. The task of incorporating failsafe capability within an embedded microcontroller design may be achieved via hardware or software techniques. This paper surveys software failsafe techniques that are available for application within a microcontroller design suitable for use with safety-critical automotive systems. Safety analysis techniques are discussed in terms of how to identify adequate failsafe coverage.

Embedded controllers and digital signal processors are increasingly being used in automotive safety critical control systems. Controller integrity is a significant concern in these systems. Over the past decade, several techniques have been published about controller safety and integrity verification. These techniques include: single processor with watchdog, dual processors, dual core processor, and asymmetric processor (intelligent watchdog). Each of these techniques have benefits, however, many new non-distributed safety-critical systems are applying the asymmetric processor technique to help verify controller integrity. This paper discusses an overview of five controller integrity techniques, and then provides a detailed discussion of an asymmetric processor approach. This paper presents two different options within the asymmetric processor approach.