Total views : 199

The Research Framework for Quantitative Safety Assessment for Safety-Critical Computer Systems


  • Department of CSE, LENDI Institute of Engineering and Technology, Vizianagaram, Jonnada – 535005, Andhra Pradesh, India
  • Department of CSE, GMRIT, Razam – 532127, Andhra Pradesh, India


Objectives: A safety-critical computer system has to be designed with safety in mind. The purpose of this paper is to identify and assess the safety hazards by using the proposed framework for Safety-Critical Computer Systems (SCCS). Methods/Statistical Analysis: Computer software quality models like McCall’s and Boehm’s were deficient in addressing the basic safety issues of SCCS. This paper proposes another safety model for software safety by adjusting McCall’s product quality model that particularly distinguishes the conditions comparing to software safety in safety-critical applications. The conditions in the proposed software safety model relate to Hazard Analysis distinguishing of Completeness of safety requirements, Safety-critical Design, Coding, and Testing. Findings: The criteria in the proposed software safety model relate to Hazard Analysis (HA) distinguishing of safety requirements, Completeness of safety requirements, Safety-critical Design, Safety-critical Coding, and Safety-critical Testing. The proposed safety model changes the current quality model by presenting different safety criteria’s and metrics in all phases of Software life cycle to assess the software safety. This model was connected to a safety basic Railroad Crossing Control System (RCCS) which is a laboratory prototype and obtained better results in terms of safety. Application/Improvements: This model was connected to a safety basic Railroad Crossing Control System (RCCS) which is a laboratory prototype and obtained better results in terms of safety.


Hazard Analysis (HA), Railroad Crossing Control Systems (RCCS), Safety Metrics, SCCS, Software Safety, Software Development Life Cycle (SDLC)

Full Text:

 |  (PDF views: 165)


  • Raghu Singh. A Systematic Approach to Software Safety.IEEE 1999.
  • Acharyulu PVS, Seetharamaiah P. A Framework for Safety Automation of Safety-Critical Systems Operations. Safety Science. 77 (2015): 133–142. Crossref
  • NASA-STD-8719.13. Software Safety. Washington, USA: Jul 2004.
  • Air France Flight 447 (Crossref).
  • Schmid D. Adaptive Middleware: Middleware for RealTime and Embedded Systems.Commun. ACM. 2002; 45:43–8. Crossref
  • Herman DS. Software Safety and Reliability Basics. Software Safety and Reliability: Techniques, Approaches and Standards of Key Industrial Sectors. Wiley-IEEE Computer Society Press;2000.p. 520.
  • Haifeng Li, Xuyang Xie, Chang Liu. The Model-Based and Bidirectional Software Failure Mode and Effect Analysis Method. International Conference on Reliability, Maintainability and Safety (ICRMS). IEEE 2014.
  • Jacob J. Stadler, Neal J. Seidl. Software Failure Modes and Effects Analysis. IEEE. 2013.
  • Sinda Rebello. Software System Reliability and Safety Assessment: An Extended FMEA Approach. InternationalJournal Reliability and Safety. 2010; 4(4):366–80. Crossref
  • Leveson NG, Turner C. An investigation of the Therac-25 accidents. IEEE Computer. 1993; 18–41.
  • IEEE 100. The Authoritative Dictionary of Standard Terms.IEEE Press; 2000.
  • Leveson NG. Software Safety – Why, What and How. ACM Comput.Surv. 1986; 18 (2):125–163. Crossref
  • John C. Knight. Safety Critical Systems: Challenges and Directions.Proceedings of the 24th International Conference on SE Orlando, Florida. 2002.p. 547 – 50.
  • System Safety Program Requirement. Mil-std-882. 1984.
  • IEEE STD 1228-1994. IEEE Standard for Software Safety Plans. 1994.
  • Huang Xizi.Software Reliability, Safety, Quality Assurance., Beijing, China: Publishing House of Electronics Industry; 2002.
  • Weaver R, Fenn J, Kelly T. A Pragmatic Approach to Reasoning about the Assurance of Safety Arguments. Proceedings of the 8th Australian Workshop on Safety Critical Systems and Software (SCS’03). 2003;.33: 57.
  • Raheja D. A Different Approach to Design Review. In: Reliability Review, American Society for Quality assurance.1982.
  • Raghu Singh, Software Quality: A Tutorial. 1998.
  • Bhansali PV. Software Safety: Current Status and Future Directions, ACM SIGSOFT Software Engineering Notes. 2005 January; 30(1):1. Crossref Crossref2 Crossref3
  • Kristian J. Cruickshank and James Bret Michael, Man-TakShing. A Validation Metrics Framework for Safety-Critical Software-Intensive Systems 2010.
  • James Bret Michael, Man-TakShing, Kristian John Cruickshank, and Patrick James Redmond. Hazard Analysis and Validation Metrics Framework for System of Systems Software Safety. IEEE Systems Journal. 2010; 4(2).
  • Anneliese Andrews, SalwaElakeili, and Salah Boukhris.Fail-safe testgeneration in safety critical systems. IEEE 15th International Symposium on High-Assurance Systems Engineering (HASE). 2014.p. 49–56.
  • Salwa Elakeili. Fail-Safe Test Generation Of Safety Critical Systems. Dissertation Book. University of Denver;, 2015.
  • Srinivas Acharyulu PV, Seetharamaiah P. A Measures and Metrics Framework for Software Safety. ACM SIGSOFT Software Engineering Notes. 2015; 40(1):1–8. Crossref 26. McCall J, Richards P, Walters G. Factors in Software Quality (3 Vols). NTIS AD-A049.1977.p.176.
  • Benswarup Medikonda,.Seetharamaiah P. An Approach to Modeling software safety in Safety-critical systems. Journal of computer Science. 2009; 5(4):311–22.
  • Jayasri Kotti, Seetharamaiah P. A GQM Based Approach towards the Development of Metrics for Software Safety.Journal of Computer Science. 2015; 11(6): Crossref.
  • Jayasri Kotti, Seetharamaiah P. An Experimental Safety Analysis using SFMEA for a Small Embedded Computer Control System. International Journal of Innovations in Engineering and Technology (IJIET). 2016; 7(3): 342–51.
  • Jayasri Kotti, Seetharamaiah P. The Quantitative Safety Assessment and Evaluation for Safety-Critical Computer Systems. ACM SIGSOFT Software Engineering Notes., ACM New York; NY, USA: 2016; 41(1): Crossref.


  • There are currently no refbacks.

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 License.