This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
An Examination of Fault Exposure Ratio
November 1993 (vol. 19 no. 11)
pp. 1087-1094

The fault exposure ratio, K, is an important factor that controls the per-fault hazard rate, and hence, the effectiveness of the testing of software. The authors examine the variations of K with fault density, which declines with testing time. Because faults become harder to find, K should decline if testing is strictly random. However, it is shown that at lower fault densities K tends to increase. This is explained using the hypothesis that real testing is more efficient than strictly random testing especially at the end of the test phase. Data sets from several different projects (in USA and Japan) are analyzed. When the two factors, e.g., shift in the detectability profile and the nonrandomness of testing, are combined the analysis leads to the logarithmic model that is known to have superior predictive capability.

[1] N. Karunanithi, D. Whitley, and Y. K. Malaiya, "Using neural networks in reliability prediction,"IEEE Software, vol. 9, no. 4, pp. 53-59, July 1992.
[2] C. V. Ramamoorthy and F. B. Bastani, "Software reliability: Status and perspectives,"IEEE Trans. Software Eng., vol. SE-8, no. 4, pp. 354-371, Apr. 1982.
[3] J. D. Musaet al., Software Reliability Measurement, Prediction, Application. New York: McGraw-Hill International, 1987.
[4] G. A. Krueger, "Validation and further application of software reliability growth models,"Hewlett Packard J., pp. 75-79, Apr. 1989.
[5] M. Takahashi and Y. Kamayachi, "An empirical study of a model for program error prediction," inProc. 8th Int. IEEE Conf. on Software Engineering, pp. 330-336, Aug. 1985.
[6] T. M. Khoshgoftaar and J. C. Munson, "Predicting software development errors using software complexity metrics,"IEEE J. Selected Areas Commun., vol. 8, pp. 253-261, 1990.
[7] Y. K. Malaiya and P. K. Verma, "Testability profile and approach to software reliability," in M. H. Hamza, Ed.,Advances in Reliability and Quality Control. Acta Press, Dec. 1988, pp. 67-71.
[8] J. D. Musa, "Rationale for fault exposure ratio K,"Software Eng. Notes, vol. 16, no. 3, pp. 78-79, 1991.
[9] A. von Mayrhauser and J. A. Teresinki, "The effects of static code metrics toon dynamic software reliability models," inProc. Symp. on Software Reliability Engineering, pp. 19.1-19.13, Apr. 1990.
[10] J. M. Keables, "Program structure and dynamic models in software reliability: investigation in a simulated environment," Ph.D. dissertation, Illinois Institute of Technology, 1991.
[11] B. Littlewood, "A Bayesian differential debugging model for software reliability," inProc. COMPSAC, Oct. 1980, pp. 511-517.
[12] Y. Nakagawa and S. Hanata, "An error complexity model for software reliability measurement," inProc. Int. Conf. on Software Engineering, 1989, pp. 230-235.
[13] A. von Mayrhauser and J. M. Keables, "A data collection environment for software reliability research," inProc. Int. Symp. on Software Reliability Engineering, 1991, pp. 98-105.
[14] Y. K. Malaiya, A. von Mayrhauser, and P. K. Srimani, "The nature of fault exposure ratio," inProc. Int. Symp. on Software Reliability Engineering(Raleigh, NC, Oct. 1992), pp. 23-32.
[15] Y. K. Malaiya, N. Karunanithi, and P. Verma, "Predictability of software reliability models,"IEEE Trans. Reliability, to be published in Dec. 1992.
[16] M. Ohba and X. M. Chou, "Does imperfect debugging affect software reliability growth," inProc. Int. Conf. on Software Engineering, 1989, pp. 230-235.
[17] W. W. Everett, "An extended execution time software reliability model," inProc. Int. Symp. on Software Reliability Engineering(Raleigh, NC, Oct. 1992), pp. 4-13.
[18] Y. K. Malaiya and S. Yang, "The coverage problem for random testing," inProc. Int. Test Conf., Oct. 1984, pp. 237-242.
[19] E. A. Adams, "Optimizing preventing service to software systems,"IBM J. Res. Devel., vol. 28, pp. 2-14, Jan. 1984.
[20] G. B. Finnelli, "Results of software error-data experiments," inProc. AIAA AHS ASEE Aircraft Design, Systems and Operations Conf., Sept. 1988, pp. 1-5.
[21] P. G. Ryan and W. K. Fuchs, "Partial detectability profiles, inProc. Int. Conf. on CAD, Nov. 1990.
[22] P. M. Misra, "Software reliability analysis,"IBM Syst. J., vol. 22, pp. 262-270, Mar. 1983.
[23] M. Ohba, "Software reliability analysis models,"IBM J. Res. Develop., vol. 21, no. 4, pp. 428-443, July 1984.
[24] N. D. Singpurwalla and R. Soyer, "Assessing software reliability growth using a random coefficient autoregressive process and its ramifications,"IEEE Trans. Software Eng., vol. SE-11, pp. 1456-1464, Dec. 1985.
[25] Y. Tohma, "Structural approach to the estimations of the number of residual software fault based on hypergeometric distribution,"IEEE Trans. Software Eng., vol. 15, pp. 345-355, Mar. 1989.
[26] Y. Tohma, "Parameter estimation of the hypergeometric distribution model for real test/debug data," Tech. Rep. TR 90 1002, Tokyo Institute of Technology, Dep. Computer Sci., 1990.
[27] J. Steben, L. Streletz, and R. Fariello, "Multiprocessing Computer System for Sensory Evoked Potentials and EEG Spectral Analysis for Clinical Neurophysiology Laboratory,"J. Medical Systems, Vol. 9, May/June 1985, pp. 347-363.
[28] L. Naixing and Y. K. Malaiya, "Empirical estimation of fault exposure ratio," Tech. Rep., Dep. Computer Sci., Colorado State Univ., 1993.
[29] Y. K. Malaiya and P. K. Srimani, Eds.,Software Reliability Models: Theoretical Developments, Evaluation and Applications. IEEE Computer Society Press, Dec. 1990.

Index Terms:
fault exposure ratio; per-fault hazard rate; software testing; detectability profile; logarithmic model; predictive capability; software reliability; fault density; program testing; software reliability
Citation:
Y.K. Malaiya, A. von Mayrhauser, P.K. Srimani, "An Examination of Fault Exposure Ratio," IEEE Transactions on Software Engineering, vol. 19, no. 11, pp. 1087-1094, Nov. 1993, doi:10.1109/32.256855
Usage of this product signifies your acceptance of the Terms of Use.