Skip to main content

Undergraduate software engineering education

  • Conference paper
  • First Online:

Part of the book series: Lecture Notes in Computer Science ((LNCS,volume 327))

Abstract

Software engineering education is a difficult venture at very best but the difficulty of teaching software engineering ideas at the undergraduate level is even more problematic. The most significant problem in undergraduate software engineering education is, not surprisingly, lack of maturity. From our experience over the last six years this immaturity manifests itself in three different areas: computer science, academics in general, and social and personal relations. Each of the these manifestations of the undergraduate's lack of development has a significant impact on their ability to understand software engineering concepts. The results of our study on the unique pitfalls of undergraduate software engineering education are detailed in the first of the two papers that follow.

We feel that software engineering should be an equal partner in our undergraduate computer science major with the more traditional hardware and software topics. Based on our experiences, we have developed an approach for teching software engineering which considers the immaturity of undergraduates and attempts to avoid the problems it imposes. The second paper briefly outlines our approach, which is based upon the sound educational principle of iteration of basic concepts and the eventual synthesis of those concepts into second and third level relationships.

This is a preview of subscription content, log in via an institution.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Bibliography

  1. James W. Canan, The Software Crisis, Air Force Magazine, May 1986.

    Google Scholar 

  2. James Collofello, A Project-Unified Software Engineering Course Sequence, Proceedings of the Thirteenth SIGCSE Technical Symposium on Computer Science Education, 1982.

    Google Scholar 

  3. James Collofello, The Software Technical Review Process, Curriculum Module SEI-CM-3.0, Software Engineering Institute, Carnegie-Mellon University, September 1986.

    Google Scholar 

  4. J. L. Cornfeld and L. L. Knefelkamp, Combining Student Stage and Style in the Design of Learning Environments: An Integration of Perry Stages and Holland Typologies, presented to the 1979 American College Personnel Association Conference, 1979.

    Google Scholar 

  5. R. S. Culver and J. T. Hackos, Perry's Model of Intellectual Development, in Engineering Education, December 1982.

    Google Scholar 

  6. Gary Ford, Educational Needs of the Software Community, in Software Engineering Education, The Educational Needs of the Software Community, edited by Norman E. Gibbs and Richard E. Fairley, Springer-Verlag, New York, 1987.

    Google Scholar 

  7. Peter Freeman, Essential Elements of Software Engineering Education Revisited, in Software Engineering Education, The Educational Needs of the Software Community, edited by Norman E. Gibbs and Richard E. Fairley, Springer-Verlag, New York, 1987.

    Google Scholar 

  8. Robert L. Glass, Software Engineering and Computer Science: How Do They Differ?, in Software Engineering Education, The Educational Needs of the Software Community, edited by Norman E. Gibbs and Richard E. Fairley, Springer-Verlag, New York, 1987.

    Google Scholar 

  9. E. B. Koffman, P. L. Miller, and C. E. Wardle, Recommended Curriculum for CS1, 1984, Communications of the ACM, Volume 28, Number 8, August 1985.

    Google Scholar 

  10. E. B. Koffman, D. Stemple, and C. E. Wardle, Recommended Curriculum for CS2, 1984: A Report of the ACM Curriculum Task Force for CS2, Communications of the ACM, Volume 28, Number 8, August 1985.

    Google Scholar 

  11. B. Mynatt and L. Leventhal, Profile of Undergraduate Software Engineering Courses: Results from a Survey, Eighteenth SIGCSE Technical Symposium on Computer Science Education, St. Louis, MO, February 19–20, 1987.

    Google Scholar 

  12. William E. Richardson, Why Is Software Engineering So Difficult?, in Software Engineering Education, The Educational Needs of the Software Community, edited by Norman E. Gibbs and Richard E. Fairley, Springer-Verlag, New York, 1987.

    Google Scholar 

  13. G. M. Schneider and S. C. Bruell, Advanced Programming and Problem Solving with Pascal, John Wiley and Sons, New York, 1987.

    Google Scholar 

  14. R. H. Thayer and L. A. Endres, Software Engineering Project Laboratory: The Bridge Between University and Industry, in Software Engineering Education, The Educational Needs of the Software Community, edited by Norman E. Gibbs and Richard E. Fairley, Springer-Verlag, New York, 1987.

    Google Scholar 

  15. James Tomayko, Software Configuration Management, Curriculum Module SEI-CM-4.0, Software Engineering Institute, Carnegie-Mellon University, September 1986.

    Google Scholar 

  16. James Tomayko, Teaching a Project-Intensive Introduction to Software Engineering, SEI-87-SR-1, Software Engineering Institute, Carnegie-Mellon University, March 1987.

    Google Scholar 

  17. A. I. Wasserman and P. Freeman, Ada Methodologies: Concepts and Requirements, Software Engineering Notes, Volume 8, Number 1, January 1983.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Gary A. Ford

Rights and permissions

Reprints and permissions

Copyright information

© 1988 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Richardson, W.E. (1988). Undergraduate software engineering education. In: Ford, G.A. (eds) Software Engineering Education. SEI 1988. Lecture Notes in Computer Science, vol 327. Springer, New York, NY. https://doi.org/10.1007/BFb0043595

Download citation

  • DOI: https://doi.org/10.1007/BFb0043595

  • Published:

  • Publisher Name: Springer, New York, NY

  • Print ISBN: 978-0-387-96854-4

  • Online ISBN: 978-0-387-34779-0

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics