Fault injection spot-checks computer system dependability

Carreira, João; Costa, D.; Silva, João Gabriel

doi:10.1109/6.780999

Cited by 46 publications

(20 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Numerous techniques have been proposed [3], ranging from i) simulation-based techniques at various levels of representation of the target system (technological, logical, RTL, PMS, etc. ), ii) hardware techniques (e.g., pin-level injection, heavy-ion radiation, EMI, power supply alteration, etc.…”

Section: Fault Injection-based Experimental Assessmentmentioning

confidence: 99%

From experimental assessment of fault-tolerant systems to dependability benchmarking

Arlat

2002

Proceedings 16th International Parallel and Distributed Processing Symposium

View full text Add to dashboard Cite

show abstract

Section: Fault Injection-based Experimental Assessmentmentioning

confidence: 99%

From experimental assessment of fault-tolerant systems to dependability benchmarking

Arlat

2002

Proceedings 16th International Parallel and Distributed Processing Symposium

View full text Add to dashboard Cite

show abstract

“…Fault injection with software was initially introduced to emulate hardware faults, an approach commonly referred to as Software Implemented Hardware Fault Injection [10]. However, when performing FMEA on software components, it is interesting to consider failure modes caused by programming (or configuration) faults.…”

Section: Software Fmeamentioning

confidence: 99%

“…Fault-tolerance of the final system is often demonstrated by hardware fault injection and intentional corruption of inputs or memory [10]. This process can be regarded as the testing of the mechanisms designed during the FMEA process, but can also serve as an automated way to discover the effects of different faults.…”

Section: Failure Mode and Effects Analysismentioning

confidence: 99%

Model Checking-based Software-FMEA: Assessment of Fault Tolerance and Error Detection Mechanisms

Molnár

Majzik

2017

Period. Polytech. Elec. Eng. Comp. Sci.

View full text Add to dashboard Cite

Failure Mode and Effects Analysis (FMEA) is a systematic IntroductionThe risk of failure is one of the main concerns of safetycritical systems. Certification requires the systematic analysis of potential failures, their causes and effects, and the evaluation of risk mitigation techniques used to reduce the chance and the severity of system-level failures.One of the first systematic techniques for failure analysis was Failure Mode and Effect Analysis (FMEA) [2]. FMEA is often the first step in reliability analysis, as it collects the potential failure modes of subsystems, their root causes and their effects on the whole system. Together with criticality analysis (often treated as part of FMEA, sometimes emphasized by the term FMECA), the output of FMEA serves as the basis of other qualitative and quantitative analyses, as well as design decisions regarding risk mitigation techniques.FMEA is usually applied at the hardware and communication level, where it requires a qualified analyst to collect postulated component failures and identify their effects on other components and the system level. In case of software (SW-FMEA), failure modes originate in different types of programming faults, commonly referred to as bugs. Due to the complex nature of software and the many types of potential bugs, it is much harder to collect failure modes and deduce their potential effects, so an automated mechanism is desired. This paper presents a way of automated SW-FMEA with the use of executable software models. Assuming a set of predefined fault types (programming faults) and a specification of safe behavior at the system level, the proposed approach applies model checking to systematically generate execution traces leading from fault activations to states that violate the specification of safe behavior (system-level failures). These traces can be used to understand and demonstrate fault propagation through the system and also as test sequences to reveal actual faults in the final product.Our approach improves existing model checking-based SW-FMEA by optimizing fault activations and using monitor components instead of a formal specification. The optimization helps in scaling the solution to apply it on more complex systems and situations, whereas using a monitor instead of formal

show abstract

“…By definition, fault injection corresponds to artificial insertion of faults into a real target system [17]. A fault injection campaign is characterized by its goal, the system under investigation, and the input and output domains.…”

Section: Experimental Evaluation Of Error Detection Capabilitiesmentioning

confidence: 99%

Error Detection in Control Flow of Event-Driven State Based Applications

Pintér

Majzik

2007

Series on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

This chapter presents two runtime error detection techniques for UML 2.0 statechart implementations. The first technique aims at detecting errors caused by model refinement faults (introduced in early phases of the development) by proposing a temporal logic language to be used for defining and checking temporal correctness criteria on statecharts. The second solution is a watchdog structure aiming at detection of errors caused by implementation faults. The solutions can detect a subset of errors emerging from operational fault as well.

show abstract

Fault injection spot-checks computer system dependability

Cited by 46 publications

References 0 publications

From experimental assessment of fault-tolerant systems to dependability benchmarking

From experimental assessment of fault-tolerant systems to dependability benchmarking

Model Checking-based Software-FMEA: Assessment of Fault Tolerance and Error Detection Mechanisms

Error Detection in Control Flow of Event-Driven State Based Applications

Contact Info

Product

Resources

About