Skip to main content
SpringerLink
Log in

Teaching software maintenance

  • Section I Third SEI Conference On Software Engineering Education
  • Conference paper
  • First Online:
Software Engineering Education (SEI 1989)

Part of the book series: Lecture Notes in Computer Science ((LNCS,volume 376))

Included in the following conference series:

  • 130 Accesses

Abstract

An often-cited problem in software engineering education is that many of the relevant topics are difficult to address in a university setting. Though project work is a useful supplement to the lectures, it is very difficult to make the project truly realistic. In our environment therefore, we decided not to try to mimic all aspects of reality. Rather, we try to concentrate on a few aspects which can be realistically dealt with in a university environment. In this paper we describe a project which concentrates on maintenance activities. Independent evaluations by both students and project instructors reveal that these maintenance activities were most seriously hampered by inappropriate documentation at the component level.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

6. References

  1. F.P. Brooks, People are our most important product, in N.E. Gibbs & R.E. Fairley (Eds.), Software Engineering Education, Springer Verlag (1987) pp 1–15.

    Google Scholar 

  2. S. van Egmond & J. Warmer, The Implementation of the Amsterdam SGML Parser, Report IR-159, Department of Mathematics and Computer Science, Vrije Universiteit, 1988.

    Google Scholar 

  3. R. Fairley, Software Engineering Concepts, McGraw-Hill, 1985.

    Google Scholar 

  4. N.E. Gibbs & R.E. Fairley (Eds), Software Engineering Education, Springer-Verlag, 1987.

    Google Scholar 

  5. IEEE Guide to Software Requirements Specifications, IEEE Std 830, 1984.

    Google Scholar 

  6. IEEE Recommended practice for Software Design Descriptions, IEEE Std 1016, 1987.

    Google Scholar 

  7. Information Processing — Text and Office Systems — Standard Generalized Markup Language (SGML), first edition, 1986-10-15, Ref no ISO8879-1986 (E).

    Google Scholar 

  8. R.S. Pressman, Software Engineering, McGraw-Hill, 1987.

    Google Scholar 

  9. E. Soloway et al, Designing software documentation to compensate for delocalized plans, Comm. of the ACM 31, 11 (1988) pp 1259–1267.

    Article  Google Scholar 

  10. D.F. Stubbs & N.W. Webre, Data Structures with Abstract Data Types and Modula-2, Brooks/Cole, 1987.

    Google Scholar 

  11. A.S. Tanenbaum, Computer Organization, second edition, Prentice-Hall, 1984.

    Google Scholar 

  12. J.C. van Vliet, Software Engineering, Stenfert Kroese, 1988.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Department of Mathematics and Computer Science, Vrije Universiteit, De Boelelaan 1081, 1081 HV, Amsterdam, The Netherlands

    J. C. van Vliet

Authors
  1. J. C. van Vliet
    View author publications

    You can also search for this author in PubMed Google Scholar

Editor information

Norman E. Gibbs

Rights and permissions

Reprints and permissions

Copyright information

© 1989 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

van Vliet, J.C. (1989). Teaching software maintenance. In: Gibbs, N.E. (eds) Software Engineering Education. SEI 1989. Lecture Notes in Computer Science, vol 376. Springer, New York, NY. https://doi.org/10.1007/BFb0042351

Download citation

  • DOI: https://doi.org/10.1007/BFb0042351

  • Published:

  • Publisher Name: Springer, New York, NY

  • Print ISBN: 978-0-387-97090-5

  • Online ISBN: 978-0-387-34791-2

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics

Search

Navigation