Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Comparison of the FMEA and STPA safety analysis methods: a case study
Lund University, SWE.ORCID iD: 0000-0001-8635-7462
Beer Test Consulting, AUT.
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0003-3818-4442
Lund University, SWE.
2017 (English)In: Software quality journal, ISSN 0963-9314, E-ISSN 1573-1367, p. 1-39Article in journal (Refereed) Epub ahead of print
Abstract [en]

As our society becomes more and more dependent on IT systems, failures of these systems can harm more and more people and organizations. Diligently performing risk and hazard analysis helps to minimize the potential harm of IT system failures on the society and increases the probability of their undisturbed operation. Risk and hazard analysis is an important activity for the development and operation of critical software intensive systems, but the increased complexity and size puts additional requirements on the effectiveness of risk and hazard analysis methods. This paper presents a qualitative comparison of two hazard analysis methods, failure mode and effect analysis (FMEA) and system theoretic process analysis (STPA), using case study research methodology. Both methods have been applied on the same forward collision avoidance system to compare the effectiveness of the methods and to investigate what are the main differences between them. Furthermore, this study also evaluates the analysis process of both methods by using a qualitative criteria derived from the technology acceptance model (TAM). The results of the FMEA analysis were compared to the results of the STPA analysis, which were presented in a previous study. Both analyses were conducted on the same forward collision avoidance system. The comparison shows that FMEA and STPA deliver similar analysis results.

Place, publisher, year, edition, pages
Springer, 2017. p. 1-39
Keywords [en]
Hazard analysis, Safety analysis, Critical systems, Failure mode and effect analysis, System theoretic process analysis
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-15664DOI: 10.1007/s11219-017-9396-0OAI: oai:DiVA.org:bth-15664DiVA, id: diva2:1166953
Note

open access

Available from: 2017-12-17 Created: 2017-12-17 Last updated: 2018-01-13Bibliographically approved

Open Access in DiVA

fulltext(1452 kB)178 downloads
File information
File name FULLTEXT01.pdfFile size 1452 kBChecksum SHA-512
41c1a4c428d8a5969a022bc0b5cafbf49807f949d76992935af79f80facba91f40acd059c8320dd862aa86aa3a386073afae6c273b31f63e1ff2b5790c2f90f4
Type fulltextMimetype application/pdf

Other links

Publisher's full texthttps://link.springer.com/article/10.1007/s11219-017-9396-0

Authority records BETA

Felderer, Michael

Search in DiVA

By author/editor
Sulaman, Sardar MuhammadFelderer, Michael
By organisation
Department of Software Engineering
In the same journal
Software quality journal
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 178 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 166 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf