A Software Release Policy Assuring Reliability for Imperfect Debugging


The Transactions of the Korea Information Processing Society (1994 ~ 2000), Vol. 5, No. 5, pp. 1225-1233, May. 1998
10.3745/KIPSTE.1998.5.5.1225,   PDF Download:

Abstract

An important issue for software developers is to determine when to stop testing the software system and release it to users. Generally the release time is specified by the number of detected faults or the testing time needed to meet the reliability requirement. Software reliability directly depends on the number of remaining or corrected faults. All the detected faults are not always corrected under imperfect debugging environment. We therefore need a new approach to software release policy for imperfect debugging. This paper suggests a software release policy, which guarantees that the reliability requirement has been achieved. The suggested policy is then implemented and illustrated for specific SRGMs.


Statistics
Show / Hide Statistics

Statistics (Cumulative Counts from September 1st, 2017)
Multiple requests among the same browser session are counted as one view.
If you mouse over a chart, the values of data points will be shown.


Cite this article
[IEEE Style]
P. J. Yang and K. Y. Soon, "A Software Release Policy Assuring Reliability for Imperfect Debugging," The Transactions of the Korea Information Processing Society (1994 ~ 2000), vol. 5, no. 5, pp. 1225-1233, 1998. DOI: 10.3745/KIPSTE.1998.5.5.1225.

[ACM Style]
Park Joong Yang and Kim Young Soon. 1998. A Software Release Policy Assuring Reliability for Imperfect Debugging. The Transactions of the Korea Information Processing Society (1994 ~ 2000), 5, 5, (1998), 1225-1233. DOI: 10.3745/KIPSTE.1998.5.5.1225.