Issue No.04 - July-Aug. (2013 vol.11)
Domenico Cotroneo , Università degli Studi di Napoli Federico II
Roberto Natella , Università degli Studi di Napoli Federico II
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MSP.2013.54
As software becomes more pervasive and complex, it's increasingly important to ensure that a system will be safe even in the presence of residual software faults (or bugs). Software fault injection consists of the deliberate introduction of software faults for assessing the impact of faulty software on a system and improving its fault tolerance. SFI has been included as a recommended practice in recent safety standards and has therefore gained interest among practitioners, but it's still unclear how it can be effectively used for certification purposes. In this article, the authors discuss the adoption of SFI in the context of safety certification, present a tool for the injection of realistic software faults, and show the usage of that tool in evaluating and improving the robustness of an operating system used in the avionic domain.
Safety, Fault tolerance, Software safety, Certification, Software reliability, Security, SAFE tool, safety-critical systems, software fault tolerance, fault injection, software dependability assessment, software faults, safety certification, SW-FMEA, software RAMS
Domenico Cotroneo, Roberto Natella, "Fault Injection for Software Certification", IEEE Security & Privacy, vol.11, no. 4, pp. 38-45, July-Aug. 2013, doi:10.1109/MSP.2013.54