Abstract
The University of Melbourne recently introduced a new four year engineering degree course in software engineering. This degree course includes two project subjects, each running for the duration of our academic year. Educating students through project work invariably results in tradeoffs. Exposing students to two team projects in successive years builds on the students' experience and provides a much greater opportunity to address the relevant issues than is possible with a single project. This paper examines some of the problems we have experienced in running software engineering projects and how we address these problems in our course by including a project component with two distinct parts. We also examine the overheads and other issues that arise from student projects, especially where external clients are involved. The paper is based on our experience of over one hundred different student projects with external clients over several years.
Preview
Unable to display preview. Download preview PDF.
References
Tim Arnold, Lorraine Johnston, and Philip Dart. Software engineering project manual. Department of Computer Science, The University of Melbourne, 1993.
Paul A. Bailes, Eric J. Salzman, and Andreas Rosel. A proposal for a Bachelor's degree program in software engineering. Proceedings of the Third SEI Conference on Software Engineering Education, LNCS 376, pages 90–108, 1989.
Jon Bentley. Teaching the tricks of the trade. Proceedings of the Second SEI Conference on Software Engineering Education, LNCS 327, pages 1–8, 1988.
Douglas D. Grant and Ross Smith. Undergraduate software engineering — an innovative degree at Swinburne. The Australian Computer Journal, pages 106–113, 1991.
Manmahesh Kantipudi, Ken W. Collier, James S. Collofello, and Scott Medeiros. Software engineering course projects: Failures and recommendations. Proceedings of the Sixth SEI Conference on Software Engineering Education, LNCS 640, pages 324–338, 1992.
Peter J. Knoke. Medium size project model: Variations on a theme. Proceedings of the Fifth SEI Conference on Software Engineering Education, LNCS 536, pages 5–24, 1991.
William M. Lively and Mark Lease. Undergraduate software engineering laboratory at Texas A&M University. Proceedings of the Sixth SEI Conference on Software Engineering Education, LNCS 640, pages 315–323, 1992.
Institute of Electrical and Electronic Engineers. IEEE Software Engineering Standards Collection. 1991.
R. S. Pressman. Software Engineering: A Practitioner's Approach, 3rd edition. McGraw-Hill Inc., 1992.
K. Reed and T. S. Dillon. An undergraduate software engineering major embedded in a computer systems engineering degree. Proceedings of the Fourth SEI Conference on Software Engineering Education, LNCS 423, pages 49–66, 1990.
William E. Richardson. Undergraduate software engineering education. Proceedings of the Second SEI Conference on Software Engineering Education, LNCS 327, pages 121–144, 1988.
Terence P. Rout. Quality, culture and education in software engineering. The Australian Computer Journal, pages 86–91, 1991.
Mary Shaw and James E. Tomayko. Models for undergraduate project courses in software engineering. Proceedings of the Fifth SEI Conference on Software Engineering Education, LNCS 536, pages 33–71, 1991.
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 1993 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Johnston, L., Dart, P. (1993). Building on experience: An undergraduate course with two year-long projects. In: DÃaz-Herrera, J.L. (eds) Software Engineering Education. CSEE 1994. Lecture Notes in Computer Science, vol 750. Springer, Berlin, Heidelberg. https://doi.org/10.1007/BFb0017626
Download citation
DOI: https://doi.org/10.1007/BFb0017626
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-57461-3
Online ISBN: 978-3-540-48191-1
eBook Packages: Springer Book Archive