{"title":"Practical lessons for improving software quality","authors":"J. Bukowski, W. Goble","doi":"10.1109/ARMS.1990.67998","DOIUrl":null,"url":null,"abstract":"Discussed is a retrospective study of the errors uncovered in developing a multiple-release industrial software product of some 60000 lines of C source code. The purpose of the study was to determine what changes in existing software development procedures would detect errors earlier in the life cycle, where they are less expensive to correct. The study procedure consisted of three tasks: establishing criteria for sorting the problems into software development errors and other problems/errors, determining error classes for categorizing the development errors, and identifying a series of ten error-detection steps within the software development process. A number of results specific to this study are presented, and conclusions are drawn and recommendations made regarding functional and design errors.<<ETX>>","PeriodicalId":383597,"journal":{"name":"Annual Proceedings on Reliability and Maintainability Symposium","volume":"18 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1990-01-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"5","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Annual Proceedings on Reliability and Maintainability Symposium","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ARMS.1990.67998","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 5
Abstract
Discussed is a retrospective study of the errors uncovered in developing a multiple-release industrial software product of some 60000 lines of C source code. The purpose of the study was to determine what changes in existing software development procedures would detect errors earlier in the life cycle, where they are less expensive to correct. The study procedure consisted of three tasks: establishing criteria for sorting the problems into software development errors and other problems/errors, determining error classes for categorizing the development errors, and identifying a series of ten error-detection steps within the software development process. A number of results specific to this study are presented, and conclusions are drawn and recommendations made regarding functional and design errors.<>