Reflections on Software Engineering Education

  • Hans van Vliet
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4309)


The “engineering” focus in software engineering education leaves instructors vulnerable to several traps. It also misleads students as to SE’s essential human and social dimensions. In this paper we argue that there’s more to SE than engineering. A major challenge is to reconcile the engineering dimension with the human and social dimension.


Software Engineer Requirement Engineering Social Dimension Software Architecture Software Development Project 
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.
    Kruchten, P.: Putting the ”engineering” into ”software engineering”. In: Strooper, P. (ed.) Australian Software Engineering Conference (ASWEC 2004), Melbourne, Australia, pp. 2–8. IEEE Computer Society, Los Alamitos (2004)Google Scholar
  2. 2.
    Parnas, D.: Software Engineering Programs Are Not Computer Science Programs. IEEE Software 16(6), 19–30 (1999)CrossRefGoogle Scholar
  3. 3.
    Shaw, M.: Prospects for an Engineering Discipline of Software. IEEE Software 7(6), 15–24 (1990)CrossRefGoogle Scholar
  4. 4.
    Saiedian, H., Bagert, D., Mead, N.: Software Engineering Programs: Dispelling the Myths and Misconceptions. IEEE Software 19(5), 35–41 (2002)CrossRefGoogle Scholar
  5. 5.
    Dawson, R., Newsham, R.: Introducing Software Engineers to the Real World. IEEE Software 14(6), 37–43 (1997)CrossRefGoogle Scholar
  6. 6.
    Dawson, R.: Twenty Dirty Tricks to Train Software Engineers. In: Proceedings 22nd International Conference on Software Engineering (ICSE22), pp. 209–218. IEEE, Los Alamitos (2000)CrossRefGoogle Scholar
  7. 7.
    van Vliet, H.: Software Engineering, Principles and Practice, 2nd edn. John Wiley & Sons, Chichester (2000)Google Scholar
  8. 8.
    Budgen, D.: Software Design, 2nd edn. Addison-Wesley, Reading (2003)Google Scholar
  9. 9.
    Lago, P., van Vliet, H.: Teaching a Course on Software Architecture. In: Proceedings Eighteenth Conference on Software Engineering Education & Training, pp. 35–42. IEEE Computer Society, Los Alamitos (2005)Google Scholar
  10. 10.
    Spector, A., Gifford, D.: A Computer Science Perspective of Bridge Design. Communications of the ACM 29(4), 267–283 (1986)CrossRefGoogle Scholar
  11. 11.
    Leveson, N.: High-Pressure Steam Engines and Computer Software. In: Proceedings 14th International Conference on Software Engineering (ICSE14), pp. 2–14. IEEE, Los Alamitos (1992)CrossRefGoogle Scholar
  12. 12.
    Bryant, A.: Metaphor, myth and mimicry: The bases of software engineering. Annals of Software Engineering 10, 273–292 (2000)MATHCrossRefGoogle Scholar
  13. 13.
    Hirschheim, R., Klein, H.: Four Paradigms of Information Systems Development. Communications of the ACM 32(10), 1199–1216 (1989)CrossRefGoogle Scholar
  14. 14.
    Lewerentz, C., Rust, H.: Are software engineers true engineers? Annals of Software Engineering 10, 311–328 (2000)MATHCrossRefGoogle Scholar
  15. 15.
    Hilburn, T., Humphrey, W.: The Impending Changes in Software Education. IEEE Software 19(5), 22–24 (2002)CrossRefGoogle Scholar
  16. 16.
    Yourdon, E.: Death March, The Complete Software Developer’s Guide to Surviving ”Mission Impossible” Projects. Prentice Hall, Englewood Cliffs (1997)Google Scholar
  17. 17.
    Flyvbjerg, B., Bruzelius, N., Rothengatter, W.: Megaprojects and Risk: An Anatomy of Ambition. Cambridge University Press, Cambridge (2003)Google Scholar
  18. 18.
    DeMarco, T.: Controlling Software Projects. Yourdon Press (1982)Google Scholar
  19. 19.
    Jørgensen, M., Grimstad, S.: Over-optimism in Software Development Projects: ”The winner’s curse”. Improve, Software Process Improvement Newsletter (4) (2004)Google Scholar
  20. 20.
    Mulligan, R., Altom, M., Simkin, D.: User Interface Design in the Trenches: Some Tips on Shooting from the Hip. In: Proceedings CHI 1991, pp. 232–236. ACM, New York (1991)Google Scholar
  21. 21.
    Vinter, O., Poulsen, P., Lauesen, S.: Experience Driven Software Process Improvement. In: Software Process Improvement, Brighton (1996)Google Scholar
  22. 22.
    Nielsen, J.: Web Resarch: Believe the Data. Alertbox (July 11, 1999) (2000),
  23. 23.
    Lethbridge, T.: What Knowledge Is Important to a Software Professional? IEEE Computer 33(5), 44–50 (2000)Google Scholar
  24. 24.
    Bevan, N.: Quality in Use: Meeting User Needs for Quality. Journal of Systems and Software 49(1), 89–96 (1999)CrossRefGoogle Scholar
  25. 25.
    van der Veer, G., van Vliet, H.: A Plea for a Poor Man’s HCI Component in Software Engineering and Computer Science Curricula. Computer Science Education (Special Issue: Human-Computer Interaction) 13(3), 207–226 (2003)Google Scholar
  26. 26.
    Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice, 2nd edn. Addison-Wesley, Reading (2003)Google Scholar
  27. 27.
    Bosch, J.: Software architecture: The next step. In: Oquendo, F., Warboys, B.C., Morrison, R. (eds.) EWSA 2004. LNCS, vol. 3047, pp. 194–199. Springer, Heidelberg (2004)CrossRefGoogle Scholar
  28. 28.
    Borchers, G.: The Software Engineering Impacts of Cultural Factors on Multi-cultural Software Development Teams. In: Proceedings 25th International Conference on Software Engineering (ICSE25), pp. 540–545. IEEE, Los Alamitos (2003)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Hans van Vliet
    • 1
  1. 1.Vrije UniversiteitAmsterdam

Personalised recommendations