Software reliability for agile testing

Willem Dirk van Driel (Corresponding author), Jan Willem Bikker, Matthijs Tijink, Alessandro Di Bucchianico

Research output: Contribution to journalArticleAcademicpeer-review

8 Citations (Scopus)


It is known that quantitative measures for the reliability of software systems can be derived from software reliability models, and, as such, support the product development process. Over the past four decades, research activities in this area have been performed. As a result, many software reliability models have been proposed. It was shown that, once these models reach a certain level of convergence, it can enable the developer to release the software and stop software testing accordingly. Criteria to determine the optimal testing time include the number of remaining errors, failure rate, reliability requirements, or total system cost. In this paper, we present our results in predicting the reliability of software for agile testing environments. We seek to model this way of working by extending the Jelinski-Moranda model to a "stack" of feature-specific models, assuming that the bugs are labeled with the features they belong to. In order to demonstrate the extended model, two use cases are presented. The questions to be answered in these two cases are: how many software bugs remain in the software and should one decide to stop testing the software?.

Original languageEnglish
Article number791
Number of pages14
Issue number5
Publication statusPublished - 1 May 2020


  • Agile software testing
  • Goel-Okumoto model
  • Jelinski-Moranda model
  • Software reliability


Dive into the research topics of 'Software reliability for agile testing'. Together they form a unique fingerprint.

Cite this