A two-semester undergraduate sequence in Software Engineering: Architecture and experience

  • David B. Boardman
  • Aditya P. Mathur
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 750)


A two-semester sequence in Software Engineering has been offered to Computer Science undergraduates at Purdue University since the fall of 1991. An attempt was made to balance the teaching of theory and practice of software engineering and provide the students with an opportunity to apply some of the techniques learned in the classroom to a controlled development project. The project was selected from an industrial setting and the product developed was returned to industry. We describe the architecture of the offering and our experience during the first offering in Fall 1991 and Spring 1992.


Software Engineering Software Engineer Integration Manager Mutation Testing Spring Semester 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [1]
    B. J. Choi, R. A. DeMillo, E. W. Krauser, A. P. Mathur, R. J. Martin, A. J. Offutt, H. Pan, and E. H. Spafford, “The Mothra toolset”, Proceedings of Hawaii International Conference on System Sciences, HI, January 3–6, 1989.Google Scholar
  2. [2]
    L. A. Clarke, A. Podgruski, D. J. Richardson, and S. Zeil, “A formal evaluation of data flow path selection criteria”, IEEE Trans. on Software Engineering, Vol. 15, No 11, pp 1318–1332, November 1989.CrossRefGoogle Scholar
  3. [3]
    R. A. DeMillo, R. J. Lipton, and F. G. Sayward, “Hints on test data selection: Help for the Practicing Programmer”, Computer, Vol. 11, No.4, April 1978.Google Scholar
  4. [4]
    C. Ghezzi, M. Jazayeri, D. Mandrioli, Fundamentals of Software Engineering, Prentice Hall, New Jersey, 1991.Google Scholar
  5. [5]
    J. R. Horgan, Bellcore, Personal Communication.Google Scholar
  6. [6]
    J. R. Horgan and A. P. Mathur, “Assessing tools in research and education”, IEEE Software, May 1992, pp 61–69Google Scholar
  7. [7]
    L. Lamport, A document preparation system: LaTEX User's guide & reference manual, Addison-Wesley Publishing Company, Reading, MA, 1986.Google Scholar
  8. [8]
    J. W. Laski and B. Korel, “A data-flow oriented program testing strategy”, IEEE Trans. on Software Engineering, Vol. SE-9, No. 3, May 1983, pp 347–354.Google Scholar
  9. [9]
    S. Levy and D. E. Knuth, “The CWEB system of structured documentation”, Technical Report, UMSI 91/56, February 1991, University of Minnesota Supercomputing Research Institute, MN.Google Scholar
  10. [10]
    A. P. Mathur, “On the relative strengths of data flow and mutation testing”, Proceedings of the Ninth Annual Pacific Northwest Software Quality Conference, October 7–8, 1991, Portland, OR.Google Scholar
  11. [11]
    D. B. Boardman and A. P. Mathur, “A 2-semester undergraduate sequence in software engineering: architecture and experience”, Technical Report SERC-TR-140-P, May 1993, Software Engineering Research Center, Purdue University, W. Lafayette, IN 47907.Google Scholar
  12. [12]
    Using Saber-C, Version 3.0, Saber Software Systems, Inc., Cambridge, MA, 1986.Google Scholar
  13. [13]
    M. Shaw, “We can teach software better”, Computing Research News, September 1992.Google Scholar
  14. [14]
    W. F. Tichy, “An introduction to the Revision Control System”, in Unix Programmer's Manual, Supplementary Documents 1, USENIX Association, November 1986.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1993

Authors and Affiliations

  • David B. Boardman
    • 1
  • Aditya P. Mathur
    • 1
  1. 1.Software Engineering Research Center and Department of Computer SciencesPurdue universityW. Lafayette

Personalised recommendations