When is the Software Reliability Estimate Reliable?
(1996)- Abstract
- It is of paramount importance that software reliability requirements not only can be formulated, but also enforced and evaluated before accepting a software product for release. This requires sound acceptance criteria for software, which implies that methods for evaluating the software reliability are needed during the testing phase. Thus, theoretical models which are practically applicable are needed. These models should support software procurers in their difficult task of objectively accepting software products prior to releasing them for operation. This paper addresses this issue through studying two possible models for when to stop testing and accepting the software. The models are discussed with one particular software reliability... (More)
- It is of paramount importance that software reliability requirements not only can be formulated, but also enforced and evaluated before accepting a software product for release. This requires sound acceptance criteria for software, which implies that methods for evaluating the software reliability are needed during the testing phase. Thus, theoretical models which are practically applicable are needed. These models should support software procurers in their difficult task of objectively accepting software products prior to releasing them for operation. This paper addresses this issue through studying two possible models for when to stop testing and accepting the software. The models are discussed with one particular software reliability growth model in mind, but the approach can be enlarged to take other software reliability growth models into account. The proposed stopping rules are illustrated on a set of failure data. It is concluded that it is indeed possible to evaluate and hence accept software products based on a software reliability estimate, including confidence in the estimate. (Less)
Please use this url to cite or link to this publication:
https://lup.lub.lu.se/record/b1413eb3-5be5-401a-82e0-4c28fae77bfe
- author
- Wohlin, Claes
LU
; Runeson, Per
LU
and Johansson, Jan-Eric
- publishing date
- 1996
- type
- Chapter in Book/Report/Conference proceeding
- publication status
- published
- subject
- host publication
- Workshop on Issues in Software Reliability
- language
- English
- LU publication?
- no
- additional info
- Fourth Bellcore/KPN/Purdue Workshop on Issues in Software Reliability", Leidschendam, The Netherlands, 1995
- id
- b1413eb3-5be5-401a-82e0-4c28fae77bfe
- date added to LUP
- 2019-03-28 20:29:46
- date last changed
- 2019-04-04 02:16:55
@inproceedings{b1413eb3-5be5-401a-82e0-4c28fae77bfe, abstract = {{It is of paramount importance that software reliability requirements not only can be formulated, but also enforced and evaluated before accepting a software product for release. This requires sound acceptance criteria for software, which implies that methods for evaluating the software reliability are needed during the testing phase. Thus, theoretical models which are practically applicable are needed. These models should support software procurers in their difficult task of objectively accepting software products prior to releasing them for operation. This paper addresses this issue through studying two possible models for when to stop testing and accepting the software. The models are discussed with one particular software reliability growth model in mind, but the approach can be enlarged to take other software reliability growth models into account. The proposed stopping rules are illustrated on a set of failure data. It is concluded that it is indeed possible to evaluate and hence accept software products based on a software reliability estimate, including confidence in the estimate.}}, author = {{Wohlin, Claes and Runeson, Per and Johansson, Jan-Eric}}, booktitle = {{Workshop on Issues in Software Reliability}}, language = {{eng}}, title = {{When is the Software Reliability Estimate Reliable?}}, year = {{1996}}, }