Towards the Design of Safety-Critical Software

 

R. Rafeh¹, A. Rabiee^1,2

 

^1,2 Department of Computer Engineering Arak University Arak, Iran, r-rafeh@araku.ac.ir.

² Department of IT, Education Organization Arak, Iran. arvand.rabiee@gmail.com.

 

ABSTRACT

Safety is the most important factor when developing software for safety-critical systems. Traditional approaches attempted to achieve safety through testing the software. However, there might be some bugs in the software not revealed in the test procedure. Formal verification is a new trend in developing safe software. In this paper, we propose a multi-phase formal approach for safety management in safety-critical software. We use timed transition Petri-net as a formal means to specify the properties of the model and their relations in each component of the software. In addition, we use the Z language to specify textual and mathematical specifications of the model, as a representative model to evaluate the proposed approach; we chose continuous infusion insulin pump (CIIP).

Keywords: Safety-critical software, hazard, formal languages, CIIP.

 

DESCARGAR ARTÍCULO EN FORMATO PDF

 

References

[1] J. Slagle and S. Shankar, Theorem proving. Chichester, UK: John Wiley and Sons Ltd, 2003.         [ Links ]

[2] C. Baier and J. Katoen, Principles of Model Checking. London, England: Cambridge, Mass. : MIT Press, 2008.         [ Links ]

[3] M. Leucker, "Checking and Enforcing Safety: Runtime Verification and Runtime Reflection," ERCIM News, vol. 75, pp. 35-36, 2008, ERCIM EEIG, Sophia Antipolis Cedex, France.         [ Links ]

[4] S. Smetsers and M. Eekelen, "LaQuSo: Using Formal Methods for Analysis, Verification and Improvement of Safety-Critical Software," ERCIM News, vol. 75, pp. 36-37, 2008, ERCIM EEIG, Sophia Antipolis Cedex, France.         [ Links ]

[5] S Fischmeister and Azim, "A Design Choices for High-Confidence Distributed Real-Time Software," Leveraging Applications of Formal Methods, Verification, and Validation, Lecture Notes in Computer Science, vol. 6416, pp. 97-111, 2010, Springer.         [ Links ]

[6] D Mery and N.K Singh, "Trustable Formal Specification for Software Certification," Leveraging Applications of Formal Methods, Verification, and Validation, Lecture Notes in Computer Science, vol. 6416, pp. 312-326, 2010, Springer.         [ Links ]

[7] I. Sommerville, Software Engineering, 8th ed. China: Pearson Education, 2007.         [ Links ]

[8] S.M. Babamir and M. Borhani, "Formal Verification of Medical Monitoring Software Using Z Language: A Representative Sample," Journal of Medical Systems, 2011, Springer, DOI: 10.1007/s10916-011-9739-5.         [ Links ]

[9] S. Gabriele and W. Werner, "Practical Ways of Improving Product Safety in Industry," Improvements In system Safety, no. 6, pp. 177-193, 2008, Springer, DOI: 10.1007/978-1-84800-100-8_11.         [ Links ]

[10] D. G. Firesmith, "Engineering Safety- and Security-Related Requirements: Tutorial," in 15 IEEE International Requirements Engineering Confencee, New Delhi, India, 2007.         [ Links ]

[11] D. G. Firesmith, "Engineering Safety-Related Requirements for Software-Intensive Systems: Tutorial," in 27th International Conference on Software Engineering (ICSE'2005) in, Louis, Missouri, USA, 2005.         [ Links ]

[12] S. Tucker and M. Halbert, "Risk Assessment for M42 Active Traffic Management," Developments in Risk-Based Approaches to Safety, no. 2, pp. 25-45, 2006, Springer, DOI: 10.1007/1-84628-447-3_2.         [ Links ]

[13] C. A. Ericson, Hazard analysis techniques for system safety. Hoboken, New Jersey, USA: Wiley-Interscience, 2005.         [ Links ]

[14] M.B. Swarup and P. S. Ramaiah, "An Approach to Modeling Software Safety in Safety-Critical Systems," Journal of Computer Science, vol. 5, no. 4, pp. 311-322, 2009.         [ Links ]

[15] R. Patton, Software Testing. Indianapolis, Indiana, USA: Sams, 2001.         [ Links ]

[16] S. Sohn and P. Seong, "A Comprative Study of Formal Methods for Safety Critical Software in Nuclear Power Plant," Journal of the Korean Nuclear Society, vol. 32, no. 6, pp. 537-548, 2000.         [ Links ]

[17] J. M Spivey, The Z Notation: A Reference Manual, 2nd ed. Oxford, UK: Prentice Hall, 2001.         [ Links ]

[18] National Aeronautics and Space Administration, NASA Software Safety Guidebook, NASA-GB-8719.13B. USA: NASA, 2004.         [ Links ]

[19] J. D. Gahl, J. E. DijKstra, and C.A.R. Hoare, Notes on Structured Programming. London, England: Academic Press London, 1972.         [ Links ]

[20] Office of Government Commerce, Intruduction to ITIL. London, Britain: TSO, 2006.         [ Links ]