Successful application of software reliability: A case study

International Journal of Performability Engineering

Volumn 6, Issue 6, 2010, Pages 531-546

  Schneidewind, Norman F ^a  

^a IEEE   (United States)

Author keywords

Institute of Electrical and Electronic engineers and the American Institute of Aeronautics and Astronautics Recommended Practice for Software Reliability; NASA Space Shuttle application; Software reliability program

Indexed keywords

EID: 78651365784     PISSN: 09731318     EISSN: 29938341     Source Type: Journal    
DOI: None     Document Type: Article

References (17)

1. Boehm B. Software Risk Management: Principles and Practices. IEEE Software January 1991; 8(1): 32-41.
2. Dalal S. and A. McIntosh. When to Stop Testing for Large Software Systems with Changing Code. IEEE Transactions on Software Engineering April 1994; 20(4): 318-323.
3. Dalal S. and A. McIntosh. Some Graphical Aids for Deciding When to Stop Testing. IEEE Journal on Selected Areas in Communications February 1990; 8(2):169-175.
4. Ehrlich W., B. Prasanna, John Stampfel, and Jar Wu. Determining the Cost of a Stop-Test Decision. IEEE Software, March 1993:10(2) 33-42.
5. Keller T. and N. Schneidewind. A Successful Application of Software Reliability Engineering for the NASA Space Shuttle. Software Reliability Engineering Case Studies. International Symposium on Software Reliability Engineering, Albuquerque, New Mexico, November 4, 1997: 71-82.
6. Leveson N. Software Safety: What, Why, and How. ACM Computing Surveys June 1986; 18(2):125-163.
7. Lyu M. (Editor-in-Chief), Handbook of Software Reliability Engineering. Computer Society Press, Los Alamitos, CA and McGraw-Hill, New York, NY, 1995.
8. Musa J. and A. Ackerman. Quantifying Software Validation: When to Stop Testing? IEEE Software May 1989; 6(3):19-27.
9. Musa John D., Anthony Iannino, and Kazuhira Okumoto. Software Reliability: Measurement, Prediction, and Applications. McGraw-Hill, New York 1987.
10. Nikora A., N. Schneidewind, and J. Munson. Practical Issues In Estimating Fault Content And Location In Software Systems. Proceedings of the AIAA Space Technology Conference and Exposition, Albuquerque, NM, Sep 29-30, 1999.
11. Nikora A., N. Schneidewind, and J. Munson. IV&V Issues in Achieving High Reliability and Safety in Critical Control Software. Final Report, Volume 1 -Measuring and Evaluating the Software Maintenance Process and Metrics-Based Software Quality Control, Volume 2 - Measuring Defect Insertion Rates and Risk of Exposure to Residual Defects in Evolving Software Systems, and Volume 3 - Appendices, Jet Propulsion Laboratory, National Aeronautics and Space Administration, Pasadena, California, January 19, 1998.
12. A. Nikora, N. Schneidewind, and J. Munson. IV&V Issues in Achieving High Reliability and Safety in Critical Control System Software. Proceedings of the Third International Society of Science and Applied Technologies Conference on Quality in Design, Anaheim, California, March 12-14, 1997: 25-30.
13. Schneidewind N. Measuring and Evaluating Maintenance Process Using Reliability, Risk, and Test Metrics. IEEE Transactions on Software Engineering November/December 1999; 25(6): 768-781.
14. Schneidewind N. Software Validation for Reliability. Wiley Encyclopedia of Electrical and Electronics Engineering, John G. Webster, editor, John Wiley & Sons, Inc., 1999;19: 607-618.
15. Schneidewind N. Reliability Modeling for Safety Critical Software. IEEE Transactions on Reliability March 1997; 46(1):88-98.
16. Singpurwalla N. Determining an Optimal Time Interval for Testing and Debugging Software. IEEE Transactions on Software Engineering April 1991; 17(4): 313-319.
17. Voas J. and K. Miller. Software Testability: The New Verification. IEEE Software May 1995; 12(3):17-28.