Case Study of Failure Analysis Techniques for Safety Critical Systems

  • Aiswarya Sundararajan
  • R. Selvarani
Part of the Advances in Intelligent and Soft Computing book series (AINSC, volume 166)


Safety critical systems are built upon complex software and are difficult to maintain. These systems must effectively deal with the defects identified by analyzing its failure in order to make the system free from hazards. Any chance of human injury or death can be avoided by thoroughly verifying the safety of critical software embedded in any safety system. In this paper, the analysis on different failure analysis techniques such as Failure Modes, Effects Analysis (FMEA), Failure Modes, Effects and Criticality Analysis (FMECA) and Fault Tree Analysis (FTA) are carried out considering dependability as its critical parameter. The risk involved in safety critical system is analyzed with the case study of remote monitoring of a patient with pacemaker. The main observations are: i) Failure mode classification of the software at every stage, ii) Safety critical parameter evaluation, iii) Indication of defensive measures against the severity of hazards, iv) Correlation of FMEA, FMECA and FTA with the computed critical data and v) Recommendation of an appropriate failure analysis method for pacemaker operation to ensure safety.

Index Terms

cardiac arrhymias dependability FMEA FMECA FTA pacemaker remote monitoring and safety critical systems 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Greenwell, W.S., Knight, J.C.: Framing analysis of software failure with safety cases. IEEE Transactions on Software Engineering 22904 (January 2010)Google Scholar
  2. 2.
    Kornecki, A.J.: Assesment of software safety via catastrophic events coverage. In: Proceedings of IEEE Computer Society (March 2007)Google Scholar
  3. 3.
    Muller, A., Helms, T.M., Wildau, H.-J.: Remote Monitoring in Patients with Pacemakers and Implantable Cardioverter-Defibrillators: New Perspectives for Complex Therapeutic Management. University of Heidelberg, Germany (2009)Google Scholar
  4. 4.
    Mauser, H., Thurner, E.: Electronic Throttle Control-A Dependability case study. Jounal of Universal Computer Science 5(10), 730–741 (2009), Siemens, A.G.Google Scholar
  5. 5.
    SoftWcare, S.L., Serafin Avendano, C.: Safety and dependability analysis to complement testing of safety-critical software. Espana (2009)Google Scholar
  6. 6.
    Ben Swarup, M., Seetha Ramaiah, P.: An approach to modeling software safety, department of computer science and systems engineering. In: 9th International Conference on Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing. IEEE Computer Society Press (2010)Google Scholar
  7. 7.
    Ben Swarup, M., Seetha Ramaiah, P.: A software safety model for safety critical applications, department of computer science and systems engineering, Andhra University. International Journal of Software Engineering and its Applications 3(4) (October 2009)Google Scholar
  8. 8.
    Glancey, J.: Failure Analysis Methods- What, Why and How? Special Topics in Design. MEEG 466 (Spring 2006)Google Scholar
  9. 9.
    FMECA for command, control, communications, computer, intelligence, surveillance and reconnaissance (C4ISR). Technical Manual (September 29, 2006)Google Scholar
  10. 10.
    Halperin, D., Heydt-Benjamin, T.S., Ransford, B., Clark, S.S., Defend, B., Fu, K., Kohno, T., Maisel, W.H.: Pacemakers and Implantable Cardiac Defibrillators:Software Radio Attacks and Zero-Power Defenses (2010)Google Scholar
  11. 11.
    Sharma, A.: Towards A Verified Cardiac Pacemaker. A Technical Report (November 2010)Google Scholar
  12. 12.
    Barbacci, M., Klein, M.H., Longstaff, T.H., Weinstock, C.B.: Principles for Evaluating the Quality Attributes of a Software Architecture. SEI, Carnegie Mellon University (March 1997)Google Scholar
  13. 13.
    User’s Manual for CARA-FaultTree v4.1 by Sydvest SoftwareGoogle Scholar
  14. 14.
    Crowe, D., Feinberg, A.: Design for Reliability. In: Failure Modes and Effects Analysis, ch. 12. CRC Press, Bocaraton (2001),
  15. 15.
    Assessment worksheet of a particular piece of equipment for UMS managers,supervisors,OHS consultation committees and representatives for all complex asessments, Hazard Identification. Risk Assessment and Control Procedure. University of Western Sydney, June 23 (2003)Google Scholar
  16. 16.
    Reliability engineering resources-Fault Tree Handbook (NUREG-0492), US Nuclear Regulatory Commission,
  17. 17.
    Carlo KoppPeter Harding & Associates, Pty Ltd., System Reliability and Metrics of Reliability, Copyright, PHA Pty Ltd. (1996),
  18. 18.
    FAULT TREE ANALYSIS- A Special Bibliography from the NASA Scientific and Technical Information (STI) Program,
  19. 19.
    Sommerville, I.: Software Engineering. In: Insulin Pump, 7th edn., vol. ch. 3 (2009)Google Scholar
  20. 20.
    Otto, K.W., Kristin: Product Design - Techniques in Reverse Engineering and New Product Development. Prentice Hall (2001) ISBN 0-13-021271-7Google Scholar
  21. 21.
    Kmenta, S., Ishii, K.: Scenario-Based Failure Modes and Effects Analysis Using Expected Cost. Journal of Mechanical Design- 126(6), 1027 (2004)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag GmbH Berlin Heidelberg 2012

Authors and Affiliations

  1. 1.M.S. Ramaiah Institute of TechnologyBangaloreIndia

Personalised recommendations