Medium size project model: Variations on a theme

  • Peter J. Knoke
Session 1 “A Family Album Of Software Project Courses”
Part of the Lecture Notes in Computer Science book series (LNCS, volume 536)


This paper describes some recent variations on a tested theme for teaching Software Engineering in an undergraduate Computer Science program. This theme is referred to here as the Medium-Size Project Model. It has been used as the basis for an introductory Software Engineering course which has been evolving for the last 7+ years at the University of Alaska Fairbanks. The course features 3-way reality in that it uses real software development projects supplied by real customers, and the projects are conducted under realistic schedule and cost constraints in a simulated computer industry environment. Small teams of students acting as a software development company develop a software product for a customer in one semester. The scope of the software development effort is from proposal through software test and customer sell-off. Complete documentation is required, including everything from the proposal through to the customer sell-off document. A short project history is also required. The software product is expected to be developed at a "profit". Project status is monitored by frequent team presentations which cover cost and schedule as well as technical issues. Software engineering lectures are synchronized and interleaved with project reviews. Customer, student, and other feedback indicates that the course has been very successful. The 3-way reality feature is a basic reason for this success. The theme is readily portable to other educational environments, and it allows many interesting implementation variations. Current variations in the six areas of project generation, project selection, instructor roles, student team and role assignments, technical documentation, and grading bases are described.


Software Engineer Project Generation Project Selection Role Assignment Student Team 
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.

7. References

  1. [1]
    R.Gatterdam. CS 40X private communication at UAF. 11 December 1990.Google Scholar
  2. [2]
    M.Kerstetter. Answers to questions on Software Systems Development 544. E-mail correspondence on 30 Oct 1990 ( Scholar
  3. [3]
    P.Knoke. Teaching Undergraduate Software Engineering. Computer Science Education (submitted December 1990)Google Scholar
  4. [4]
    B.McSteen, B.Gottier, and M.Schmick. Software Engineering Education Directory. Technical Report CMU/SEI-90-TR-4, Software Engineering Institute, Carnegie Mellon University, April 1990.Google Scholar
  5. [5]
    B.McSteen and M.Schmick. Software Engineering Education Directory. Technical Report CMU/SEI-89-TR-10, Software Engineering Institute, Carnegie Mellon University, February 1989.Google Scholar
  6. [6]
    J.Tomayko. Teaching a Project-Intensive Introduction to Software Engineering. Technical Report CMU/SEI-87-R-171, Software Engineering Institute, Carnegie Mellon University, August 1987.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1991

Authors and Affiliations

  • Peter J. Knoke
    • 1
  1. 1.University of Alaska FairbanksUSA

Personalised recommendations