Skip to main content
SpringerLink
Log in
Book cover

Conference on Software Engineering Education

CSEE 1994: Software Engineering Education pp 329–340Cite as

Suggested scenarios of software maintenance education

  • Conference paper
  • First Online:

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

Abstract

To improve the quality of software maintenance work and to reduce the time taken to perform maintenance tasks, programmers need to be educated on how to maintain programs. Despite the complexity of software maintenance and the need for informed maintainers, there are few training programs or academic courses aimed at developing the skills that are required of maintenance programmers. In this paper we will look at four different scenarios for teaching software maintenance. These scenarios will be suitable for industrial training as well as university or college courses and are based on courses on software maintenance that the authors have given in industry and academia.

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

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. B.W. Boehm, “Software Engineering,” IEEE Transactions on Computers, vol. C-25, no. 12, pp. 25–32, December 1976.

    Google Scholar 

  2. F.W. Calliss and B.J. Cornelius, “Two Module Factoring Techniques,” The Journal of Software Maintenance — Research and Practice, vol. 1, no. 2, pp. 81–89, December 1989.

    Google Scholar 

  3. F.W. Calliss and D.L. Trantina, “A Controlled Software Maintenance Project,” Software Engineering Education (SEI Conference), Springer-Verlag, Lecture Notes in Computer Science 536, pp. 25–32, October 1991.

    Google Scholar 

  4. N. Chapin, “The Job of Software Maintenance,” in Proceedings of the Conference on Software Maintenance — 1987, IEEE Computer Society Press, pp. 4–12, 1987.

    Google Scholar 

  5. E.J. Chikofsky and J.H. Cross II, “Reverse Engineering and Design Recovery: A Taxonomy,” IEEE Software, vol. 7, no. 1, pp. 13–17, January 1990.

    Article  Google Scholar 

  6. J.S. Collofello, The Software Technical Review Process, SEI Curriculum Module SEI-CM-3-1.5, June 1988.

    Google Scholar 

  7. J.S. Collofello and S.N. Woodfield, “Evaluating the Effectiveness of Reliability-Assurance Techniques,” Journal of Systems and Software, pp. 191–195, 1989.

    Google Scholar 

  8. C.B. Engle, G. Ford and T. Korson, Software Maintenance Exercises for a Software Engineering Project Course, SEI Curriculum Module CMU/SEI-89-EM1, February 1989.

    Google Scholar 

  9. S.A. Gamalel-Din and L.J. Osterweil, “New Perspectives on Software Maintenance Processes,” in Proceedings of the Conference on Software Maintenance — 1988, IEEE Computer Society Press, pp. 14–22, 1988.

    Google Scholar 

  10. W. Harrison, K. Magel, R. Kluczny, and A. DeKock, “Applying Software Complexity Metrics to Program Maintenance,” Computer, pp. 65–79, September 1982.

    Google Scholar 

  11. C.H. Kepner and B.B. Trogoe, The New Rational Manager, Princeton Research Press, New Jersey, 1981.

    Google Scholar 

  12. M.M. Lehman, “On Understanding Laws, Evolution, and Conservation in the Large-Program Life Cycle,” The Journal of Systems and Software, vol. 1, pp. 213–221, 1980.

    Article  Google Scholar 

  13. B.P. Lientz and E.B. Swanson, Software Maintenance Management, Addison-Wesley, Reading, Massachusetts, 1980.

    Google Scholar 

  14. R.S. Pressman, Software Engineering: A Practitioners Approach, McGraw-Hill, 1992.

    Google Scholar 

  15. B. Schwartz, “Eight Myths about Software Maintenance,” Datamation, August 1982.

    Google Scholar 

  16. N.F. Schneidewind, “The State of Software Maintenance,” IEEE Transactions on Software Engineering, vol. SE-13, no. 3, pp. 303–310, March 1987.

    Google Scholar 

  17. E. Soloway and K. Ehrlich, “Empirical Studies of Programming Knowledge,” IEEE Transactions on Software Engineering, vol. SE-10, no. 5, pp. 595–609, March 1984.

    Google Scholar 

  18. M. Weiser, “Programmers use Slices When Debugging,” Communications of the ACM, vol. 25, no. 7, pp. 446–452, July 1982.

    Article  Google Scholar 

  19. N. Wilde, Understanding Program Dependencies, SEI Curriculum Module SEI-CM-26, August 1990.

    Google Scholar 

  20. M.H. Williams and H.L. Ossher, “Conversion of Unstructured Flow Diagrams to Structured Form,” The Computer Journal, vol. 21, no. 2, pp. 161–167, May 1978.

    Google Scholar 

  21. S.S. Yau and J.S. Collofello, “Some Stability Measures for Software Maintenance,” IEEE Transactions on Software Engineering, vol. SE-6, no. 6, pp. 545–552, November 1980.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Department of Computer Science and Engineering College of Engineering and Applied Sciences, Arizona State University, Box 875406, 85287-5406, Tempe, AZ, USA

    Frank W. Calliss & Debra Trantina Calliss

Authors
  1. Frank W. Calliss
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Debra Trantina Calliss
    View author publications

    You can also search for this author in PubMed Google Scholar

Editor information

Jorge L. Díaz-Herrera

Rights and permissions

Reprints and permissions

Copyright information

© 1993 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Calliss, F.W., Calliss, D.T. (1993). Suggested scenarios of software maintenance education. 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/BFb0017624

Download citation

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

  • 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

Publish with us

Policies and ethics

Search

Navigation