Jayasri kotti
Abstract
The rapid increase in computer-related technologies puts greater demands on the software-controlled systems. These demands place the software in total control over safety-critical systems. A fault in such a Safety-Critical Computer Systems (SCCS) can result in catastrophic concerns such as loss of life, harm, or equipment damage. In order to detect and prevent such faults, some safety standards, safety analysis and fault-tolerant techniques have been developed. Still, it requires adequate methodologies and frameworks to complete verification of these SCCS. In this work, the software safety is considered into 3 parts: Safety Modeling, Safety Measurement and Safety Management, with assurance lying down to develop high quality software for SCCS. The proposed methodology is SM-Cube (Safety Modeling, Safety Measurement and Safety Management) which is the Safety-Critical Computer Systems concerned. SM-Cube provides a clarified differentiation for assessing and evaluating the safety embedded into the software. SM-Cube consists of required processes and operations for developing SCCS free of faults. This proposed SM-cube has been applied to safety-critical software based Railroad Crossing Control System (RCCS) which is a laboratory prototype. The outcomes of the prototype confirmed that all critical operations have been safe and risk free. The development of the software based on the proposed SM-cube for RCCS have shown a simplified and improved safety-critical operations of the overall system performance
- Knight J.C. 2002.Safety critical systems: challenges and directions. In: ICSE '02: Proceedings of the 24th International Conference on Software Engineering, New York, NY, USA, ACM (2002) 547--550 Google Scholar
Digital Library
- Dunn W.R. 2003. Designing safety-critical computer systems. Computer 36(11) (2003) 40--46 Google ScholarDigital Library
- Basili V.R and Weiss D. 1984. A Methodology for Collecting Valid Software Engineering Data. IEEE Trans. Software Eng. 10 (1984) 728--738. Google ScholarDigital Library
- Basili V.R and Rombach .H.D. 1988. The Tame Project: Towards Improvement-Oriented Software Environments. IEEE Trans. Software Eng. 14 (1988) 758--773. Google ScholarDigital Library
- +SAFE. 2007. A safety extension to CMMIDEV, V1.2. Defence materiel Organization, Australian. Department of Defence. V1.2, 2007.Google Scholar
- McCall J. Richards P. and Walters G . 1977. Factors in Software Quality. 3 Vols. NTIS AD-A049.Google Scholar
- Mil-std-882, 1984. System safety program Requirement. Department of DefenceGoogle Scholar
- Benswarup Medikonda and Seetharamaiah P . 2009. An Approach to Modeling software safety in Safety-critical systems. Journal of computer Science 5(4):311-322,2009. ISSN 1549--3636Google Scholar
- CMMI Product Development Team . 2006. CMMI for Development. Version 1.2 (CMU/SEI-2006-TR- 008, ESC-TR-2006- 08). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.Google Scholar
- Srinivas Acharyulu P.V. and Seetharamaiah P. 2012. A Methodological Framework for Software Safety in Safety Critical Computer Systems .Journal of Computer Science. 1564--1575, 2012Google Scholar
- NASA software safety guidebook 2004. NASA technical standard. Department of Defense. NASASTD-8719.13, 2004. Sandro Bologna and Gustav Dahll. 1997. Safety applications of computer based systems for the process industry, 1997.Google Scholar
- DeLong T, Smith D and Johnson B. 2005. Dependability metrics to assess safety-critical systems. IEEE Transactions on Reliability 54(3) (2005) 498--505.Google Scholar
- Yu Y and Johnson B. 2005. The quantitative safety assessment for safety-critical software. In: Proc. 29th Annual IEEE/NASA Software Engineering Workshop. (2005) 150--162. Google ScholarDigital Library
- MIL-STD- 882D Standard Practice for System Safety. US Department of Defense (DOD), 2000.Google Scholar
- IEC61508: Functional safety for electrical / electronic / programmable electronic safety-related systems. International Electro technical commission (1998).Google Scholar
- Yang yang Yu, Barry W and Johnson . 2006. Safety Assessment for Safety-Critical Systems Including Physical Faults and Design Faults. IEEE Trans. 1-4244-0008-2/06, 2006.Google Scholar
- Ashraf Armoush and Stefan Kowalewski. 2009. Safety Recommendations for Safety-Critical Design Patterns. International Workshop on the Design of Dependable Critical Systems September 15, 2009, Hamburg, Germany.Google Scholar
- Norman Fenton E. and Hari Lawrence. Software Metrics- A rigorous and practical approach. Second Edition, PWS publishing company. Google ScholarDigital Library
- Axelrod, C.W., 2014. Reducing software assurance risks for security-critical and safety-critical systems. Proceedings of the IEEE Long Island Systems, Applications and Technology Conference, May 2-2, IEEE Xplore Press, Farmingdale, pp: 1-6. DOI: 10.1109/LISAT.2014.6845212.Google Scholar
- Chen, L., L. Huang, C. Li, L. Wu and W. Luo, 2014, Design and safety analysis for system architecture: A breeze/ADL-based approach. Proceedings of the IEEE 38th Annual Computer Software and Applications Conference, Jul. 21-25, IEEE Xplore Press, Vasteras, pp: 261--266. DOI: 10.1109/COMPSAC.2014.35. Google ScholarDigital Library
- P.V. Srinivas Acharyulu, P. Seetharamaiah, Safety Science 77 (2015) 133--142, A framework for safety automation of safety-critical systems operationsGoogle ScholarCross Ref
- James Bret Michael, Senior Member, IEEE, Man-Tak Shing, Senior Member, IEEE, Kristian John Cruickshank, and Patrick James Redmond, IEEE SYSTEMS JOURNAL, VOL. 4, NO. 2, JUNE 2010, Hazard Analysis and Validation Metrics Framework for System of Systems Software Safety.Google Scholar
- Ian Dodd, Ibrahim Habli, Reliability Engineering and System Safety 98 (2012) 7-23 Safety certification of airborne software: An empirical studyGoogle ScholarCross Ref
- ISO/IEC. ISO/IEC 9126-1:2001 Software engineering ¿ product quality -- Part 1: Quality model; ISO 2001.Google Scholar
- "10 historical software bugs with extreme consequences". March 19, 2009, IN TECH BLOG.Google Scholar
Index Terms
- The Quantitative Safety Assessment and Evaluation for Safety-Critical Computer Systems
Recommendations
Issues in the application of software safety standards
SCS '05: Proceedings of the 10th Australian workshop on Safety critical systems and software - Volume 55The application of software safety standards as part of the development of safety critical software is usually considered an essential element of any safety program. Yet it is fairly rare for safety practitioners to step back and critically evaluate both ...
A framework for software safety in safety-critical systems
Software for safety-critical systems must deal with the hazards identified by safety analysis in order to make the system safe, risk-free, and fail-safe. Because human lives may be lost and tremendous economic costs may result if the software fails, the ...
Integrated safety analysis of software-controlled critical systems
Software for safety-critical systems must deal with the hazards identified by safety analysis in order to make the system safe, risk-free and fail-safe. Certain faults in critical systems can result in catastrophic consequences such as death, injury or ...
Comments