The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
On Fault Representativeness of Software Fault Injection
Abstract
The injection of software faults in software components to assess the impact of these faults on other components or on the system as a whole, allowing the evaluation of fault tolerance, is relatively new compared to decades of research on hardware fault injection. This paper presents an extensive experimental study (more than 3.8 million individual experiments in three real systems) to evaluate the representativeness of faults injected by a state-of-the-art approach (G-SWFIT). Results show that a significant share (up to 72 percent) of injected faults cannot be considered representative of residual software faults as they are consistently detected by regression tests, and that the representativeness of injected faults is affected by the fault location within the system, resulting in different distributions of representative/nonrepresentative faults across files and functions. Therefore, we propose a new approach to refine the faultload by removing faults that are not representative of residual software faults. This filtering is essential to assure meaningful results and to reduce the cost (in terms of number of faults) of software fault injection campaigns in complex software. The proposed approach is based on classification algorithms, is fully automatic, and can be used for improving fault representativeness of existing software fault injection approaches.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Orthogonal defect classification-a concept for in-process measurements
Chillarege, R., Bhandari, I. S., Chaar, J. K., Halliday, M. J., Moebus, D. S., Ray, B. K., & Wong, M.-Y. (1992) · IEEE Transactions on Software Engineering · doi:10.1109/32.177364 · Cited by 792
Cited by
Challenges in autonomous vehicle testing and validation
Koopman, P., & Wagner, M. (2016) · SAE International Journal of Transportation Safety · doi:10.4271/2016-01-0128 · Cited by 675
Zhang, P., Li, W., Li, S., Wang, Y., & Xiao, W. (2013) · Applied Energy · doi:10.1016/j.apenergy.2012.12.010 · Cited by 265
Quantifying the Accuracy of High-Level Fault Injection Techniques for Hardware Faults
Wei, J., Thomas, A., Li, G., & Pattabiraman, K. (2014) · 2014 44th Annual IEEE/IFIP International Conference on Dependable Systems and Networks · doi:10.1109/dsn.2014.2 · Cited by 182
A survey of AIOps methods for failure management
Notaro, P., Cardoso, J., & Gerndt, M. (2021) · ACM Transactions on Intelligent Systems and Technology · doi:10.1145/3483424 · Cited by 142
Understanding Error Propagation in GPGPU Applications
Li, G., Pattabiraman, K., Cher, C.-Y., & Bose, P. (2016) · SC16: International Conference for High Performance Computing, Networking, Storage and Analysis · doi:10.1109/sc.2016.20 · Cited by 89
Metadata
- Authors
- Natella, R., Cotroneo, D., Duraes, J. A., & Madeira, H. S.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2013-01
- Volume
- 39
- Issue
- 1
- Pages
- 80-96
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2031411490
- Cited by
- 199
- References
- 1
- FWCI
- 70.64
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: On Fault Representativeness of Software Fault Injection. https://app.cochat.ai/papers/10.1109/tse.2011.124
- The paper
- Natella, R., Cotroneo, D., Duraes, J. A., & Madeira, H. S. (2013). On Fault Representativeness of Software Fault Injection. IEEE Transactions on Software Engineering. https://doi.org/10.1109/tse.2011.124
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.