Modeling Software Multi Up-Gradations with Error Generation and Fault Severity

Raksha Verma,R S Parihar,Subhrata Das

doi:10.33889/ijmems.2018.3.4-030

Raksha Verma, R S Parihar + Show 1 more

Open Access

https://doi.org/10.33889/ijmems.2018.3.4-030

Copy DOI

Abstract

World is moving very fast and with each new step ‘our desire to want something more’ is increasing in all the aspects of lives. Keeping in mind the growing demand of society for highly equipped software; the suppliers tend to come with up-gradations very frequently with the desire to make an impression in the market. Each organization is battling to showcase that their products is an enhanced version. As a result, companies at proper intervals are coming up with innovative functionalities. In order to have an upper hand amongst the competitors; the judgement on apt time of release of a software is utmost sensitive. This decision is majorly governed by company’s expertise in being able to remove all kinds of faults in the software. Development of a multi-release upgraded software reliability growth model is done with regard to trace the upshots of faults in line for the existing software and the one’s remaining in the software at different intervals. This model ascertains the remaining bugs occurred in the software during its operational phase while testing of the new code in other words which occurs in course of addition of new features to the current software. Further, the case of three types of faults existing in the software namely: simple, hard and complex has been incorporated to model the fault removal phenomenon. Data Analysis has been given to support the results.

Highlights

There can be many instances when the testing team may not be able to debug bugs perfectly instead it affects the eventual fault count by either not being able to debug the faults completely or leading to addition of some of new flaws (Aggarwal et al, 2011; Kapur et al, 2010b; Singh et al, 2014c). There is another stream of research which focused on the impact of fault severity within a fault removal process for multi upgraded software
Enormous work has been done in the field of software engineering to model the fault removal process under the concept of multi upgradation with the inclusion of fault severity, imperfect debugging, testing effort and many more (Anand et al, 2015; Garmabaki et al, 2014; Singh et al, 2011)
The test cases executed will be designed in order to gather the discovery or removal of faults due to the added functionality or due to the remaining faults of previous release

Summary

Introduction

There can be many instances when the testing team may not be able to debug bugs perfectly instead it affects the eventual fault count by either not being able to debug the faults completely (i.e. imperfect fault removal phenomenon) or leading to addition of some of new flaws (Aggarwal et al, 2011; Kapur et al, 2010b; Singh et al, 2014c) There is another stream of research which focused on the impact of fault severity within a fault removal process for multi upgraded software. Enormous work has been done in the field of software engineering to model the fault removal process under the concept of multi upgradation with the inclusion of fault severity, imperfect debugging, testing effort and many more (Anand et al, 2015; Garmabaki et al, 2014; Singh et al., 2011). The emphasis is given to model the case of successive releases of software discussed below

Multi-Upgradation Modeling Framework Release I

Conclusion