Teaching software project management by simulation — Experiences with a comprehensive model

  • Marcus Deininger
  • Kurt Schneider
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 750)


Students of software engineering very rarely have the opportunity to gather experience in leading projects. This not only restricts their management skills, but also prevents them from learning about the project manager's point of view. We consider this lack of experience a major flaw of software engineering education. In this paper, we describe an approach to educate software engineers by simulating a software project. Students became project leaders of our simulated project and had to finish this given project successfully. To reduce biases and obtain reproducible effects, we decided to use a simple, but quantitative mathematical model. This simple model turned out to be sufficient to an amazing extent: Many effects well-known from real projects arose during the simulation. The project managers made many characteristic errors which led to plausible project distortions. The evolution of the simulated projects provided valuable feedback to teachers and students. This model is one result of our long-term project SESAM.


Project Manager Software Engineering Function Point Software Project Module Design 
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. Abdel-Hamid, T. K. (1991): Software Project Dynamics — An Integrated Approach. Prentice Hall, Englewood Cliffs, New Jersey.Google Scholar
  2. Albrecht, A. J., J. E. Gaffney (1983): Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation. IEEE Transactions on Software Engineering, SE-9, Nov. 83, 639–648.Google Scholar
  3. Boehm, B. W. (1981): Software Engineering Economics. Prentice Hall, Englewood Cliffs, New Jersey.Google Scholar
  4. Fairley, R. (1985): Software Engineering Concepts. McGraw-Hill, New York.Google Scholar
  5. IEEE(1989): Standard Dictionary of Measures to Produce Reliable Software. IEEE Std 982.1-1988.Google Scholar
  6. IEEE (1993): Standard for Software Productivity Metrics. IEEE Std. 1045.Google Scholar
  7. Knöll, H.-D., J. Busse (1991): Aufwandsschätzung von Software-Projekten in der Praxis: Methoden, Werkzeugeinsatz, Fallbeispiele. (Reihe Angewandte Informatik Bd. 8), BI-Wissenschaftsverlag, Mannheim, Wien, Zürich.Google Scholar
  8. Ludewig, J., Th. Bassler, M. Deininger, K. Schneider, J. Schwille (1992): SESAMSimulating Soft-ware Projects. Proceedings of the Software Engineering and Knowledge Engineering (SEKE) Conference, Capri, Italy.Google Scholar
  9. McCabe, T. J. (1976): A Complexity Measure. IEEE Transactions on Software Engineering, SE-2, pp. 308–320.Google Scholar
  10. McKeeman, W. M. (1989): Graduation Talk at Wang Institute. IEEE Computer, Vol. 22, No. 5, pp. 78–80.Google Scholar
  11. Schneider, K. (1993): Object-Oriented Simulation of the Software Development Process in SESAM. Proceedings of the Object-Oriented Simulation Conference (OOS '93), part of the Western Simulation Multiconference, San Diego, January 1993.Google Scholar
  12. Schneider, K. (1993a): SESAM-Zwischen Planspiel und Adventure Game. “Informatik und Schule '93”, Koblenz, Germany, October 11–13, 1993.Google Scholar
  13. Sommerville, I. (1989): Software Engineering. 3rd Edition, Addison Wessley, Workingham, England.Google Scholar
  14. Vester, F. (1987): Ökolopoly — Ein kybernetisches Umweltspiel. Otto Maier Verlag, Ravensburg, Germany.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1993

Authors and Affiliations

  • Marcus Deininger
    • 1
  • Kurt Schneider
    • 1
  1. 1.Software Engineering Group, Dept. of Computer ScienceUniversity of StuttgartStuttgartGermany

Personalised recommendations