Advertisement

Software Reliability Modeling with Impact of Beta Testing on Release Decision

  • Adarsh AnandEmail author
  • Navneet Bhatt
  • Deepti Aggrawal
  • Ljubisa Papic
Chapter
Part of the Management and Industrial Engineering book series (MINEN)

Abstract

Increased dependence of humans on technologies has made it necessary for developing the software with high reliability and quality. This has led to an increased interest of firms toward the development of software with high level of efficiency; which can be achieved by incorporating beta tests for improving and ensuring that the software is safe and completely free from errors. In a software release life cycle, beta testing is the last important step that software developers carry out before they launch new software. Beta testing is a unique testing process that helps software developers to test a software product in different environments before its final release in the market. In this chapter of the book, we develop a SRGM by inculcating the concept of beta testing in the fault removal process to account for situations that might occur when the software is used in diverse environments. This is done to evade the chances of system being failed in the field. Conducting beta tests results in enhancement of software reliability and has been widely acknowledged. Furthermore, we have developed an optimal scheduling model and showed the importance of beta test while determining the general availability time of the software and making the system more cost effective. For validating the accuracy and predictive capability of the proposed model, we analyzed it on real software data set.

Keywords

Software reliability Software release life cycle Beta testing Optimal release scheduling 

Notes

Acknowledgments

The research work presented in this chapter is supported by grants to the first author from University of Delhi, R&D Grant No-RC/2015/9677, and Delhi, India.

References

  1. 1.
    Press Release (2016) Gartner Says Worldwide Security Software Market Grew 3.7 Percent in 2015. http://www.gartner.com/newsroom/id/3377618. Accessed 12 August 2016
  2. 2.
    India IT-BPM Overview (2016) http://www.nasscom.in/indian-itbpo-industry. Accessed 15 June 2016
  3. 3.
    Levenson NG, Turner CS (1993) An investigation of the Therac-25 accidents. Computer 26(7): 18-41Google Scholar
  4. 4.
    Dowson M (1997) The Ariane 5 software failure. Software Engineering Notes 22 (2): 84.Google Scholar
  5. 5.
    Rogerson S (2002) The Chinook helicopter disaster. IMIS Journal 12(2).Google Scholar
  6. 6.
    Charlotte Jee (2015) Top 10 software failures of 2014. http://www.computerworlduk.com/galleries/infrastructure/top-10-software-failures-2014-3599618/. Accessed 15 June 2016
  7. 7.
    Arora A, Caulkins JP, Telang R (2006) Research Note: Sell First, Fix Later: Impact of Patching on Software Quality. Management Science 52(3): 465-471Google Scholar
  8. 8.
    Kapur PK, Pham H, Gupta A, Jha PC (2011) Software Reliability assessment with OR application. Springer, BerlinGoogle Scholar
  9. 9.
    Software release life cycle (2016) https://en.wikipedia.org/wiki/Software_release_life_cycle. Accessed 15 June 2016
  10. 10.
    Pradhan T (2012) All Types of Software Testing. http://www.softwaretestingsoftware.com/all-types-of-software-testing/. Accessed 15 June 2016
  11. 11.
    Kocbek M, Hericko M (2013) Beta Testing of a Mobile Application: A Case Study. SQAMIA 29-34Google Scholar
  12. 12.
    Buskey CD (2005) A Software Metrics Based Approach to Enterprise Software Beta Testing Design. Dissertation, Pace UniversityGoogle Scholar
  13. 13.
    Jiang Z, Scheibe KP, Nilakanta S (2011) The Economic Impact of Public Beta Testing: The Power of Word-of-Mouth. Supply Chain and Information Management Conference Papers: Posters and Proceedings Paper 10Google Scholar
  14. 14.
    Fine MR (2002) Beta testing for better software. John Wiley & Sons, New YorkGoogle Scholar
  15. 15.
    Bla1ze (2016) Snap v3 Beta sees over 11,000 downloads in the first 24 hours. http://crackberry.com/snap-v3-sees-over-11000-downloads-first-24-hours. Accessed 15 June 2016
  16. 16.
    Apple Press Info (2000) Apple Releases Mac OS X Public Beta. http://www.apple.com/pr/library/2000/09/13Apple-Releases-Mac-OS-X-Public-Beta.html. Accessed 15 June 2016
  17. 17.
    Bogdan Popa (2014) Windows 10 Preview Was Installed by 1.5 Million Users. http://news.softpedia.com/news/Windows-10-Preview-Was-Installed-by-1-5-Million-Users-467767.shtml. Accessed 15 April 2016
  18. 18.
    Posts by Gabe Aul (2016) http://blogs.windows.com/bloggingwindows/author/gabeaul/. Accessed 15 June 2016
  19. 19.
    Press Release (2005) Microsoft Windows Vista October Community Technology Preview Fact Sheet. http://www.microsoft.com/presspass/newsroom/winxp/WinVistaCTPFS.mspx. Accessed 15 June 2016
  20. 20.
    Terry Myerson (2015) Hello World: Windows 10 Available on July 29. http://blogs.windows.com/bloggingwindows/2015/06/01/hello-world-windows-10-available-on-july-29/. Accessed 15 June 2016
  21. 21.
    Fester P (2005) A long winding road out of beta. ZDNet. http://www.zdnet.com/article/a-long-winding-road-out-of-beta/. Accessed 15 June 2016
  22. 22.
    BlackBerry Beta Zone (2015) WhatsApp Messenger Bug Reports. https://appworld.blackberry.com/webstore/content/35142896/?lang=en. Accessed 15 June 2016
  23. 23.
    Goel AL, Okumoto K (1979) Time dependent error detection rate model for software reliability and other performance measures. IEEE Trans Reliability 28(3): 206–211Google Scholar
  24. 24.
    Kapur PK, Garg RB, Kumar S (1999) Contributions to hardware and software reliability. World Scientific Publishing Co. Ltd, SingaporeGoogle Scholar
  25. 25.
    Musa JD, Iannino A, Okumoto K (1987) Software reliability: measurement, prediction, applications. McGraw Hill, New YorkGoogle Scholar
  26. 26.
    Yamada S, Ohba M, Osaki S (1984) S-shaped software reliability growth models and their applications. IEEE Trans Reliability 33(4): 289–292Google Scholar
  27. 27.
    Ohba M (1984) Software reliability analysis models. IBM J Res Dev 28: 428–443Google Scholar
  28. 28.
    Okumoto K, Goel AL (1983) Optimal release time for computer software. IEEE Trans Softw Eng SE 9(3): 323–327Google Scholar
  29. 29.
    Yamada S, Osaki S (1987) Optimal Software Release Policies with simultaneous Cost and Reliability Requirements. European Journal of Operational Research 31: 46-51Google Scholar
  30. 30.
    Kapur PK, Agarwal S, Garg RB (1994) Bicriterion release policy for exponential software reliability growth model. Proceedings of the 3rd International Symposium on Software Reliability Engineering 28:165–180Google Scholar
  31. 31.
    Jain M, Handa BR (2001) Cost analysis for repairable units under hybrid warranty. In: M.L. Agarwal, K. Sen, eds. Recent Developments in Operational Research. Narosa Publishing House: New Delhi 149–165Google Scholar
  32. 32.
    Singh O, Kapur PK, Anand A (2012) A Multi Attribute Approach for Release Time and Reliability Trend Analysis of a Software. International Journal of System Assurance and Engineering Management (IJSAEM) 3 (3): 246-254Google Scholar
  33. 33.
    Singh O, Aggrawal D, Kapur PK (2012) Reliability Analysis and Optimal Release Time for a Software using Multi-Attribute Utility Theory. Communications in Dependability and Quality Management -An International Journal 5(1): 50-64Google Scholar
  34. 34.
    Anand A, Agarwal M, Tamura Y, Yamada S (2016) Economic Impact of Software Patching and Optimal Release Scheduling. Quality and Reliability Engineering International. doi: 10.1002/qre.1997
  35. 35.
    Das S, Anand A, Singh O, Singh J (2015) Influence of Patching on Optimal Planning for Software Release & Testing Time. Communication in Dependability and Quality Management: An International Journal 18(4): 82-93Google Scholar
  36. 36.
    Wiper MP, Wilson SP (2006) A Bayesian analysis of beta testing. TEST 15(1): 227-255Google Scholar
  37. 37.
    Mäkinen SJ, Kanniainen J, Peltola I (2014) Investigating Adoption of Free Beta Applications in a Platform‐Based Business Ecosystem. Journal of Product Innovation Management 31(3): 451-465Google Scholar
  38. 38.
    Jiang Z, Sarkar S, Jacob VS (2012) Postrelease testing and software release policy for enterprise-level systems. Information Systems Research 23(3-part-1): 635-657Google Scholar
  39. 39.
    Kanoun K, Martini M, Souza J (1991) A method for software reliability analysis and prediction application to the TROPICO-R switching system. IEEE Trans. on Software Engineering 17 (4): 334–344Google Scholar
  40. 40.
    Huang CY, Lyu MR (2011) Estimation and analysis of some generalized multiple change-point software reliability models. IEEE Transactions on Reliability 60(2): 498-514Google Scholar
  41. 41.
    SAS Institute Inc (2010) SAS/ETS® 9.22 User’s Guide. Cary, NCGoogle Scholar

Copyright information

© Springer International Publishing AG 2017

Authors and Affiliations

  • Adarsh Anand
    • 1
    Email author
  • Navneet Bhatt
    • 1
  • Deepti Aggrawal
    • 2
  • Ljubisa Papic
    • 3
  1. 1.Department of ORUniversity of DelhiNew DelhiIndia
  2. 2.Keshav Mahavidyalaya, University of DelhiNew DelhiIndia
  3. 3.DQM Research CentreCacakSerbia

Personalised recommendations