Skip to main content
SpringerLink
Log in

SEI report on graduate software engineering education

  • 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:

Abstract

A report on the SEI's 1988 Curriculum Design Workshop is provided, along with descriptions of the six core courses for a Master of Software Engineering degree program that were designed at that workshop. A summary of current SEI recommendations for such a degree program is also included.

This work was sponsored by the US Department of Defense.

This report is an abridged version of an SEI technical report [Ardis89].

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.

References

  1. Ardis, M., and Ford, G., 1989 SEI Report on Graduate Software Engineering Education. Tech. Rep. CMU/SEI-89-TR-21, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pa., June 1989.

    Google Scholar 

  2. Bloom, B. Taxonomy of Educational Objectives: Handbook I: Cognitive Domain. New York: David McKay, 1956.

    Google Scholar 

  3. Ford, G., Gibbs, N., and Tomayko, J. Software Engineering Education: An Interim Report from the Software Engineering Institute. Tech. Rep. CMU/SEI-87-TR-8, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pa., May 1987.

    Google Scholar 

  4. Software Engineering Education: The Educational Needs of the Software Community. Norman E. Gibbs; Richard E. Fairley, eds. New York: Springer-Verlag, 1987.

    Google Scholar 

  5. Webster's Ninth New Collegiate Dictionary. Springfield, Mass.: Merriam-Webster Inc., 1983.

    Google Scholar 

Bibliography

  1. Agresti, W.W. “What Are the New Paradigms?.” Tutorial: New Paradigms for Software Development, William W. Agresti, ed. IEEE Computer Society, 1986.

    Google Scholar 

  2. Bartussek, W., and Parnas, D.L. “Using Assertions About Traces to Write Abstract Specifications for Software Modules.” Proc. of Second Conf. of European Cooperation in Informatics. 1978.

    Google Scholar 

  3. Bjørner, D. “Programming in the Meta-Language: A Tutorial.” The Vienna Development Method: The Meta-Language, Dines Bjørner; Cliff B. Jones, eds. New York: Springer-Verlag, 1978, 24–217.

    Google Scholar 

  4. Bjørner, D., and Jones, C.B. Formal Specification and Software Development. Englewood Cliffs, N.J.: Prentice-Hall, 1982.

    Google Scholar 

  5. Guttag, J. V. “Notes on Type Abstraction.” Proc. SRS Conf.. 1979.

    Google Scholar 

  6. Guttag, J. V., and Horning, J. J. “Formal Specification as a Design Tool.” Seventh Symp. Principles of Prog. Lang.. ACM, 1980.

    Google Scholar 

  7. Guttag, J. V., Horning, J. J., and Wing, J. M. “The Larch Family of Specification Languages.” IEEE Software 2, 5 (Sept. 1985), 24–36.

    Google Scholar 

  8. Harel, D. “Statecharts: A Visual Formalism for Complex Systems.” Science of Computer Programming 8 (1987), 231–274.

    Article  MATH  MathSciNet  Google Scholar 

  9. Hoare, C. A. R. “Communicating Sequential Processes.” Comm. ACM 21, 8 (Aug. 1978), 666–677.

    Article  MATH  MathSciNet  Google Scholar 

  10. Jones, C. B. “Systematic Program Development.” Proc. Symposium on Mathematics and Computer Science. 1986.

    Google Scholar 

  11. Parnas, D. L. “A Technique for Software Module Specification with Examples.” Comm. ACM 15, 5 (May 1972), 330–336.

    Article  Google Scholar 

  12. Peterson, J. L. “Petri Nets.” Computing Surveys 9, 3 (Sept. 1977), 223–252.

    Article  MATH  MathSciNet  Google Scholar 

  13. Zave, P., and Yeh, R. T. “Executable Requirements for Embedded Systems.” Proc. Fifth Intl. Conf. Soft. Eng.. New York: IEEE, 1981, 295–304.

    Google Scholar 

  14. Zave, P. “An Operational Approach to Requirements Specification for Embedded Systems.” Trans. Soft. Eng. SE-8, 3 (May 1982), 250–269.

    Google Scholar 

Bibliography

  1. Dijkstra, E. “The Structure of the THE-Multiprogramming System.” Comm. ACM 11, 5 (May 1968), 341–346.

    Article  MATH  Google Scholar 

  2. Gane, C., and Sarson, T. Structured Systems Analysis: Tools and Techniques. Englewood Cliffs, N.J.: Prentice-Hall, 1979.

    Google Scholar 

  3. Jackson, M. Principles of Program Design. London: Academic Press, 1975.

    Google Scholar 

  4. Jackson, M. System Development. Englewood Cliffs, N.J.: Prentice-Hall, 1983.

    Google Scholar 

  5. Liskov, B., and Guttag, J. Abstraction and Specification in Program Development. New York: McGraw-Hill, 1986.

    Google Scholar 

  6. Mills, H. D., Linger, R. C., and Hevner, A. R. Principles of Information Systems Analysis and Design. Academic Press, 1986.

    Google Scholar 

  7. Parnas, D.L., and Weiss, D.M. “Active Design Reviews: Principles and Practices.” Proc. 8th Intl. Conf. Soft. Eng.. IEEE Computer Society Press, 1985, 132–136.

    Google Scholar 

  8. Wirth, N. “Program Development by Stepwise Refinement.” Comm. ACM 14, 4 (Apr. 1971).

    Google Scholar 

  9. Yourdon, E., and Constantine, L. Structured Design: Fundamentals of a Discipline of Computer Program and Systems Design. Englewood Cliffs, N.J.: Prentice-Hall, 1979.

    Google Scholar 

Bibliography

  1. Bentley, J. L. Writing Efficient Programs. Englewood Cliffs, N.J.: Prentice-Hall, 1982.

    Google Scholar 

  2. Bentley, J. L. Programming Pearls. Reading, Mass.: Addison-Wesley, 1986.

    Google Scholar 

  3. Boehm, B. W. “A Spiral Model of Software Development and Enhancement.” Computer 21, 5 (May 1988), 61–72.

    Article  Google Scholar 

  4. Britcher, R. N., and Craig, J. J. “Using Modern Design Practices to Upgrade Aging Software Systems.” IEEE Software 3, 3 (May 1986), 16–24.

    Google Scholar 

  5. Clapp, J. A. “Designing Software for Maintainability.” Computer Design 20, 9 (Sept. 1981).

    Google Scholar 

  6. Cleveland, L. An Environment for Understanding Programs. Tech. Rep. 12880, IBM, 1987.

    Google Scholar 

  7. Collofello, J. S., and Buck, J. J. “Software Quality Assurance for Maintenance.” IEEE Software 4, 5 (Sept. 1987), 46–51.

    Google Scholar 

  8. Freeman, P. Software Perspectives: The System is the Message. Reading, Mass.: Addison-Wesley, 1987.

    Google Scholar 

  9. Glass, R., and Noiseux, R. A. Software Maintenance Guidebook. Englewood Cliffs, N.J.: Prentice-Hall, 1981.

    Google Scholar 

  10. Goldberg, A. “Programmer as Reader.” IEEE Software 4, 5 (Sept. 1987), 62–70. Reprinted from Information Processing 86, H. J. Kugler, ed., North-Holland, Amsterdam, 1986.

    Google Scholar 

  11. Grady, R. B. “Measuring and Managing Software Maintenance.” IEEE Software 4, 5 (Sept. 1987), 35–45.

    Google Scholar 

  12. Gremillion, L. L. “Determinants of Program Repair Maintenance Requirements.” Comm. ACM 27, 8 (Aug. 1984), 826–832.

    Article  Google Scholar 

  13. Holbrook, H. B., and Thebaut, S. M. A Survey of Maintenance Tools that Enhance Program Understanding. Tech. Rep. SERC-TR-9-F, Soft. Eng. Res. Ctr., Purdue Univ.-Univ. of Florida, Sept. 1987.

    Google Scholar 

  14. Ince, D. C. “A Program Design Language Based Software Maintenance Tool.” Software Practice and Experience 15, 6 (June 1985).

    Google Scholar 

  15. Lehman, M. M. “A Further Model of Coherent Programming Processes.” Proc. Software Process Workshop, Colin Potts, ed. IEEE Computer Society Press, Feb. 1984, 27–34.

    Google Scholar 

  16. Lehman, M. M. Program Evolution: Processes of Software Change. London: Academic Press, 1985.

    Google Scholar 

  17. Lientz, B. P., and Swanson, E. Software Maintenance Management. Reading, Mass.: Addison-Wesley, 1980.

    Google Scholar 

  18. Linger, R. C., Mills, H. D., and Witt, B. I. Structured Programming: Theory and Practice. Reading, Mass.: Addison-Wesley, 1979.

    Google Scholar 

  19. Martin, J., and McClure, C. Software Maintenance: The Problem and Its Solutions. Englewood Cliffs, N.J.: Prentice-Hall, 1983.

    Google Scholar 

  20. Parnas, D. L. “Designing Software for Ease of Extension and Contraction.” Trans. Soft. Eng. SE-5, 2 (Mar. 1979).

    Google Scholar 

  21. Shneiderman, B., Shafer, P., Simon, R., and Weldon, L. “Display Strategies for Program Browsing: Concept and Experiment.” IEEE Software 3, 3 (May 1986), 7–15.

    Google Scholar 

  22. Wegner, P. “Capital-Intensive Software Technology.” IEEE Software 1, 3 (July 1984), 7–45.

    Google Scholar 

  23. Wilde, N., and Nejmeh, B. Dependency Analysis: An Aid for Software Maintenance. Tech. Rep. SERC-TR-13-F, Soft. Eng. Res. Ctr., Purdue Univ.-Univ. of Florida, Sept. 1987.

    Google Scholar 

  24. Wilde, N., and Thebaut, S. M. The Maintenance Assistant: Work in Progress. Tech. Rep. SERC-TR-10-F, Soft. Eng. Res. Ctr., Purdue Univ.-Univ. of Florida, Sept. 1987. To be published in Journal of Systems and Software.

    Google Scholar 

Bibliography

  1. Dijkstra, E. A Discipline of Programming. Englewood Cliffs, N.J.: Prentice-Hall, 1976.

    Google Scholar 

  2. Goodenough, J. B., and Gerhart, S. L. “Toward a Theory of Test Data Selection.” Trans. Soft. Eng. SE-1, 2 (June 1975).

    Google Scholar 

  3. Guttag, J. V., Horowitz, E., and Musser, D. R. “Abstract Data Types and Software Validation.” Comm. ACM 21, 12 (Dec. 1978), 1048–1064.

    Article  MathSciNet  Google Scholar 

  4. Hoare, C. A. R. “Procedures and Parameters — An Axiomatic Approach.” Symp. Semantics of Algor. Lang., E. Engeler, ed. 1971.

    Google Scholar 

  5. Mills, H. D., Basili, V. R., Gannon, J. D., and Hamlet, R. G. Principles of Computer Programming, A Mathematical Approach. Allyn and Bacon, 1986.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Software Engineering Institute, USA

    Mark Ardis & Gary Ford

Authors
  1. Mark Ardis
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Gary Ford
    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

Ardis, M., Ford, G. (1989). SEI report on graduate software engineering education. 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/BFb0042361

Download citation

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

  • 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