Reliability Models for Application Software in Maintenance Phase

  • Published : 2008.06.30

Abstract

With growing demand for zero defects, predicting reliability of software systems is gaining importance. Software reliability models are used to estimate the reliability or the number of latent defects in a software product. Most reliability models to estimate the reliability of software in the literature are based on the development lifecycle stages. However, in the maintenance phase, the software needs to be corrected for errors and to be enhanced for the requests from users. These decrease the reliability of software. Software Reliability Growth Models (SRGMs) have been applied successfully to model software reliability in development phase. The software reliability in maintenance phase exhibits many types of systematic or irregular behaviors. These may include cyclic behavior as well as long-term evolutionary trends. The cyclic behavior may involve multiple periodicities and may be asymmetric in nature. In this paper, SGRM has been adapted to develop a reliability prediction model for the software in maintenance phase. The model is established using maintenance data from a commercial shop floor control system. The model is accepted to be used for resource planning and assuring the quality of the maintenance work to the user.

Keywords

References

  1. Abran, A. and Moore, J. W. (2001), Guide to the Software Engineering Body of Knowledge, Trial Version, IEEE Computer Society Press.
  2. ANSI/IEE Standard STD-729 (1991), Glossary of Software Engineering terminology.
  3. Kececioglu, D. (1991), Reliability Engineering Handbook, 2, Prentice-Hall, Englewood Cliffs, N. J.
  4. Lyu, Michael R. (1996), Handbook of Software Reliability Engineering, Los Alamitos, Calif.: IEEE Computer Society Press, New York: McGraw Hill.
  5. Moriguchi, S. (1996), Software Excellence: A Total Quality Management Guide, Productivity Press.
  6. Musa, J., Iannino A., and Okumoto K. (1987), Software Reliability: Measurement, Prediction, Application, McGraw-Hill, New York.
  7. Musa J., Fuoco G., Irving N., Kropfl D, and Juhlin B. (1996), The operational profile. In Lyu MR (ed), Handbook of software reliability engineering, (Mc-Graw-Hill), chapter 5.
  8. Musa, J. D. (1998), Software Reliability Engineering, McGraw-Hill, New York.
  9. Okumoto, K. and Goel A. L. (1980), Optimum Release Time for Software Systems Based on Reliability and Cost Criteria, Journal of Systems and Software, 1, 315-318.
  10. Okamura, H., Tadashi, D., and Shunji, O. (2001), A reliability assessment method for software products in operational phase-Proposal of an accelerated life testing model, Electronics and Communications in Japan, Part 3, 84(8), 25-33.
  11. Yamada, S., Ohba, M., and S. Osaki (1983), S-Shaped Reliability Growth Modeling for Software Error Detection, IEEE Transaction on Reliability, 32(5), 475- 478.
  12. Yamada, S. and Osaki, S. (1985), Cost-Reliability Optimal release policies for software systems, IEEE Trans. on Reliability, 34(5), 422-424.
  13. Yamada, S., Ohtera, H., and Narihisa, H. (1986), Software reliability growth models with testing effort, IEEE Transaction on Reliability, 35(1), 19-23.
  14. Yamada, S., Tanio Y., and Osaki, S. (1989), A software reliability evaluation method during operation phase, Trans IEICE, J72-D-I, 797-803, (in Japanese).
  15. Yamada, S., Kimura, M., and Osaki, S. (1989), A note on software reliability evaluation during operation phase considering testing-effort expenditures, Trans IEICE, J72-D-I, 922-924, (in Japanese).
  16. Yamada, S., Tanio, Y., and Osaki, S. (1991), Software reliability measurement and assessment methods during operation phase and their comparisons, Trans IEICE, J74-D-I, 240-248, (in Japanese).
  17. Yamada, S., Hishitani, J., and Osaki, S. (1993), Software Reliability Growth Model with Weibull Testing Effort: A Model and Application, IEEE Trans. on Reliability, R-42, 100-105.
  18. Yamada, S. (1993), Software reliability measurement during operational phase and its application, Journal of Computer and Software Engineering, 1(4), 389-402.
  19. Tamura, Y., Yamada, S., and Kimura, M. (2003), Electronics and Communications in Japan, Part 3, 86(11), 13-20.