Cleanroom Software Development: An Empirical Evaluation

IEEE Transactions on Software Engineering

Volumn SE-13, Issue 9, 1987, Pages 1027-1037

  Selby, Richard W ^a   Basili, Victor R ^b   Baker, F Terry ^b  

^a UNIVERSITY OF CALIFORNIA   (United States)

^b UNIVERSITY OF MARYLAND   (United States)

Author keywords

Empirical study; methodology evaluation; off line; software development methodology; software management; software measurement; software review; software testing

Indexed keywords

EID: 5344270031     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/TSE.1987.233525     Document Type: Article

References (47)

1. E. N. Adams, “Optimizing preventive service of software products, “ IBM J. Res. Develop., vol. 28, no. 1, pp. 2-14, Jan. 1984.
2. F. T. Baker, “Chief programmer team management of production programming,” IBM Syst. J., vol. 11, no. 1, pp. 131-149, 1972.
3. ——,”Chief programmer teams,” in Tutorial on Structured Programming: Integrated Practices, V. R. Basili and F. T. Baker, Eds. New York: IEEE, 1981.
4. V. R. Basili and D. H. Hutchens, “An empirical study of a syntactic metric family,” IEEE Trans. Software Eng., vol. SE-9, pp. 664-672, Nov. 1983.
5. V. R. Basili and R. W. Reiter, “A controlled experiment quantitatively comparing software development approaches,” IEEE Trans. Software Eng., vol. SE-7, May 1981.
6. V. R. Basili and R. W. Selby, “Data collection and analysis in software ware research and management,” in Proc. Amer. Statist. Ass. and Biometric Sov. Joint Statist. Meetings, Philadelphia, PA, August 13-16, 16, 1984.
7. “Comparing the effectiveness of software testing strategies,” Dep. Comput. Sci., Univ. Maryland, College Park, Tech. Rep. TR-1501, 1501, May 1985; to appear in IEEE Trans. Software Eng.
8. V. R. Basili, R. W. Selby, and D. H. Hutchens, “Experimentation in software engineering,” IEEE Trans. Software Eng., vol. SE-12, pp. 733-743, July 1986.
9. V. R. Basili and A. J. Turner, SIMPL-T: A Structured Programming Language. Geneva, IL: Paladin House, 1976.
10. V. R. Basili and D. M. Weiss, “A methodology for collecting valid software engineering data,” IEEE Trans. Software Eng., vol. SE-10, pp. 728-738, Nov. 1984.
11. L. J. Bass, “An approach to user specification of interactive display interfaces,” IEEE Trans. Software Eng., vol. SE-11, pp. 686-698,. Aug. 1985.
12. B. W. Boehm, T: E. Gray, and T. Seewaldt, “Prototyping versus specifying: A multiproject experiment,” IEEE Trans. Software Eng., vol. SE-10, pp. 290-303, May 1984.
13. T. P. Bowen, G. B. Wigle, and J. T. Tsai, “Specification of software quality attributes, Rome Air Development Center, Griffiss Air Force Base, NY, Tech. Rep. RADC-TR-85-37 (3 volumes), Feb. 1985.
14. J. P. Cavano and J. A. McCall, “A framework for the measurement of software, quality,” in Proc. Software Quality and Assurance Workshop, San Diego, CA; Nov. 1978, pp. 133-139.
15. P. A. Currit, “Cleanroom certification model,” in Proc. 8th Annu. Software Eng. Workshop, NASA/GSFC, Greenbelt, MD, Nov. 1983.
16. P. A. Currit, M. Dyer, and H. D. Mills, “Certifying the reliability of software,” IEEE Trans. Software Eng., vol. SE-12, pp. 3-11, Jan. 1986.
17. B. Curtis, “Cognitive science of programming,” in Sixth Minnow-brook brook Workshop Software Performance Evaluation, Blue Mountain Lake, NY, July 19-22, 1983.
18. J. W. Duran and S. Ntafos, “A report on random testing,” in Proc. Fifth Int. Conf. Software Eng., San Diego, CA, Mar. 9-12, 1981, pp. 179-183.
19. M. Dyer, “Cleanroom software development method,” IBM Federal Systems Division, Bethesda, MD, Oct. 14, 1982.
20. ——, “Software validation in the Cleanroom development method,” IBM-FSD Tech. Rep. 86.0003, Aug. 19, 1983.
21. ——, “Software development under statistical quality control,” in Proc. NATO Advanced Study Institute: The Challenge of Advanced Computing Technology to System Design Methods, Durham, UK, July 29-Aug. 10, 1985.
22. M. Dyer, R. C. Linger, H. D. Mills, D. O’Neill, and R. E. Quinnan, “The management of software engineering,” IBM Syst. J., vol. 19, no. 4, 1980.
23. M. Dyer and H. D. Mills, “The Cleanroom approach to reliable software development,” in Proc. Validation Methods Research for Fault-Tolerant Tolerant Avionics and Control Systems Sub-Working-Group Meeting: Production. of Reliable Flight-Crucial Software, Research Triangle, Institute, NC, Nov. 2-4, 1981.
24. ——,”Developing electronic systems with certifiable reliability,” in Proc. NATO Conf., Summer 1982.
25. M. E. Fagan, “Design and code inspections to reduce errors in program development,” IBM Syst. J., vol. 15, no. 3, pp. 182-211, 1976.
26. A. B. Ferrentino and H. D. Mills, “State machines and their semantics i n software engineering,” in Proc. IEEE COMPSAC, 1977.
27. A. L. Goel, “A guidebook for software reliability assessment,” Dep. Industrial Eng. and Oper. Res., Syracuse Univ., New York, Tech. Rep. 83-11, Apr. 1983.
28. M. H. Halstead, Elements of Software Science. New York: North-Holland, Holland, 1977.
29. C. A. R. Hoare, “An axiomatic basis for computer programming,” Commun. ACM, vol. 12, no. 10, pp. 576-583, Oct. 1969.
30. W. E. Howden, “Reliability of the path analysis testing strategy,” IEEE Trans. Software Eng., vol. SE-2, no. 3, Sept. 1976.
31. P. Kerola and P. Freeman, “A comparison of lifecycle models,” in Proc. 5th Int. Conf. Software Eng., Mar. 1981, pp. 90-99.
32. R. C. Linger, H. D. Mills, and B. I. Witt, Structured Programming: Theory and Practice. Reading, MA: Addison-Wesley, 1979.
33. B. Littlewood, “Stochastic reliability growth: A model for fault renovation computer programs and hardware designs,” IEEE Trans. Rel., vol. R-30, Oct. 1981.
34. B. Littlewood and J. L. Verrall, “A Bayesian reliability growth model for computer software,” Appl. Statist., vol. 22, no. 3,1973.
35. T. J. McCabe,'’ A complexity measure,” IEEE Trans. Software Eng., vol. SE-2, pp. 308-320, Dec. 1976.
36. J. A. McCall, P. Richards, and G. Walters, “Factors in software quality,” Rome Air Development Center, Griffiss Air Force Base, NY, Tech. Rep. RADC-TR-77-369, Nov. 1977.
37. H. D. Mills, “Chief programmer teams: Principles and procedures,” IBM Corp., Gaithersburg, MD, Rep. FSC 71-6012, 1972.
38. “Mathematical foundations for structural programming,” IBM Rep. FSL 72-6021, 1972.
39. J. D. Musa, “A theory of software reliability and its application,” IEEE Trans. Software Eng., vol. SE-1, no. 3, pp. 312-327, 1975.
40. G. J. Myers, Software Reliability: Principles & Practices. New York: Wiley, 1976.
41. D. L. Parnas, “On the criteria to be used in decomposing systems into modules,” Commun. ACM, vol. 15, no. 12, pp. 1053-1058, 1972.
42. R. W. Selby, “Evaluations of software technologies: Testing, CLEANROOM, and metrics,” Ph.D. dissertation, Dep. Comput. Sci., Univ. Maryland, College Park, Tech. Rep. TR-1500, 1985.
43. ——,”Combining software testing strategies: An empirical evaluation,” in Proc. Workshop Software Testing, Banff, Alta., Canada, July 15-17, 1986, pp. 82-91.
44. K. S. Shankar, “A functional approach to module verification,” IEEE Trans. Software Eng., vol. SE-8, Mar. 1982.
45. J. G. Shanthikumar, “A statistical time dependent error occurrence rate software reliability model with imperfect debugging,” in Proc. 1981 Nat. Comput. Conf., June 1981.
46. R. A. Thayer, M. Lipow, and E. C. Nelson, Software Reliability. Amsterdam, The Netherlands: North-Holland, 1978.
47. M. V. Zelkowitz and M. Branstad, in Proc. ACM SIGSOFT Rapid Prototyping Symp., Apr. 1982.