Software safety: why, what, and how
ACM Computing Surveys (CSUR)
Software reliability: measurement, prediction, application
Software reliability: measurement, prediction, application
Software Reliability Model with Optimal Selection of Failure Data
IEEE Transactions on Software Engineering - Special issue on software reliability
Journey to a mature software process
IBM Systems Journal
Applying Reliability Models to the Space Shuttle
IEEE Software
Software Testability: The New Verification
IEEE Software
The Infeasibility of Quantifying the Reliability of Life-Critical Real-Time Software
IEEE Transactions on Software Engineering
When to Stop Testing for Large Software Systems with Changing Code
IEEE Transactions on Software Engineering
Analysis of error processes in computer software
Proceedings of the international conference on Reliable software
| Hi-index | 0.00 |
Remaining failures, total failures, test time required to attain a given fraction of remaining failures, and time to next failure are useful reliability metrics for: 1) providing confidence that the software has achieved reliability goals; 2) rationalizing how long to test a piece of software; and 3) analyzing the risk of not achieving remaining failure and time to next failure goals. Having predictions of the extent that the software is not fault free (remaining failures) and whether it is likely to survive a mission (time to next failure) provide criteria for assessing the risk of deploying the software. Furthermore, fraction of remaining failures can be used as both a program quality goal in predicting test time requirements and, conversely, as an indicator of program quality as a function of test time expended. We show how these software reliability predictions can increase confidence in the reliability of safety critical software such as the NASA Space Shuttle Primary Avionics Software.