Please use this identifier to cite or link to this item: http://dx.doi.org/10.18419/opus-3535
Authors: Abdulkhaleq, Asim
Wagner, Stefan
Title: A controlled experiment for the empirical evaluation of safety analysis techniques for safety-critical software
Issue Date: 2015
metadata.ubs.publikation.typ: Konferenzbeitrag
metadata.ubs.publikation.source: 19th International Conference on Evaluation and Assessment in Software Engineering (EASE 2015), Nanjing, China
URI: http://nbn-resolving.de/urn:nbn:de:bsz:93-opus-99965
http://elib.uni-stuttgart.de/handle/11682/3552
http://dx.doi.org/10.18419/opus-3535
metadata.ubs.bemerkung.extern: This is the authors' preprint. The copyright is held by ACM.<br>This preprint is also available from: https://www.researchgate.net/publication/274733061 [accessed Apr 13, 2015].
Abstract: Context: Today's safety critical systems are increasingly reliant on software. Software becomes responsible for most of the critical functions of systems. Many different safety analysis techniques have been developed to identify hazards of systems. FTA and FMEA are most commonly used by safety analysts. Recently, STPA has been proposed with the goal to better cope with complex systems including software. Objective: This research aimed at comparing quantitatively these three safety analysis techniques with regard to their effectiveness, applicability, understandability, ease of use and efficiency in identifying software safety requirements at the system level. Method: We conducted a controlled experiment with 21 master and bachelor students applying these three techniques to three safety-critical systems: train door control, anti-lock braking and traffic collision and avoidance. Results: The results showed that there is no statistically significant difference between these techniques in terms of applicability, understandability and ease of use, but a significant difference in terms of effectiveness and efficiency is obtained. Conclusion: We conclude that STPA seems to be an effective method to identify software safety requirements at the system level. In particular, STPA addresses more different software safety requirements than the traditional techniques FTA and FMEA, but STPA needs more time to carry out by safety analysts with little or no prior experience.
Appears in Collections:05 Fakultät Informatik, Elektrotechnik und Informationstechnik



Items in OPUS are protected by copyright, with all rights reserved, unless otherwise indicated.