Postrelease Testing and Software Release Policy for Enterprise-Level Systems

References

• Arora A., Caulkins J. P., Telang R. Research note—Sell first, fix later: Impact of patching on software quality. Management Sci. (2006) 52(3):465–471Link, Google Scholar
• Baskerville R., Levine L., Pries-Heje J., Ramesh B., Slaughter S. How internet software companies negotiate quality. IEEE Comput. (2001) 14(4):51–57Crossref, Google Scholar
• Bass F. M. A new product growth model for consumer durables. Management Sci. (1969) 15(4):215–227Link, Google Scholar
• Berger J. O.Statistical Decision Theory and Bayesian Analysis (1993) (Springer-Verlag, New York) Google Scholar
• Chiu K., Ho J., Huang Y. Bayesian updating of optimal release time for software systems. Software Quality J. (2009) 17(1):99–120Crossref, Google Scholar
• Dalal S. R., Mallows C. L. When should one stop testing software? J. Amer. Statist. Assoc. (1988) 83:872–879Crossref, Google Scholar
• Dalal S. R., Mallows C. L. Some graphical aids for deciding when to stop testing software. IEEE J. Selected Areas Comm. (1990) 8(2):169–175Crossref, Google Scholar
• Ehrlich W., Prasanna B., Stampfel J., Wu J. Determining the cost of a stop-test decision. IEEE Software (1993) 10(2):33–42Crossref, Google Scholar
• Goel A. L. Software reliability models: Assumptions, limitations, and applicability. IEEE Trans. Software Engrg. (1985) SE-11(12):1411–1142Crossref, Google Scholar
• Goel A. L., Okumoto K. Time-dependent error-detection rate model for software and other performance measures. IEEE Trans. Reliability (1979) R-28(3):206–211Crossref, Google Scholar
• Gross N., Stepanek M., Port O., Carey J. Software hell: Glitches cost billions of dollars and jeopardize human lives. How can we kill the bugs? Bussiness Week (1999) December 6):104–118Google Scholar
• McDaid K., Wilson S. P. Deciding how long to test software. Statistician (2001) 50(2):117–134Google Scholar
• Ohba M., Chou X. M. Does imperfect debugging affect software reliability growth? Proc. 11th Internat. Conf. Software Engrg. (1989) (IEEE Computer Society Press, Washington, DC) Google Scholar
• Okumoto K., Goel A. L. Optimum release time for software systems based on reliability and cost criteria. J. Systems Software (1980) 1:315–318Crossref, Google Scholar
• Pham H.Software Reliability (2000) (Springer, Singapore) Google Scholar
• Pham H.System Software Reliability (2006) (Springer, London) Crossref, Google Scholar
• Pham H., Zhang X. Software release policies with gain in reliability justifying costs. Ann. Software Engrg. (1999) 8(1–4):147–166Crossref, Google Scholar
• Rinsaka K., Dohi T. Optimal testing and maintenance design in a software development project. Electronics Comm. Japan, Part 3 (2006) 89(6):953–961Google Scholar
• Singpurwalla N. D. Determining an optimal time interval for testing and debugging software. IEEE Trans. Software Engrg. (1991) 17(4):313–319Crossref, Google Scholar
• Singpurwalla N., Wilson S. Software reliability modeling. Internat. Statist. Rev. (1994) 62(3):289–317Crossref, Google Scholar
• Standish Group International, Inc. Extreme chaos. (2001) . Retrieved July 13, 2011. http://standishgroup.com/sample_research/extreme_chaos.pdfGoogle Scholar
• Thibodeau P. Study: Buggy software costs users, vendors nearly $60B annually. Computerworld (2002) June 25). Retrieved July 13, 2011, http://www.computerworld.com/s/article/72245/Study_Buggy_software_costs_users_vendors_nearly_60B_annuallyGoogle Scholar
• Vienneau R. L. The cost of testing software. Reliability Maintainability Sympos. (1991) Jan. 29–31):423–427Google Scholar
• Wood A. Predicting software reliability. IEEE Comput. (1996) 29(9):69–77Crossref, Google Scholar
• Xie M., Yang B. A Study of the effect of imperfect debugging on software development cost. IEEE Trans. Software Engrg. (2003) 29(4):471–473Google Scholar