A Quality Assurance Model for Airborne Safety-Critical Software


The tragic nature of safety-critical software failure’s consequences makes high quality and extreme reliability requirements in such types of software of paramount importance. Far too many accidents have been caused by software failure error or where such failure/error was part of the problem. Safety-critical software is widely applied in diverse areas, ranging from medical equipment to airborne systems. Currently, the trend in the use of safety-critical software in the aerospace industry is mostly concentrated on avionic systems. While standards for certification and development of safety-critical software have been developed by authorities and the industry, very little research has been done to address safety-critical software quality. In this paper, we study safety-critical software embedded in airborne systems. We propose a lifecycle specially modeled for the development of safety-critical software in compliance with the DO-178B standard and a software quality assurance (SQA) model based on a set of four acceptance criteria that builds quality into safety-critical software throughout its development.

Share and Cite:

Bhuiyan, N. and ElSabbagh, H. (2014) A Quality Assurance Model for Airborne Safety-Critical Software. Journal of Software Engineering and Applications, 7, 162-176. doi: 10.4236/jsea.2014.73018.

Conflicts of Interest

The authors declare no conflicts of interest.


[1] Kornecki, A., Zalewski, J., Ehrenberger, W., Saglietti, F. and Górski J. (2003) Safety of Computer Control Systems: Challenges and Results in Software Development. Annual Reviews in Control, 27, 23-37. http://dx.doi.org/10.1016/S1367-5788(03)00004-X
[2] Jackson, D., Thomas, M. and Millet, L. (2007) Software for Dependable Systems, Sufficient Evidence. Academic Press, Washington DC.
[3] Kornecki, A.J. and Zalewski, J. (2005) Experimental Evaluation of Software Development Tools for Safety-Critical Real-Time Systems. Innovations System Software Engineering, 1, 176-188.
[4] Sakugawa, B., Cury, E. and Yano, E. (2005) Airborne Software Concerns in Civil Aviation Certification. Dependable Computing, 3747, 52-60. http://dx.doi.org/10.1007/11572329_7
[5] Wils, A., Van Baelen, S., Holvoet, T. and De Vlaminck, K. (2006) Agility in the Avionic Software World. Extreme Programming and Agile Processes in Software Engineering, 4044, 123-132.
[6] Rauch, N., Kuhn, E. and Friedrich, H. (2008) Index-Based Process and Software Quality Control in Agile Development Projects. http://goo.gl/RxNXJ
[7] Leveson, N.G., Cha, S.S. and Shimeall, T.J. (1991) Safety Verification of Ada Programs Using Software Fault Trees. IEEE Software, 8, 48-59. http://dx.doi.org/10.1109/52.300036
[8] Redmill, F., Chudleigh, M. and Catmur, J. (1999) System Safety: HAZOP and Software HAZOP. John Wiley & Sons, New York.
[9] Maier, T. (1995) FMEA and FTA to Support Safety Design of Embedded Software in Safety-Critical Systems. Proceedings of the ENCRESS Conference on Safety and Reliability of Software Based Systems, Bruges, 12-15 September 1995.
[10] Cichocki, T. and Górski J. (2000) Failure Mode and Effect Analysis for Safety Critical Systems with Software Components. Computer Safety, Reliability and Security, Lecture Notes in Computer Science, 1943, 382-394.
[11] Elliott, L., Mojdehrakhsh, R., Tsai, W.T. and Kirani, S. (1994) Retrofitting Software Safety in an Implantable Medical Device. IEEE Software, 11, 41-50. http://dx.doi.org/10.1109/52.300036
[12] Wichmann, B. (1999) Guidance for the Adoption of Tools for Use in Safety Related Software Development. Draft Report, British Computer Society, London.
[13] Bowen, J.P., Vilkomir, S.A. and Kapoor, K. (2003) Tolerance of Control-Flow Testing Criteria. Annual International Computer Software and Applications Conference (COMPSAC 2003), Dallas, November 2003, 182-187.
[14] Fisher, M.J. and Cooper, J.D. (1979) Software Quality Management, Petrocelli Books Inc., Princeton.
[15] Reifer, D.J. (1985) State of the Art in Software Quality Management. Reifer Consultants, Torrance.
[16] Rubey, R.J. and Hartwick, R.D. (1968) Quantitative Measurement of Program Quality. ACM National Conference, Las Vegas, 27-29 August 1968, 671-677.
[17] Wulf, W.A. (1973) Programming Methodology. Proceedings of a Symposium on the High Cost of Software, Stanford Research Institute, Menlo Park.
[18] Fagan, M. (1976) Design and Code Inspections to Reduce Errors in Software Development. IBM Systems Journal, 15, 182-211.
[19] Butler, R.W. and Finelli, G.B. (1993) Quantifying the Reliability of Life-Critical Real-Time Software. IEEE Transactions on Software Engineering, 19, 3-12. http://dx.doi.org/10.1109/32.210303
[20] Nagel, P.M. and Skrivan, J.A. (1982) Software Reliability: Repetitive Run Experimentation and Modeling. NASA Contractor Rep. 165836.
[21] Littlewood, B. (1989) Predicting Software Reliability. Philosophical Transactions of the Royal Society, London, 513-526.
[22] ANSI/IEEE (1981) IEEE Standard for Software Quality Assurance Plans. ANSI/IEEE Std 730-1981.
[23] Kumar, C.A. (1994) Excellence in Software Quality. India Infotech Standards, New Delhi.
[24] Manns, T. and Coleman, M. (1998) Software Quality Assurance. Macmillan Education, London.
[25] Johnson, J. (1995) Chaos: The Dollar Drain of IT Project Failures. Application Development Trends, 2, 41-47.
[26] Genuchten, M. (1991) Why Is Software Late? An Empirical Study of Reasons for Delay in Software Development. IEEE Transactions on Software Engineering, 17, 582-590. http://dx.doi.org/10.1109/ 32.210303
[27] Galin, D. (2004) Software Quality Assurance, From Theory to Implementation. Pearson-Addison Wesley, New York.
[28] O’Regan, G. (2002) A Practical Approach to Software Quality. Springer-Verlag, New York.
[29] ElSabbagh, H. (2006) A Quality Assurance Model for Airborne Safety-Critical Software. M.Sc. Thesis, Department of Mechanical and Industrial Engineering, Concordia University, Montreal.

Copyright © 2022 by authors and Scientific Research Publishing Inc.

Creative Commons License

This work and the related PDF file are licensed under a Creative Commons Attribution 4.0 International License.