Software Reliability for Agile Testing

Abstract

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?

Reliability and Failures in Solid State Lighting Systems

“…As it is expected, due to the growing maturity level of solid-state lighting products, this trend will once flatten out, the data is fitted with the Goel-Okumoto maturity growth model. This model is well-known for predicting the reliability of software [26]. Eventually, a total number of approximately 130 unique failure modes is to be discovered.…”

Reliability of LED-based Systems

“…As it is expected, due to the growing maturity level of solid-state lighting products, this trend will once flatten out, the data is fitted with the Goel-Okumoto maturity growth model. This model is well-known for predicting the reliability of software [16]. Eventually, a total number of approximately 130 unique failure modes is to be discovered.…”