Skip to main navigation Skip to search Skip to main content

Improved NHPP software reliability growth model considering imperfect debugging

  • Beihang University

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

Although there have been a lot of researches on software reliability growth models, the problem that limited considerations of imperfect debugging phenomenon in the existing models is still not solved. In this paper, we aim for such study and propose a new software reliability growth model that connects both faults detective process and faults corrective process in a software test. Faults introduction, time delay, and fault removal efficiency, considered as 3 assumptions to propose an improved NHPP software reliability growth model. Then we choose two different sets of real software data to examine the merit and the predictive power of the new model. The results show that compared with other models, the proposed model provides the best fit, which means it is useful to improve the model.

Original languageEnglish
Title of host publicationProceedings of 2017 International Conference on Management Engineering, Software Engineering and Service Sciences, ICMSS 2017
EditorsYulin Wang
PublisherAssociation for Computing Machinery
Pages59-63
Number of pages5
ISBN (Electronic)9781450348348
DOIs
StatePublished - 14 Jan 2017
Event2017 International Conference on Management Engineering, Software Engineering and Service Sciences, ICMSS 2017 - Wuhan, China
Duration: 14 Jan 201716 Jan 2017

Publication series

NameACM International Conference Proceeding Series

Conference

Conference2017 International Conference on Management Engineering, Software Engineering and Service Sciences, ICMSS 2017
Country/TerritoryChina
CityWuhan
Period14/01/1716/01/17

Keywords

  • Correction process
  • Fault detection process
  • Imperfect debugging
  • Software reliability growth model

Fingerprint

Dive into the research topics of 'Improved NHPP software reliability growth model considering imperfect debugging'. Together they form a unique fingerprint.

Cite this