Safety critical software ground rules

  • Authors

    • Krishna Chaya Addagarrala
    • Patrick Kinnicutt
    2018-05-16
    https://doi.org/10.14419/ijet.v7i2.28.13209
  • MISRA, Safety Critical Standard, Static Analysis.

  • Abstract

    Safety critical software development field is one of the active research areas in many industries like automotive, medical, railways, nuclear and aerospace are placing increased value on safety and reliability. Safety critical software systems are those systems whose failure could result in the death or a serious injury to the people’s life, security is one of the important topics in the field of safety-critical systems and it must be addressed completely in order to operate safety critical software successfully. In this paper we present a study about the set of standards and different ground rules to be followed in critical software development practices in different industries and the challenges in applying these standards. We also discuss the role of static analysis and software integrity levels in these standards, similarities in these standards and the set of activities followed in the development process of these standards.

     

  • References

    1. [1] M. Barr. How to enforce coding standards automatically. https://www.embedded.com/ electronics-blogs/barr-code/4218283/ How-to-enforce-coding-standards-automatically, 2011.

      [2] P. V. Bhansali. Universal software safety standard. SIGSOFT Software Engineering Notes, 30(5), September 2005.

      [3] J.-L. Boulanger. CENELEC 50128 and IEC 62279 Standards. Wiley, 2015.

      [4] David and M. Kleidermacher. Using coding standards to improve software quality and security. https://www. embedded.com/design/safety-and-security/4418986/2/ Using-coding-standards-to-improve-software-quality-and-security, 2013.

      [5] T. J. Erkkinen. Safety critical software generation. In IEEE Interna-tional Symposium on Computer Aided Control System Design, pages 237–242. IEEE, 1999.

      [6] ISO. Iso 26262-10:2012(en) road vehicles – functional safety – part 10: Guideline on iso 26262. https://www.iso.org/obp/ui/#iso: std: iso: 26262:-10: ed-1:v1:en, 2012.

      [7] R. Johansson and J. Nilsson. The need for an environment perception block to address all asil levels simultaneously. In IEEE Intelligent Vehicles Symposium, pages 1–4. IEEE, 2016.

      [8] L. A. S. Johnson. Do-178b, â€software considerations in airborne systems and equipment certificationâ€. http://www.stsc.hill.af. mil/CrossTalk/1998/oct/schad.asp, 1998.

      [9] J. C. Knight. Safety critical systems: Challenges and directions. In International Conference on Software Engineering, pages 547–550. IEEE, 2002.

      [10] A. Lindgren. Misra c — some key rules to make embedded sys-tems safer. https://www.scribd.com/document/333699819/ MISRA-C-Some-key-rules-to-make-embedded-systems-safer-pdf.

      [11] N. Manzoor, H. Munir, and M. Moayyed. Comparison of static analy-sis tools for finding concurrency. In IEEE 23rd International Sympo-sium on Software Reliability Engineering Workshops, pages 129–133. IEEE, 2012.

      [12] MISRA. MISRA Standards. https://www.misra.org.uk.

      [13] National Instruments. What is the iso 26262 functional safety stan-dard? http://www.ni.com/white-paper/13647/en, 2014

      [14] P. Panaroni, G. Sartori, and F. Fabbrini. Safety in automotive software: An overview of current practices. In 32nd Annual IEEE International Conference on Computer Software and Applications, pages 1053–1058. IEEE, 2008.

      [15] S. Panichella, V. Arnaoudova, M. D. Penta, and G. Antoniol. Would static analysis tools help developers with code reviews? In IEEE 22nd International Conference onSoftware Analysis, Evolution and Reengineering, pages 161–170. IEEE, 2015.

      [16] PharmOut Pty Ltd.Implementation of ansi/aami/iec 62304 medical device software lifecycle processes. https://40rik02ft2xye26xv2i0y0yc-wpengine. netdna-ssl.com/downloads/ white-paper-medical-device-software-lifecycle-processes. Pdf, 2016.

      [17] QA Systems. Achieving en 50128 compliance with qa.c and qa.c++. https://www.qa-systems.de/ressourcen/details/ achieving-en-50128-compliance-with-qa-c-and-qa-c.

      [18] Reactive Systems. Achieving iso26262 compliance with reac-tis. http://www.reactive-systems.com/papers/iso-26262. Pdf, 2015.

      [19] L. Torri, G. Fachini, L. Steinfeld, V. Camara, L. Carro, and E. Cota. An evaluation of free/open source static analysis tools applied to embedded software. In 11th Latin American Test Workshop, pages 1–6. IEEE, 2010.

      [20] D. D. Ward. Misra standards for automotive software. In The 2nd IEE Conference on Automotive Electronics, pages 5–18. IEEE, 2006.

      [21] J. Westman and M. Nyberg. Extending contract theory with safety integrity levels. In IEEE 16th International Symposium on High Assurance Systems Engineering, pages 85–92. IEEE, 2015.

  • Downloads

  • How to Cite

    Chaya Addagarrala, K., & Kinnicutt, P. (2018). Safety critical software ground rules. International Journal of Engineering & Technology, 7(2.28), 344-350. https://doi.org/10.14419/ijet.v7i2.28.13209

    Received date: 2018-05-23

    Accepted date: 2018-05-23

    Published date: 2018-05-16