Bitte benutzen Sie diese Kennung, um auf die Ressource zu verweisen: http://dx.doi.org/10.18419/opus-3535
Langanzeige der Metadaten
DC ElementWertSprache
dc.contributor.authorAbdulkhaleq, Asimde
dc.contributor.authorWagner, Stefande
dc.date.accessioned2015-04-16de
dc.date.accessioned2016-03-31T08:02:15Z-
dc.date.available2015-04-16de
dc.date.available2016-03-31T08:02:15Z-
dc.date.issued2015de
dc.identifier.other429864043de
dc.identifier.urihttp://nbn-resolving.de/urn:nbn:de:bsz:93-opus-99965de
dc.identifier.urihttp://elib.uni-stuttgart.de/handle/11682/3552-
dc.identifier.urihttp://dx.doi.org/10.18419/opus-3535-
dc.description.abstractContext: 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.en
dc.language.isoende
dc.rightsinfo:eu-repo/semantics/openAccessde
dc.subject.classificationFMEAde
dc.subject.ddc004de
dc.subject.otherFTA , STPAde
dc.subject.otherFTA , FMEA, STPA , Controlled Experiment , Safety Analysis Techniquesen
dc.titleA controlled experiment for the empirical evaluation of safety analysis techniques for safety-critical softwareen
dc.typeconferenceObjectde
dc.date.updated2015-04-16de
ubs.bemerkung.externThis 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].de
ubs.fakultaetFakultät Informatik, Elektrotechnik und Informationstechnikde
ubs.institutInstitut für Softwaretechnologiede
ubs.opusid9996de
ubs.publikation.source19th International Conference on Evaluation and Assessment in Software Engineering (EASE 2015), Nanjing, Chinade
ubs.publikation.typKonferenzbeitragde
Enthalten in den Sammlungen:05 Fakultät Informatik, Elektrotechnik und Informationstechnik



Alle Ressourcen in diesem Repositorium sind urheberrechtlich geschützt.