Proceedings of ISSRE '96: 7th International Symposium on Software Reliability Engineering
DOI: 10.1109/issre.1996.558785
|View full text |Cite
|
Sign up to set email alerts
|

Error injection aimed at fault removal in fault tolerance mechanisms-criteria for error selection using field data on software faults

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Publication Types

Select...
3
3

Relationship

0
6

Authors

Journals

citations
Cited by 14 publications
(5 citation statements)
references
References 19 publications
0
5
0
Order By: Relevance
“…In the last decade, a framework has been formulated for rigorous evaluation of computer systems with emphasis on software faults, namely dependability benchmarking, which has been used for comparisons between systems and for risk assessment [5,13]. Fault injection has also been used for fault removal in fault tolerance mechanisms [3,21].…”
Section: Background and Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…In the last decade, a framework has been formulated for rigorous evaluation of computer systems with emphasis on software faults, namely dependability benchmarking, which has been used for comparisons between systems and for risk assessment [5,13]. Fault injection has also been used for fault removal in fault tolerance mechanisms [3,21].…”
Section: Background and Related Workmentioning
confidence: 99%
“…Figure 3 shows the Apache configuration adopted in this work. Apache Web Server 3 2) depicts the number of injected faults resulting in a failure outcome. For failure outcomes, we further investigate Apache logfiles to identify the presence of log entries (two rightmost columns of Table 2).…”
Section: Apache Web Servermentioning
confidence: 99%
“…Second, injection of faults and errors in memory at arbitrary time does not reflect the characteristics of software faults, which are permanent design/implementation faults into the source code. [13], [21] Subsequent works pursued error injection by (i) designing a formal framework for error injection experiments, (ii) corrupting the memory state using a realistic error model, and (iii) triggering error injection every time that a target sourcecode statement (supposed to be faulty) is executed [9], [12], [22]. Error injection techniques are convenient in terms of time and efforts devoted to experiments.…”
Section: Related Workmentioning
confidence: 99%
“…However, FTMs in critical systems have to undertake a thorough assessment before acceptance, which can be achieved by means of Software Fault Injection (SFI). By deliberate injection of software faults, fault tolerance can be tested and potentially improved [9], [10]; SFI is also useful to assess the impact of software faults on the system during the operational phase [11].…”
Section: Introductionmentioning
confidence: 99%
“…In [6] is reported that six error types accounted for nearly 80% of the highest severity defects. Nine error types accounted for about 80% of the defects exposed by recovery procedures or exception handlers.…”
Section: % or 22%mentioning
confidence: 99%