The purpose of this report is to implement the idea of using testability to estimate software reliability. The basic steps involve estimating testability, evaluating how well software was written, and assessing the relationship between testing and usage. Results from these steps along with operational profiles are used to estimate software reliability. This paper describes an application of this method to evaluate the reliability of a real software system of about 6000 lines of executable code and discusses the results of such an estimation. The results are also compared with those obtained by using two reliability growth models.
|
125
|
An evaluation of random testing
– Duran, Ntafos
- 1984
|
|
112
|
Partition testing does not inspire confidence
– Hamlet, Taylor
- 1990
|
|
81
|
PIE: A dynamic failure-based technique
– Voas
- 1992
|
|
58
|
K.: Software Reliability - Measurement, prediction, application
– Musa, Okumoto
- 1987
|
|
56
|
Software Testability: The New Verification
– Voas, Miller
- 1995
|
|
53
|
Estimating the Probability of Failure When Testing Reveals no Failures
– Miller, Morell, et al.
- 1992
|
|
52
|
Mutation Analysis of Program Test Data
– Budd
- 1980
|
|
46
|
Coverage Measurement Experience During Function Test
– Piwowarski, Ohba, et al.
- 1993
|
|
42
|
A semantic model of program faults
– OFFUTT, H
- 1996
|
|
36
|
ATAC: A data flow coverage testing tool for C
– JR, London
- 1992
|
|
28
|
Test set size minimization and fault detection effectiveness: A case study in a space application
– Wong, Horgan, et al.
- 1997
|
|
25
|
CTraps and Pitfalls
– Koenig
- 1989
|
|
23
|
On the use of software artifacts to evaluate the effectiveness of mutation analysis for detecting errors in production software
– DeMillo, Mathur
- 1990
|
|
21
|
An experimental evaluation of data flow and mutation testing
– Offutt, Pan, et al.
- 1996
|
|
21
|
Software Error Analysis: A Real Case Study Involving Real Faults and Mutations
– Daran, Thevenod-Fosse
- 1996
|
|
19
|
On the use of testability measures for dependability assessment
– Bertolino, Strigini
- 1996
|
|
19
|
Software reliability model for modular program structure
– Littlewood
- 1979
|
|
11
|
Reliable software and communication: Software quality, reliability and safety
– Dalal, Horgan, et al.
- 1993
|
|
11
|
Software Reliability Growth Models: Assumptions vs. Reality
– Wood
- 1997
|
|
10
|
On the correlation between code coverage and software reliability
– Frate, Garg, et al.
- 1995
|
|
8
|
On Input Profile Selection for Software Testing
– Li, Malaiya
- 1994
|
|
8
|
Reliability of Systems with Markov Transfer of Control
– Siegrist
- 1988
|
|
7
|
An empirical study of the correlation between code coverage and reliability estimation
– Chen, Lyu, et al.
- 1996
|
|
5
|
Software Trustability
– Howden, Huang
- 1970
|
|
5
|
Ntafos, "An evaluation of random testing
– Duran, C
- 1984
|
|
4
|
Incorporating Code Coverage in the Reliability Estimation for Fault-Tolerant Software
– Chen, Lyu, et al.
- 1997
|
|
3
|
The relation between software test coverage and reliability
– Malaiya, Li, et al.
- 1994
|
|
1
|
A user-oriented reliability model
– Cheung
- 1980
|
|
1
|
Th � ¡ venod-Fosse, “Software error analysis: A real case study involving real faults and mutations
– Daran, P
- 1996
|
|
1
|
An empirical comparison of data flow and mutation based test adequacy criteria,” The
– Mathur, Wong
- 1994
|
|
1
|
Order and difficulty of debugging
– Trachtenberg
- 1983
|
|
1
|
Trends in reliability and test strategies
– Varadan
- 1995
|
