An Empirical Software Reliability Growth Model for Identification of True Failures

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.

Scrum: An Agile Process Reengineering In Software Engineering

“…ML (Machine Learning), a sub domain of AI, is scientific and statistical analysis of data that can play a vital role in SPM (Software Project Management) as a processing unit of SDLC project planning to produce accurate output [37]. In 2019, Medapati et al [38] presented that procedural based software layout reduced failures by identifying them at early stages.…”

Scrumban: An Agile Integration of Scrum and Kanban in Software Engineering

“…Hence their contribution to Software Engineering Management should be considerable with the ABPR by software development organizations. Scrum is very suitable for software product development while Kanban is suitable for information and work flow management for regular production industries but still flow based approach of Kanban is more convenient than time boxed approach of Scrum [27] ; as procedural system flow reduces software failure by highlighting issues immediately [35] . The combination of Scrum and Lean based Kanban has been found very effective in Software Engineering Management [31] .…”