A Practical Approach to Failure Mode, Effects and Criticality Analysis (Fmeca) for Computing Systems

Becker, J.; Flick, Glenn

doi:10.1002/j.2334-5837.1996.tb01996.x

Cited by 6 publications

(3 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Moreover, FMEA can complement FTA and identify many more failure modes and causes (McDermott et al 2008). Failure modes and effects criticality analysis (FMECA) is an extension to FMEA that ranks the identified failure modes based on their severity, which is used for prioritization of countermeasures (Becker and Flick 1996;MIL-STD-1629A 1980. Another extension is provided by Grunske et al (2007) who introduced an extension to the conventional FMEA, namely "the probabilistic FMEA."…”

Section: Fmeamentioning

confidence: 99%

Comparison of the FMEA and STPA safety analysis methods–a case study

et al. 2017

View full text Add to dashboard Cite

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.

show abstract

Section: Fmeamentioning

confidence: 99%

Comparison of the FMEA and STPA safety analysis methods–a case study

et al. 2017

View full text Add to dashboard Cite

show abstract

“…FTA is a top–down analysis method where undesirable end events are identified and then all contributing factors, determine which failures are most critical, whereas FMEA is a bottom‐up analysis method used to identify each potential failure mode for all the parts in the system and traces negative effects though up the system. Failure Modes and Effects Criticality Analysis is an extension to FMEA where the severity ranking of the failure modes is made and allows prioritisation of countermeasures . Another failure mode method is Healthcare Failure Mode and Effect Analysis developed by the United States Department of Veterans Affairs' National Center for Patient Safety; it is based on multidisciplinary teams, identifying possible failure modes using graphical described healthcare processes .…”

Section: Related Workmentioning

confidence: 99%

Involving user perspective in a software risk management process

Lindholm

2015

J Software Evolu Process

View full text Add to dashboard Cite

More and more user groups are using medical devices. Heart starters are, for example, available in public places and used by non-professionals. Different mobile medical applications, designed to help people manage their own health, are now being added to the medical device spectra. Users handling medical devices make errors, but by involving users in the risk management process, it is possible to lower the risk of these errors. This paper presents an evaluation of the value of complementing a traditional risk management process with an emphasised user perspective. A medical device software risk management framework is being designed, and the risk management process should be regarded as the first part of the framework. The main goal of the evaluated risk management process is to integrate users and user perspective into the risk management process. The results indicate that the use of use cases as input at risk meetings makes the discussions more focused, saving effort and time. When users attend the risk meetings, user perspective and domain knowledge are brought into the process, affecting risk identification and risk assessment. The results also show that the use of usability testing gives valuable input to the risk management process.

show abstract

“…FMECA investigates how the system detects and recovers from failures and analyzes the failure semantics, and criticality of each failure mode [1]. Fig.4 depicts a consequence of errors and failures.…”

Section: Leve Ls Of Data Center Comple Xitymentioning

confidence: 99%