Software safety: why, what, and how
ACM Computing Surveys (CSUR)
Completeness, robustness, and safety in real-time software requirements specification
ICSE '89 Proceedings of the 11th international conference on Software engineering
Software risk management
Safeware: system safety and computers
Safeware: system safety and computers
Realtime systems
Software engineering for safety: a roadmap
Proceedings of the Conference on The Future of Software Engineering
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Middleware for real-time and embedded systems
Communications of the ACM - Adaptive middleware
Control System Safety Evaluation and Reliability
Control System Safety Evaluation and Reliability
Safety Critical Computer Systems
Safety Critical Computer Systems
Safety critical systems: challenges and directions
Proceedings of the 24th International Conference on Software Engineering
Software Architecture in Practice
Software Architecture in Practice
A Systematic Approach to Software Safety
APSEC '99 Proceedings of the Sixth Asia Pacific Software Engineering Conference
Practical Design of Safety-Critical Computer Systems
Practical Design of Safety-Critical Computer Systems
Software safety: current status and future direction
ACM SIGSOFT Software Engineering Notes
Engineering safety-related requirements for software-intensive systems
Proceedings of the 27th international conference on Software engineering
IEEE Transactions on Software Engineering
A survey of linguistic structures for application-level fault tolerance
ACM Computing Surveys (CSUR)
| Hi-index | 0.00 |
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 development of high-integrity software adopts practices that impose greater rigor on the software development processes. Software safety is a composite of many factors. Existing software quality models like McCall's and Boehm's and ISO 9126 are inadequate in addressing the software safety issues of real time safety-critical embedded systems. At present there does not exist any standard framework that comprehensively addresses the factors, criteria and metrics (FCM) approach of the quality models in respect of software safety. The safety of a software component must be considered within the context of both the overall system of which it is a component and the environment in which this system operates. It is not useful to investigate the safety of a software component in isolation. This paper proposes a new framework for software safety based on the McCall's software quality model that specifically identifies the criteria corresponding to software safety in safety critical applications. The criteria in the proposed software safety framework pertains to system hazard analysis, completeness of requirements, identification of software-related safety-critical requirements, safety-constraints based design, run-time issues management, and software safety-critical testing. This framework is then applied to a prototype safety-critical system viz. a software--based Railroad Crossing Control System (RCCS) to validate its utility.