Abstract
Software engineering education has a 30-year history. It is a story of academics struggling to fulfill industry needs with almost no support from computer science curriculum designers. It is a story of industry finally winning over some of academia to teach software engineering rather than vanilla computer science. It is a story of a discipline still incomplete, but having made great strides in the last decade. This paper discusses the succeeding eras of software engineering education, from lone teachers to master's curricula to undergraduate degree programs. Even though the maturity of the discipline is as yet unattained, it will achieve adult status through practice, not by waiting for academia to glacially catch up.
Similar content being viewed by others
References
ACM Curriculum Committee on Computer Science (1968), “Curriculum 68,” Communications of the ACM 11, 3, 151–197.
Ardis, M. and G. Ford (1989), “1989 SEI Report on Graduate Software Engineering Education,” Technical Report CMU/SEI-89-TR-021, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA.
Brooks, F.P., Jr. (1995), The Mythical Man-Month: Essays on Software Engineering (Anniversary Edition), 2nd Edition, Addison-Wesley, Boston, MA.
Buchanan, R.A. (1985), “The Rise of Scientific Engineering in Britain,” British Journal for the History of Science 18, 218–233.
Coulter, N. and J. Damman (1994), “Current Practices, Culture Changes, and Software Engineering Education,” Computer Science Education 5, 211–227.
Davis, M. (1996), “Defining ‘Engineer:’ How to Do it and Why it Matters,” ASEE Journal of Engineering Education 4, 97–101.
Ferguson, E.S. (1991), “Elegant Inventions: The Artistic Component of Technology,” In Technology and Choice: Readings from Technology and Culture, M.C. LaFollette and J.K. Stine, Eds., University of Chicago Press, Chicago.
Ford, G., N. Gibbs, and J. Tomayko (1987), “Software Engineering Education: An Interim Report from the Software Engineering Institute,” Technical Report CMU/SEI-87-TR-8, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA.
Fores, M. (1979), “The History of Technology: An Alternated View,” Technology and Culture 20, 853– 861.
Galler, B. (1989), “The IBM 650 and the Universities,” Annals of the History of Computing 8, 1.
Garlan, D., D. Gluch, and J.E. Tomayko (1997), “Agents of Change: Educating Software Engineering Leaders,” IEEE Computer 30, 11.
Gerhart, S.L. (1986), “Skills versus Knowledge in Software Engineering Education: A Retrospective on the Wang Institute MSE Program,” In Software Engineering Education: The Educational Needs of the Software Community, N.E. Gibbs and R.E. Fairley, Eds., Springer-Verlag, New York, p. 221.
Gibbs, N.E. and R.E. Fairley, Eds. (1987), Software Engineering Education: The Educational Needs of the Software Community, Springer-Verlag, New York.
Gibbs-Smith, G.H. (1962), Sir George Cayley's Aeronautics, HMSO, London, p. 16.
Jensen, R.W. and C.C. Tonies (1979), Software Engineering, Prentice-Hall, Englewood Cliffs, NJ.
Kuhn, T.S. (1971), “The Relations Between History and History of Science,” Daedulus 100, 271–304.
Lutz, M.J. and J.F. Naveda (1997), “The Road Less Traveled: A Baccalaureate Degree in Software Engineering,” In Proceedings of the 1997 ACM SIGSCE Conference, pp. 287–291.
Mahoney, M. (1996), “Finding a History of Software Engineering,” manuscript.
Mills, E.E. (1987), “The Master of Software Engineering Program at Seattle University after Six Years,” In Software Engineering Education: The Educational Needs of the Software Community, N.E. Gibbs and R.E. Fairley, Eds., Springer-Verlag, New York.
Mills, H.D. (1972), “Chief Programmer Teams: Techniques and Procedures (1970),” In Software Productivity, Little, Brown, and Company, Boston, MA.
Parnas, D. (1990), “Education for Computing Professionals,” IEEE Computer 23, 1, 17–22.
Ross, D. (1989), “The NATO Conferences from the Perspective of an Active Software Engineer,” Annals of the History of Computing 11, 2, 133–141.
Shaw, M. (1989), “Remembrances of a Graduate Student,” Annals of the History of Computing 11, 2, 141–143.
Shaw, M. (1990), “Prospects for an Engineering Discipline of Software,” IEEE Software 7, 6, 15–24.
Shaw, M. and J.E. Tomayko (1991), “Models for Undergraduate Project Courses in Software Engineering,” Technical Report CMU/SEI-91-TR-10, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA.
Stucki, L.G., and L. Peters (1978), “A Software Engineering Graduate Curriculum,” In Proceedings of the 1978 Annual ACM Conference, ACM, pp. 63–67.
Tomayko, J.E. (1987), “Teaching a Project-Intensive Introduction to Software Engineering,” Technical Report SEI-SR-87-1, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA.
Wasserman, A.I. and P. Freeman, Eds. (1976), Software Engineering Education: Needs and Objectives, Springer-Verlag, New York.
Wilkes, M.V., D.J. Wheeler, and S. Gill (1982), The Preparation of Programs for an Electronic Digital Computer, Reprinted by Tomash, Los Angeles.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Tomayko, J.E. Forging a discipline: An outline history of software engineering education. Annals of Software Engineering 6, 3–18 (1998). https://doi.org/10.1023/A:1018953214201
Issue Date:
DOI: https://doi.org/10.1023/A:1018953214201