CFP last date
20 May 2024
Reseach Article

Fault Severity based Multi Up-gradation Modeling considering Testing and Operational Profile

by Adarsh Anand, Ompal Singh, Subhrata Das
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 124 - Number 4
Year of Publication: 2015
Authors: Adarsh Anand, Ompal Singh, Subhrata Das
10.5120/ijca2015905441

Adarsh Anand, Ompal Singh, Subhrata Das . Fault Severity based Multi Up-gradation Modeling considering Testing and Operational Profile. International Journal of Computer Applications. 124, 4 ( August 2015), 9-15. DOI=10.5120/ijca2015905441

@article{ 10.5120/ijca2015905441,
author = { Adarsh Anand, Ompal Singh, Subhrata Das },
title = { Fault Severity based Multi Up-gradation Modeling considering Testing and Operational Profile },
journal = { International Journal of Computer Applications },
issue_date = { August 2015 },
volume = { 124 },
number = { 4 },
month = { August },
year = { 2015 },
issn = { 0975-8887 },
pages = { 9-15 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume124/number4/22089-2015905441/ },
doi = { 10.5120/ijca2015905441 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T23:13:27.690933+05:30
%A Adarsh Anand
%A Ompal Singh
%A Subhrata Das
%T Fault Severity based Multi Up-gradation Modeling considering Testing and Operational Profile
%J International Journal of Computer Applications
%@ 0975-8887
%V 124
%N 4
%P 9-15
%D 2015
%I Foundation of Computer Science (FCS), NY, USA
Abstract

For sustaining in the era of globalization, frequent up-gradation in the software is demanded. In order to maintain the competitive edge firms come up with highly reliable versions. For providing high reliability firms have to test software rigorously that requires debugging the software in the testing as well as in the operational phase. Upgrading the software leads to the enlarged complexity in the system which often results in the increase number of faults content. In this paper, a framework for successive releases is modeled which incorporates the fault of the present release and faults from the just previous release informed by the users. The approach provides a more realistic perspective of fault evaluation by taking into consideration both; the faults from the testing of new releases and the reported faults from the operational phase of the preceding releases. We have examined the case when there exists two types of faults in the software; simple and hard faults during testing and operational phase. Further we have compared our proposition with the previous developed models in the field of multi up-gradation.

References
  1. Aggarwal, A.G., Kapur, P.K., and Garmabaki, A.S. 2011. Imperfect Debugging Software Reliability Growth Model for Multiple Releases, Proceedings of the 5th National Conference on Computing for Nation Development-INDIACOM, New Delhi.
  2. Anand, A., Singh, A., Kapur, P. K., and Das, S. 2014. Modeling Conjoint Effect of Faults Testified from Operational Phase for Successive Software Releases, Proceedings of the 5th International Conference on Life Cycle Engineering and Management (ICDQM), PP 83-94.
  3. Cuong, N. H., Thang, H. Q., and Trieu, L. H. 2014. Different Ranking of NHPP Software Reliability Growth Models with Generalised Measure and Predictability, International Journal of Applied Information Systems, 7(11).
  4. Garmabaki A. H. S., Aggarwal A.G., Kapur P. K., and Yadavali V. S. S., “The Impact of Bugs Reported from Operational Phase on Successive Software Releases”, International Journal of Productivity and Quality Management, 2014, volume 14, number 4, pp 423-440.
  5. Goel, A.L., and Okumoto, K. 1979. Time-dependent Error Detection Rate Model for Software Reliability and other Performance Measures, IEEE Trans. on Reliability, vol. 28, no. 3, pp. 206–211.
  6. Hower, R. What are some recent major computer system failures caused by software bugs? http://www.softwareqatest.com/qatfaq1.html, (February 2015).
  7. Kapur, P.K, Tandon, A., and Kaur, G. 2010. Multi Up-gradations Software Reliability Model, ICRESH, 468-474.
  8. Kapur P. K., Singh O., Garmabaki A. and Singh J., “Multi up-gradation software reliability growth model with imperfect debugging”, International Journal of systems Assurance Engineering and Management, 2010, 1(4), 299-306.
  9. Kapur, P. K., Anand, A., and Singh, O. 2011. Modeling Successive Software Up-Gradations with Faults of Different Severity, Proceedings of the 5th National Conference on Computing For Nation Development, ISSN 0973-7529 ISBN 978-93-80544-00-7.
  10. Kapur, P.K., Pham, H., Gupta, A., and Jha, P.C. 2011. Software reliability Assessment with OR application, Springer London.
  11. Pham, H. 2006. System Software Reliability, Springer-Verlag.
  12. Sharma, K., Garg, R., Nagpal, C. K. and Garg, R. K. 2010. Selection of Optimal Software Reliability Growth Models Using a Distance Based Approach, IEEE Transactions on Reliability, vol. 59(2).
  13. Singh, O., Kapur, P.K., Anand, A. and Singh, J. 2009. Stochastic Differential Equation based Modeling for Multiple Generations of Software, Proceedings of Fourth International Conference on Quality, Reliability and Infocom Technology (ICQRIT), Trends and Future Directions, Narosa Publications, pp. 122-131.
  14. Singh, O., Kapur, P.K., and Anand, A. 2011. A Stochastic Formulation of Successive Software Releases with Fault Severity. Industrial Engineering and Engineering Management, 136-140.
  15. Singh, O., Kapur, P.K., Khatri, S.K., and Singh, J.N.P. 2012. Software Reliability Growth Modeling for Successive Releases. proceeding of 4th International Conference on Quality, Reliability and Infocom Technology (ICQRIT), PP 77-87.
  16. Yamada, S., Ohba, M., and Osaki, S. 1984. S-shaped Software Reliability Growth Models and their Applications. IEEE Trans. on Reliability, vol. 33, no. 4, pp. 289–292.
  17. Wood, A. 1996. Predicting Software Reliability. IEEE Computer (11) 69-77.
Index Terms

Computer Science
Information Sciences

Keywords

Fault Severity Multi Release Operational Phase Testing Phase.