An Empirical Software Reliability Growth Model for Identification of True Failures
Jagadeesh Medapati1, Anand Chandulal Jasti2, Ranajikanth TV3

1Jagadeesh Medapati, Department of Computer Science and Engineering, GITAM University, Visakhapatnam, (Andhra Pradesh), India.
2Anand Chandulal Jasti, Department of Computer Science and Engineering, GITAM University, Visakhapatnam, (Andhra Pradesh), India.
3Ranajikanth TV, Department of Computer Science and Engineering, Srinidhi Institute of Technology, Hyderabad, (Telangana), India.

Manuscript received on 02 July 2019 | Revised Manuscript received on 05 July 2019 | Manuscript published on 30 August 2019 | PP: 1-5 | Volume-8 Issue-10, August 2019 | Retrieval Number: I8756078919/2019©BEIESP | DOI: 10.35940/ijitee.I8756.0881019
Open Access | Ethics and  Policies | Cite | Mendeley | Indexing and Abstracting
© The Authors. Blue Eyes Intelligence Engineering and Sciences Publication (BEIESP). This is an open access article under the CC-BY-NC-ND license (

Abstract: Software Reliability is a special topic of software engineering that deals with the finding of glitches during the software development. Effective analysis of the reliability helps to understand the quality of the software. It also helps to reveal the number of failures occurred in development phase which facilitates refinement of the failures in the developed software’s. If the failures are not minimized the number of reviews in the software development process increases which in turn increase the expenditure to develop the software. Every software organization aims at releasing the software in time and also it becomes a mandate to manage the software such that the time to release the software is optimized. It becomes a mandate for any organization to release software patches so as to minimize the errors after software release and thereby if the number of patches increases, the credibility of the software together with the storage area will be at stake. This article presents a novel case study wherein a procedural layout is presented such that the number of failures can be reduced instantaneously and the failures are identified at the early stage. The development procedure laid in this article helps to formulate a basis for the distinction between true failures and non-failures. The work is presented using benchmark datasets and the results showcase a better recognition rate and failure deduction rate. 
Keywords: Gamma Distribution, Quality Metrics, Software Engineering, Software Reliability
Scope of the Article: Software Engineering