Safeware: system safety and computers
Safeware: system safety and computers
ICSE '97 Proceedings of the 19th international conference on Software engineering
Towards integrated safety analysis and design
ACM SIGAPP Applied Computing Review - Special issue on saftey-critical software
Safety critical systems: challenges and directions
Proceedings of the 24th International Conference on Software Engineering
Software Hazard and Safety Analysis
FTRTFT '02 Proceedings of the 7th International Symposium on Formal Techniques in Real-Time and Fault-Tolerant Systems: Co-sponsored by IFIP WG 2.2
Hierarchically Performed Hazard Origin and Propagation Studies
SAFECOMP '99 Proceedings of the 18th International Conference on Computer Computer Safety, Reliability and Security
SCS '04 Proceedings of the 9th Australian workshop on Safety critical systems and software - Volume 47
Automating the failure modes and effects analysis of safety critical systems
HASE'04 Proceedings of the Eighth IEEE international conference on High assurance systems engineering
The right degree of configurability for safety-critical embedded software in variable message signs
SAFECOMP'10 Proceedings of the 29th international conference on Computer safety, reliability, and security
| Hi-index | 0.00 |
Software is an integral part of many technical systems and responsible for the realization of safety-critical features contained therein. Consequently, software has to be carefully considered in safety analysis efforts to ensure that it does not cause any system hazards. Safety engineering approaches borrowed from systems engineering, like Failure Mode and Effect Analysis, Fault Tree Analysis, or Hazard and Operability Studies, have been applied on software-intensive systems. However, in order to be successful, tailoring is needed to the characteristics of software and the concrete application context. Furthermore, due to the manual and expert-dependent nature of these techniques, the results are often not repeatable and address mainly syntactic issues. This paper presents the concepts of a customization framework to support the definition and implementation of project-specific software hazard identification approaches. The key-concepts of the approach, generic guide-phrases, and tailoring concepts to create objective, project-specific support to detect safety-weaknesses of software-intensive systems are introduced.