Research Report: Modeling the Incidence of Postrelease Errors in Software

References

• Adams E. N.Minimizing cost impact of software defects (1980) 04IBM Research report RC 8228Google Scholar
• Butler R. W., Finelli G. The infeasibility of quantifying the reliability of life-critical real-time software. IEEE Trans. Software Engrg. (1993) 19(1):13–21Crossref, Google Scholar
• Bender D., Gahtan A.Evaluating Legal Risks in the “Year 2000 Problem.” (1998) . White & Case LLP White Paper (August) http://www.whitecase.com/Year_2000_Problem_memo.htmlGoogle Scholar
• Chillarege R., Bhandari I. S., Chaar J. K., Halliday M. J., Moebus D. S., Ray B. K., Wong M-Y. Orthogonal defect classification-a concept for in-process measurements. IEEE Trans. Software Engrg. (1992) 18(11):943–956Crossref, Google Scholar
• Geyelin M. Faulty software means business for litigators. The Wall Street Journal (1994) 0621Google Scholar
• Inwood C. Formal methods can cut your error rate. Comput. Canada (1993) 19(2):29Google Scholar
• Inwood C. To err is human, to forgive uncommon in IS. Comput. Canada (1994) 20(6):22Google Scholar
• Jones Capers. Sick software. Computerworld (1993) 121327(50):115Google Scholar
• Littlewood B., Strigini L. Validation of ultrahigh dependability for software-based systems. Comm. ACM (1993) 36(11):69–73Crossref, Google Scholar
• Osterweil L. Report from the panel on software quality: Strategic directions (1996) 0614–15:1 http://laser.cs.umass.edu/sdcr/report/Google Scholar
• Selby R. W. Interconnectivity analysis techniques for error localization in large systems. J. Systems and Software (1993) 20(3):267Crossref, Google Scholar