Search Results

The complexity and the criticality of automotive electronic embedded systems are steadily increasing today, and that is particularly the case for software development. The new ISO 26262 standard for functional safety is one of the answers to these challenges. The ISO 26262 defines requirements on the development process in order to ensure the safety. Among these requirements, fault injection (FI) is introduced as a dedicated technique to assess the effectiveness of safety mechanisms and demonstrate the correct implementation of the safety requirements. Our work aims at developing an approach that will help integrate FI in the whole development process in a continuous way, from system requirements to the verification and validation phase.

The EASIS project clarified typology of dependent failures (Common Cause Failures, Common Mode Failures and Cascading Failures). Typology of dependent failures is a key concept used within safety standards such as IEC61508, or the on-going ISO26262. A presentation of this typology supported with concrete examples will be used to introduce a discussion on dependent failure analysis and bring in the distinction between the concepts of independence and absence of interference. Independence of EE architectural elements is required particularly between two architectural elements implementing a function and its associated safety mechanism. Absence of interference which is less demanding than independence is required to allow architectural elements of different criticality to cohabit (among others, safety-related elements and non-safety-related elements). Typical EE automotive examples will support this discussion