Advertisement

Use of the individual exchange project model in an undergraduate software engineering laboratory

  • J. Kaye GrauEmail author
  • Norman Wilde
Session 11: Laboratory and Project Experiences
Part of the Lecture Notes in Computer Science book series (LNCS, volume 640)

Abstract

Organization of undergraduate project work in software engineering is always difficult because of the students' very limited computing experience. Many related concepts need to be introduced almost simultaneously: the software life cycle, the use of documentation standards, the need to use documents produced by others, the role of CASE, and the importance of configuration management. This paper describes an Individual Exchange Project Model that has been used effectively in the University of West Florida's undergraduate Software Engineering Laboratory. This model involves individuals working in small teams to develop miniature programs. Each individual carries out the entire development process exchanging intermediate documents among team members.

Keywords

Software Engineering Software Engineer Design Document Case Tool Student Comment 
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.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Cabral, G.; Dunsmore, H. E.; Stratton, S.; Zage, D. M.; Zage, W. M.; “An Evaluation of Excelerator,” SERC-TR-15-P, Software Engineering Research Center, Purdue University, West Lafayette, IN 47907, May, 1988.Google Scholar
  2. 2.
    Cabral, G.; Dunsmore, H. E.; Stratton, S.; Zage, D. M.; Zage, W. M.; “An Evaluation of Teamwork,” SERC-TR-16-P, Software Engineering Research Center, Purdue University, West Lafayette, IN 47907, May, 1988.Google Scholar
  3. 3.
    IDE; “Software through Pictures User Manual”, Interactive Development Environments, 595 Market St., San Francisco, CA 94105, December 1990.Google Scholar
  4. 4.
    ANSI/IEEE Std 830-1984, “IEEE Guide to Software Requirements Specification,” IEEE: New York, NY, 1984.Google Scholar
  5. 5.
    Index Technology Corporation, “Excelerator Reference Guide”, Index Technology Corp., One Main Street, Cambridge, Ma. 02142, 1987.Google Scholar
  6. 6.
    Knoke, Peter J.; “Medium Size Project Model: Variations on a Theme”, Software Engineering Education, Proceedings of the 1991 SEI Conference, Pittsburgh, PA, October 1991.Google Scholar
  7. 7.
    Selby, Richard; Basili, Victor; Baker, F. Terry; “Cleanroom Software Development: An Empirical Evaluation,” IEEE Transactions on Software Engineering, Vol. SE-13, No. 9 (September 1987), pp.1027–37.Google Scholar
  8. 8.
    Shaw, Mary; Tomayko, James; “Models for Undergraduate Project Courses in Software Engineering”, Software Engineering Education, Proceedings of the 1991 SEI Conference, Pittsburgh, PA, October 1991.Google Scholar
  9. 9.
    Voelcker, John, “Automating Software: Proceed With Caution”, IEEE Spectrum, Vol. 25, No. 7, pp. 25–27, July, 1988.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1992

Authors and Affiliations

  1. 1.Division of Computer ScienceUniversity of West FloridaPensacola

Personalised recommendations