CFP last date
20 May 2024
Call for Paper
June Edition
IJCA solicits high quality original research papers for the upcoming June edition of the journal. The last date of research paper submission is 20 May 2024

Submit your paper
Know more
The week's pick
Responsive image
Enhancing Privacy Preservation: Multi-Attribute Protection with P-Sensitive K-Anonymity

Twinkle Patel Kiran Amin
Random Articles
Reseach Article

Optimal Software Release Time Policy using Goal Programming

by Sanjeev Kumar, Sachin Gupta, Deepak Tyagi
journal cover thumbnail

International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 102 - Number 9
Year of Publication: 2014
Authors: Sanjeev Kumar, Sachin Gupta, Deepak Tyagi
10.5120/17843-8744

Sanjeev Kumar, Sachin Gupta, Deepak Tyagi . Optimal Software Release Time Policy using Goal Programming. International Journal of Computer Applications. 102, 9 ( September 2014), 17-22. DOI=10.5120/17843-8744

@article{ 10.5120/17843-8744,
author = { Sanjeev Kumar, Sachin Gupta, Deepak Tyagi },
title = { Optimal Software Release Time Policy using Goal Programming },
journal = { International Journal of Computer Applications },
issue_date = { September 2014 },
volume = { 102 },
number = { 9 },
month = { September },
year = { 2014 },
issn = { 0975-8887 },
pages = { 17-22 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume102/number9/17843-8744/ },
doi = { 10.5120/17843-8744 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T22:32:40.172748+05:30
%A Sanjeev Kumar
%A Sachin Gupta
%A Deepak Tyagi
%T Optimal Software Release Time Policy using Goal Programming
%J International Journal of Computer Applications
%@ 0975-8887
%V 102
%N 9
%P 17-22
%D 2014
%I Foundation of Computer Science (FCS), NY, USA
Abstract

In this paper, the impact of software testing effort and the efficiency on the modeling of software reliability for optimizing the cost in case of release time policy has been discussed. Another important problem in the software development process is to determine when to stop testing and release the software. If testing is stopped too early, there may be too many defects in the software, resulting in too many failures during the operation and leading to significant losses. If too much time is spend on testing, there may be a high testing cost. Therefore, there must be a tradeoff between testing and releasing. The release time should be determined by the testing process, efforts and cost. The more defects have been detected and removed, the less time will be used for further testing. To eliminate this problem of releasing the software goal programming approach has been discussed.

References
  1. Aggarwal K. K, Singh Yogesh, "Software Engineering". (2001) New Age International Publishers.
  2. Cai, X. and Lyu, M. R. (2004), An Empirical Study on Reliability and Fault Correlation Models for Diverse Software Systems, in Proceedings 15th International Symposium on Software Reliability Engineering, Saint-Malo, France, pp. 125-136.
  3. Chen, M. H. , Lyu, M. R. , and Wong, E. (2001), Effect of Code Coverage on Software Reliability Measurement, IEEE Transactions on Reliability Vol. 50, No. 2, pp. 165-170.
  4. Goel. A. L, Okumoto K. (1979)"Time dependent error detection rate model for software reliability and other performance measures" IEEE Transactions on Reliability; R-28(3): 206-211.
  5. Gokhale, S. S. , Philip, T. , Marinos, P. N. and Trivedi, K. S. (1996), Unification of Finite Failure Non- Homogeneous Poisson Process Models through Test Coverage, Technical Report, Center for Advanced Computing and Communication, Department of Electrical and Computer Engineering, Duke University.
  6. Gokhale, S. , Wong W. E. , Trivedi, K. S. and Horgan, J. R. (1998), An Analytical Approach to Architecture-Based Software Reliability Prediction, IEEE International, Computer Performance and Dependability Symposium, Durham, NC, pp. 13-19.
  7. Guillermo, N. and Manic, M. (2006), Fuzzy performability analysis of disk arrays, International Symposium on Industrial Electronics, pp. 9-13.
  8. Huang, C. Y. , Kuo, S. Y. and Lyu, M. R. (2001), A Framework for Modeling Software Reliability Considering Various Testing Efforts and Fault Detection Rates, IEEE Transactions on Reliability, Vol. 50,No. 3, pp. 310-321
  9. Hudson, G. R. (1967), Program Errors as Birth and Death Process, Tech. report SP-3011, System Development Corp.
  10. Huo R. H, Chen I. Y, Cheng. Y. P, Kuo. S. Y,(1996) "Optimal Release Policies for Hyper- Geomertic Distribution Software reliability growth model, " IEEE Tran. Rel. , vol 45, no. 4 pp 646-651 Dec. 1996.
  11. Jelinski Z, Moranda PB. "Software reliability research" In: Freiberger W, (Ed. ) Statistical Computer Performance Evaluation 1972; New York: Academic Press: 465-497.
  12. Kapur P. K. , AggarwalS. , Garg R. B. ( 1984. ), "Bi-criterian Release Policy for Exponential Software Reliability Growth Models ", Operational Research, vol 28,pp 165-180,
  13. Kapur PK, Garg RB, Kumar S. (1999) "Contributions to hardware and software reliability"
  14. Kapur PK, Garg RB. "A software reliability growth model for an error removal phenomenon" Software Engineering Journal 1992; 7: 291-294.
  15. Khaled, M. S. (2009), What is Hampering the Performance of Software Reliability Models, A Literature review, Proceedings of the International Multi Conference of Engineers and Computer Scientists , Hong Kong, pp. 231-238.
  16. Krishnamurthy, S. and Mathur, A. P. (1997), On the estimation of reliability of a software system using reliability of its components, in Proceedings of the 8th IEEE International
  17. Lee, I. , Tang, D. , Iyer R. K. and Hsueh M. C. (1993), Measurement-Based Evaluation of Operating System Fault Tolerance, IEEE Transactions on Reliability, pp. 238-249.
  18. Littlewood, B. , Abdel-Ghaley, A. A and Chan, P. Y. (1986), Evaluation of Competing Software .
  19. Lyu, M. R. (1996), Handbook of Software Reliability Engineering, IEEE Computer Society measurement, International Journal of Computer Science and Network Security, Vol. 9 No. 6, pp. 23-30.
  20. Lyu,M. R. (2007), Software Reliability Engineering, A Roadmap , in proceedings of international conference on Future of Software Engineering, Washington, pp. 153-170
  21. Mohanta, D. K. (2005), Fuzzy Markov model for determination of fuzzy state probabilities of generating units including the effect of maintenance. IEEE Trans. On Power System, Vol. 20, no. 4, pp. 2117-2124.
  22. Musa, J. D. , Iannino, A. and Okumoto, K. (1987) Software Reliability - Measurement, Prediction, Application, McGraw Hill, New York.
  23. Ohba M. "Software reliability analysis models" IBM Journal of Research and Development 1984; 28: 428-443.
  24. Pham H. "System Software Reliability"(2005); Springer Series in Reliability Engineering. Reliability and its Interdisciplinary Nature.
  25. Piwowarski, P. , Ohba, M. and Caruso, J. (1983), Coverage Measurement Experience During Function Test, in Proceedings of Fifteenth International IEEE Conference on Software Engg. , pp. 387-301.
  26. Schneidewind, N. F. (1972), An Approach to Software Reliability Prediction and Quality Control, Fall Joint Computer Conference, AFIP Press, Montvale, NJ. Vol. 41, pp. 837- 847. Singapore: World Scientific Publishing Co. Ltd.
  27. Smidts, C. and Sova, D. (1999), An Architectural Model for Software Reliability Quantification: Sources of Data, Reliability Engineering and System Safety Vol. 64, pp. 279–290.
  28. Suri, P. K. (2009), Simulator for Risk assessment of software project based on performance Symposium on Software Reliability Engineering, Mexico, pp. 146-145.
  29. Tang, D. and Iyer, R. K. (1992), Analysis and Modeling of Correlated Failures in Multicomputer systems, IEEE Trans. Computers, Vol. 41, No. 5, pp. 567-577.
  30. Taylor, R. and Vander, Hoek A. (2007), Software Design and Architecture: The Once and Future Focus of Software Engineering, International conference on Future of Software Engineering , IEEE-CS Press, pp. 226-243.
  31. Tohma, Y. , Tokunaga, K. , Nagase, S. and Murata, Y. (1989), Structural approach to the estimation of the number of residual software faults base on the hyper-geometric distribution, IEEE Transactions on Software Engineering, Volume SJ2-15, no. 3, pp. 345-355.
  32. Yadav, A. and Khan R. A. (2009), Critical review on software reliability models, International Journal of recent trends in Engineering, Vol 2, No. 3, pp. 114-116.
  33. Yamada H, Ohtera H, and Narihisa H. "Software reliability growth models with testing effort" IEEE Trans. On Reliability 1986; R-35(1): 19-23.
Index Terms

Computer Science
Information Sciences

Keywords

Software release time policy goal programming software testing efforts software defect removal.

Powered by PhDFocusTM