Software testing in the computer science curriculum -- a holistic approach

ABSTRACT

Although testing accounts for 50% of the cost of software, it receives little treatment in most curricula. This paper presents some approaches to giving all students multiple, incremental exposures to software testing throughout the curriculum. A unifying framework is presented which identifies a minimal set of test experiences, skills and concepts students should accumulate. The holistic approach combines common test experiences in core courses, an elective course in software testing, and volunteer participation in a test laboratory.

REFERENCES

• 1: David Carrington, Teaching software testing, Proceedings of the 2nd Australasian conference on Computer science education, p.59-64, July 1997, The Univ. of Melbourne, Australia [doi>10.1145/299359.299369]
• 2: Dahl. O.J, Dij'kstra, E.W., and Hoare, C.A.R. Structured Programming APIC Studies in Data Processing, 8. Academic Press, 1972.
• 3: Thomas B. Hilburn , Massood Townhidnejad, Software quality: a curriculum postscript?, Proceedings of the thirty-first SIGCSE technical symposium on Computer science education, p.167-171, March 07-12, 2000, Austin, Texas, United States
• 4: Watts S. Humphrey, A Discipline for Software Engineering, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1995
• 5: Watts S. Humphrey, Introduction to the team software process, Addison-Wesley Longman Ltd., Essex, UK, 1999
• 6: Jones, E.L. The SPRAE Framework for Teaching Software Testing in the Undergraduate Curriculum Proceedings of Symposium on Computing at Minority Institutions, (June 1-4, 2000).
• 7: Edward L. Jones, Grading student programs - a software testing approach, Proceedings of the fourteenth annual consortium on Small Colleges Southeastern conference, p.185-192, November 2000, Roanoke College, Salem, Virginia, United States
• 8: Glenford J. Myers, Art of Software Testing, John Wiley & Sons, Inc., New York, NY, 1979
• 9: Leon Osterweil, Strategic directions in software quality, ACM Computing Surveys (CSUR), v.28 n.4, p.738-750, Dec. 1996 [doi>10.1145/242223.242288]
• 10: Kenneth A. Reek, The TRY system -or- how to avoid testing student programs, ACM SIGCSE Bulletin, v.21 n.1, p.112-116, Feb. 1989
• 11: James A. Whittaker, What Is Software Testing? And Why Is It So Hard?, IEEE Software, v.17 n.1, p.70-79, January 2000 [doi>10.1109/52.819971]