Generic faultloads based on software faults for dependability benchmarking
- 1 January 2004
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 285-294
Abstract
The most critical component of a dependability benchmark is the faultload, as it should represent a repeatable, portable, representative, and generally accepted set of faults. These properties are essential to achieve the desired standardization level required by a dependability benchmark but, unfortunately, are very hard to achieve. This is particularly true for software faults, which surely accounts for the fact that this important class of faults has never been used in known dependability benchmark proposals. This paper proposes a new methodology for the definition of faultloads based on software faults for dependability benchmarking. Faultload properties such as repeatability, portability and scalability are also analyzed and validated through experimentation using a case study of dependability benchmarking of Web-servers. We concluded that software fault-based faultloads generated using our methodology are appropriate and useful for dependability benchmarking. As our methodology is not tied to any specific software vendor or platform, it can be used to generate faultloads for the evaluation of any software product such as OLTP systems.Keywords
This publication has 9 references indexed in Scilit:
- Reproducible dependability benchmarking experiments based on unambiguous benchmark setup descriptions2004
- Benchmarking the dependability of different OLTP systems2004
- Emulation of software faults by educated mutations at machine-code level2003
- Assessment of COTS microkernels by fault injection2003
- A Dependability Benchmark for OLTP Application Environments2003
- An approach towards benchmarking of fault-tolerant commercial systems2002
- Generation of an error set that emulates software faults based on field data2002
- Comparing operating systems using robustness benchmarks2002
- Measuring software dependability by robustness benchmarkingIEEE Transactions on Software Engineering, 1997