John B. Bowen
ABSTRACT
A standard software error classification is viable based on experimental use of different schemes on Hughes-Fullerton projects. Error classification schemes have proliferated independently due to varied emphasis on depth of casual trace-ability and when error data was collected. A standard classification is proposed that can be applied to all phases of software development. It includes a major casual category for design errors. Software error classification is a prerequisite both for feedback for error prevention and detection, and for prediction of residual errors in operational software.
- Thayer, T. A., et al, "Software Reliability Study," TRW-Redondo Beach, RADC TR-76-238 (Aug 1976).Google Scholar
- Willmorth, N. E., "Proceedings of Data Collection Problem Conference," RADC TR-76-329, Vol. VI (Dec 1976).Google Scholar
- Finfer, M. C., "Software Data Collection Study," System Development Corp., RADC-TR-76-329, Vol III (Dec 1976).Google Scholar
- Baker, W. F., "Software Data Collection and Analysis: A Real-Time System Project History," IBM Corp., RADC-TR-77-192 (Jun 1977).Google Scholar
- Fries, M. J., "Software Error Data Acquisition," Boeing-Seattle, RADC-TR-77-130 (April 1977).Google Scholar
- Chief of Naval Materiel, Military Standard for Weapon System Software Development MIL-STD-1679 (Navy), AMSC No. 23033 (Dec 1978).Google Scholar
- Willmorth, N. E., et al, "Software Data Collection Study, Summary and Conclusions," RADC-TR-76-329, Vol. I (Dec 1976).Google Scholar
- Weiss, D. M., "Evaluating Software Development by Error Analysis: The Data from the Architecture Research Facility," Naval Research Laboratory, NRL report 8268 (Dec 1978).Google Scholar
- Nelson, R., "Software Data Collection and Analysis, Draft"---partial report, RADC (Sep 1978).Google Scholar
- Gannon, C., "Error Detection Using Path Testing and Static Analysis," Computer, pp 26--31 (Aug 1979). Google ScholarDigital Library
- Hecht, H., "Measurement, Estimation, and Prediction of Software Reliability," Aerospace Corp. NASA CR-145135 (Jan 1977).Google Scholar
- Motley, R. W. and Brooks, W. D., "Statistical Prediction of Programming Errors," IBM Corp. RADC TR-77-175 (May 1977).Google Scholar
- Gerhart, S. L., "Development of a Methodology for Classifying Software Errors," Duke University (July 1976).Google Scholar
- Castle, S. G., "Software Reliability: Modelling Time-to-Error and Time-to-Fix," masters thesis, Air Force Institute of Technology (Mar 1978).Google Scholar
- Kruszewski, G., "Modeling Software Reliability Growth, Proceedings of Surface Warfare Systems RMQ Seminar," Norfolk, VA (Sept 1978).Google Scholar
- Schafer, R. E., et al, "Validation of Software Reliability Models," Hughes-Fullerton, RADC-TR-79-147 (Aug 1979).Google Scholar
- Sukert, A., "State of the Art in Software Reliability," Presentation, NSIA Software Conference, Buena Park, CA (Feb 1979).Google Scholar
- Thibodeau, R., "The State-of-the-Art in Software Error Data Collection and Analysis," AIRMICS (Jan 1979).Google Scholar
- Amory, W. and Clapp, J. A., "Engineering of Quality Software Systems (A Software Error Classification Methodology)," MITRE Corp., MTR-2648, Vol VII, Jan 1975, also RADC-TR-74-324, Vol VII.Google Scholar
- Rubey, R. J., "Quantitative Aspects of Software Validation," Proceedings of the 1975 International Conference on Reliable Software Los Angeles, pp 246--251 (April 1975). Google ScholarDigital Library
- NAVSEA, Statement of Work for AN/SLQ-32(V) Verification and Validation, Appendix A (May 1977).Google Scholar
- Hartwick, R. Dean, "Software Acceptance Criteria Panel Report," Joint Logistics Commanders Joint Policy Coordinating Group on Computer Resource Management, Software Workshop, Monterey, CA (April 1979).Google Scholar
- Bowen, J. B., "AN/TPQ-36 Software Reliability Status Report," Hughes-Fullerton, CDRL 8-18-015 (Dec 1979).Google Scholar
- Shooman, M. L. and Ruston, H., "Summary of Technical Progress, Investigation of Software Models," Polytechnic Institute of New York, RADC-TR-79-188 (July 1979).Google Scholar
- Thielen, B. J., "SURTASS Code Review Statistics," Hughes-Fullerton, IDC 78/1720.1004 (Jan 1978).Google Scholar
- Fagan, M. E., "Inspecting Software Design and Code," Datamation, pp 133--144 (Oct 1977).Google Scholar
- Hoffman, H., "An Experiment in Software Error Occurrence and Detection," masters thesis, Naval Postgraduate School (Jun 1977).Google Scholar
Recommendations
Taxonomy-Based Human Error Assessment for Senior Software Engineering Students
SIGCSE 2024: Proceedings of the 55th ACM Technical Symposium on Computer Science Education V. 1Software engineering (SE) is a complex symphony of development activities spanning multiple engineering phases. Despite best efforts, software engineers experience human errors. Human error theory from psychology has been studied in the context of SE, ...
Post-completion error in software development
CHASE '16: Proceedings of the 9th International Workshop on Cooperative and Human Aspects of Software EngineeringPost-completion errors have been observed in a variety of tasks by psychologists, but there is a lack of empirical studies in software engineering. This paper investigates whether post-completion errors occur in software development and the likelihood ...
Two Mistakes and Error-Free Software: A Confession
The software development process and the resulting product are so complex that no error-detecting approach will ever be able to produce error-free software.
Comments