On input profile selection for software testing

Analyzes the effect of input profile selection on software testing using the concept of a fault detectability profile. The optimality of the input profile during testing depends on factors such as the planned testing effort and the fault detectability profile. To achieve ultra-reliable software, it is preferable to select the test input uniformly among the different input domains. On the other hand, if the testing effort is limited due to cost or schedule constraints, one should test only the highly used input domains. Use of an operational profile is also needed for the accurate determination of operational reliability.<<ETX>>

[1]  Amrit L. Goel,et al.  Software Reliability Models: Assumptions, Limitations, and Applicability , 1985, IEEE Transactions on Software Engineering.

[2]  Pradip K. Srimani,et al.  An Examination of Fault Exposure Ratio , 1993, IEEE Trans. Software Eng..

[3]  Vernon Rego,et al.  A Time/Structure Based Model for Estimating Software Reliability , 1992 .

[4]  Edward N. Adams,et al.  Optimizing Preventive Service of Software Products , 1984, IBM J. Res. Dev..

[5]  Ytzhak H. Levendel.  Improving quality with a manufacturing process , 1991, IEEE Software.

[6]  John D. Musa,et al.  Operational profiles in software-reliability engineering , 1993, IEEE Software.

[7]  Simeon C. Ntafos,et al.  On Required Element Testing , 1984, IEEE Transactions on Software Engineering.

[8]  D. Drake,et al.  Reliability theory applied to software testing , 1987, FJCC.

[9]  Harlan D. Mills,et al.  Engineering software under statistical quality control , 1990, IEEE Software.

[10]  James M. Bieman,et al.  The relationship between test coverage and reliability , 1994, Proceedings of 1994 IEEE International Symposium on Software Reliability Engineering.

[11]  Joseph Robert Horgan,et al.  Reliable software and communication: software quality, reliability, and safety , 1993, Proceedings of 1993 15th International Conference on Software Engineering.

[12]  Paul Piwowarski,et al.  Coverage measurement experience during function test , 1993, Proceedings of 1993 15th International Conference on Software Engineering.

[13]  Phyllis G. Frankl,et al.  An Experimental Comparison of the Effectiveness of Branch Testing and Data Flow Testing , 1993, IEEE Trans. Software Eng..

[14]  Harlan D. Mills,et al.  Cleanroom Software Engineering , 1987, IEEE Software.

[15]  Victor R. Basili,et al.  Analyzing the test process using structural coverage , 1985, ICSE '85.

[16]  M. Trachtenberg.  Why failure rates observe Zipf's law in operational software , 1992 .

[17]  Michael R. Lyu,et al.  A coverage analysis tool for the effectiveness of software testing , 1993, Proceedings of 1993 IEEE International Symposium on Software Reliability Engineering.

[18]  H. Hecht,et al.  Rare conditions and their effect on software failures , 1994, Proceedings of Annual Reliability and Maintainability Symposium (RAMS).

[19]  Muneo Takahashi,et al.  An empirical study of a model for program error prediction , 1985, ICSE '85.

[20]  John D. Musa,et al.  The operational profile in software reliability engineering: an overview , 1992, [1992] Proceedings Third International Symposium on Software Reliability Engineering.

[21]  Victor R. Basili,et al.  Cleanroom Software Development: An Empirical Evaluation , 1987, IEEE Transactions on Software Engineering.