Effort based software reliability model with fault reduction factor, change point and imperfect debugging

  • PDF / 719,701 Bytes
  • 10 Pages / 595.276 x 790.866 pts Page_size
  • 21 Downloads / 207 Views

DOWNLOAD

REPORT


ORIGINAL RESEARCH

Effort based software reliability model with fault reduction factor, change point and imperfect debugging Shozab Khurshid1 • A. K. Shrivastava2



Javaid Iqbal1

Received: 21 May 2018 / Accepted: 16 January 2019 Ó Bharati Vidyapeeth’s Institute of Computer Applications and Management 2019

Abstract The growing need of software’s in almost every sphere of life has increased the demand of producing error free software’s. But producing high quality software needs resources (effort and time). Numerous time and effort based models were developed in literature with the assumptions of imperfect debugging and change point. Where imperfect debugging is the inefficiency of testing team to remove the faults perfectly due to the insufficient understanding of the software and change point as the time where change in fault detection takes place due to change in various strategies. An important attribute having an impact on software reliability is fault reduction factor (FRF) which is defined as the total number of removed faults in proportion to the experienced failures. In this paper, we have proposed a generalized framework to develop effort based software reliability model with FRF, change point and error generation. For the purpose of model validation and parameter estimation, two real datasets have been used. Keywords Software reliability growth model (SRGM)  Non-homogenous poisson process (NHPP)  Imperfect debugging  Testing effort  Change point  Fault reduction factor (FRF) & A. K. Shrivastava [email protected] Shozab Khurshid [email protected] Javaid Iqbal [email protected] 1

University of Kashmir, Srinagar, India

2

Fortune Institute of International Business, New Delhi, Delhi, India

1 Introduction A very significant role is played by software in most of the critical applications. Most of the real life functions can be automated through the use of software and thus their development and designing should be done in a very critical manner so as to prevent it from failures. Software system usually fails because of the fault that is present in them. Testing and debugging is done with the intent to detect and remove the residing faults in the software but it becomes impossible for software developers to launch fault free software’s. Whenever a fault is uncovered during testing, its removal process is carried out. Thus, a software that operates without failures always saves the precious time of its users and no inconvenience in operating the software is felt. This signifies that how much important it is to have a reliable software. Reliability of a software can be stated as the probability of its error free working under a certain environmental condition for some specified period of time [1]. One important factor that has a wide impact on the reliability of the software is FRF [2]. FRF gives the fault-failure relationship. The failures that are experienced by a software need not be equal to the faults that have been detected. FRF is thus defined as the ratio of the total count of the