On Some Statistical Aspects of Software Testing and Reliability

Coolen, Frank P. A.

doi:10.1007/978-3-642-30662-4_7

Cited by 2 publications

(1 citation statement)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Many methods to guide such testing have been presented in the literature, see e.g. Wooff et al, 16 and Coolen, 17 but there has been little attention for the question whether or not simultaneous testing is suitable. In software testing scenarios with high potential risk, testing will typically be performed in a controlled environment, for example testing a prototype that is not actually linked to the system that would possibly be at risk, or the application where severe consequences of test failure could become reality.…”

Section: Discussionmentioning

confidence: 99%

Maximum group sizes for simultaneous testing in high potential risk scenarios

Coolen

2013

Proceedings of the Institution of Mechanical Engineers, Part O:

View full text Add to dashboard Cite

When tests are performed in scenarios such as reliability demonstration, two extreme possibilities are to perform all required tests simultaneously or to test all units sequentially. From the perspective of time for testing, the former is typically preferred, but in high potential risk scenarios, for example in the case of possibly disastrous results if a tested unit fails, it is better to have the opportunity to stop testing after a failure occurs. An analogon appears in medical testing, with patients being the 'units', if new medication is to be tested to confirm its functionality while possibly severe (side) effects are not yet known. There is a wide range of test scenarios in between these two extremes, with groups of units being tested simultaneously. This article discusses such scenarios in a basic setting, assuming that the total number of required tests has been set, for example based on other criteria or legislation. A new criterion for guidance on suitable test group sizes is presented. Throughout, the aim is for high reliability, with testing stopped in case any unit fails, following which the units will not be approved. Any consecutive actions, such as improvement of the units or dismissing them, are not part of the main considerations in this article. While in practice the development of complex models and decision approaches may appear to be required, a straightforward argument is presented, which leads to results that can be widely applied and easily communicated.

show abstract

Section: Discussionmentioning

confidence: 99%