Skip to main content

Design evolution: Implications for academia and industry

  • Session 5 “Teaching Design”
  • Conference paper
  • First Online:
Software Engineering Education (SEI 1991)

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

Included in the following conference series:

Abstract

Design technology has grown over the last thirty years in response to improved programming languages and a rapidly expanding software problem domain. Faced with rapidly developing design approaches, it is vital that a meta-study of design be accomplished periodically in order to keep this growth in perspective. Such a study is necessary to determine how design can be most effectively integrated into undergraduate computer science programs and how design should be taught and applied in industry.

This paper represents a brief summary of a recent meta-study of design. In this study, design growth, seen as an evolution, was charted and a taxonomy of design approaches was produced. From this taxonomy, design approaches were analyzed in terms of their underlying theory and were categorized into generations. The results of this study, as presented here, are recommendations for the integration of design into undergraduate computer science programs with a software engineering component and recommendations for the training and use of design in the industrial sector.

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

Access this chapter

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Bibliography

  1. Grady Booch, Software Engineering with Ada, Benjamin/Cummings Publishing Company, 1983.

    Google Scholar 

  2. Grady Booch, Object Oriented Design with Applications, Benjamin/Cummings Publishing Company, 1991.

    Google Scholar 

  3. J. R. Cameron, "An Overview of JSD," IEEE Transactions on Software Engineering, February 1986.

    Google Scholar 

  4. Michael J. Clancy and Marcia C. Linn, "Functional Fun," SIGCSE Bulletin, Vol 22, Feb 1990.

    Google Scholar 

  5. Peter Coad and Edward Yourdon, Object Oriented Analysis, Prentice-Hall, Inc., 1990.

    Google Scholar 

  6. L. L. Constantine and E. Yourdon, Structured Design, Prentice-Hall, Inc., 1979.

    Google Scholar 

  7. Richard Fairley, Software Engineering Concepts, McGraw-Hill, Inc., 1985.

    Google Scholar 

  8. Thomas S. Frank and James F. Smith, "Ada as a CS1-CS2 Language," SIGCSE Bulletin, Vol 22, June 1990.

    Google Scholar 

  9. Brian Henderson-Sellers and Julian M. Edwards, "The Object-Oriented Systems Life Cycle," Communications of the ACM, September 1990.

    Google Scholar 

  10. M. A. Jackson, Principles of Program Design, Academic Press, Inc., 1975.

    Google Scholar 

  11. M. A. Jackson, System Development, Prentice-Hall, Inc., 1983.

    Google Scholar 

  12. Barbara Liskov and John Guttag, Abstraction and Specification in Program Development, McGraw-Hill, Inc., 1986.

    Google Scholar 

  13. B. Meyer, Object-Oriented Software Construction, Prentice-Hall, Inc., 1988.

    Google Scholar 

  14. Glenford J. Myers, Composite/Structured Design, Van Nostrand Reinhold Company, 1978.

    Google Scholar 

  15. Linda Northrop, "Success with the Project-Intensive Model for an Undergraduate Software Engineering Course," SIGCSE Bulletin, Vol 21, Feb 1989

    Google Scholar 

  16. Linda Northrop, Software Engineering, Product Software Engineering Training, Eastman Kodak Company, Rochester, New York, 1990.

    Google Scholar 

  17. D. L. Parnas, "On the Criteria To Be Used in Decomposing Systems into Modules," Communications of the ACM, December 1972.

    Google Scholar 

  18. John Pugh, "Object-Oriented Programming in the Computer Science Curriculum," SIGCSE Bulletin, Vol 22, Feb 1990

    Google Scholar 

  19. Roger S. Pressman, Software Engineering: A Practitioner's Approach,Second Edition, McGraw-Hill, Inc., 1982.

    Google Scholar 

  20. William E. Richardson, "Undergraduate Software Engineering Education" in Software Engineering Education, edited by G. Ford, Springer-Verlag, New York, 1988.

    Google Scholar 

  21. Douglas T. Ross and Kenneth E. Schoman, Jr., "Structured Analysis for Requirements Definition," IEEE Transactions on Software Engineering, January 1977.

    Google Scholar 

  22. James Tomayko, Teaching a Project-Intensive Introduction to Software Engineering, Special Report, Software Engineering Institute, Carnegie-Melon University, March 1987.

    Google Scholar 

  23. P. Ward and S. Mellor, Structured Development for Real-Time Systems, Prentice-Hall, Inc., 1985.

    Google Scholar 

  24. Niklaus Wirth, "Program Development by Stepwise Refinement," Communications of the ACM, April 1971.

    Google Scholar 

  25. Niklaus Wirth, Algorithms and Data Structures, Prentice-Hall, Inc., 1986.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

James E. Tomayko

Rights and permissions

Reprints and permissions

Copyright information

© 1991 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Northrop, L.M., Richardson, W.E. (1991). Design evolution: Implications for academia and industry. In: Tomayko, J.E. (eds) Software Engineering Education. SEI 1991. Lecture Notes in Computer Science, vol 536. Springer, Berlin, Heidelberg. https://doi.org/10.1007/BFb0024293

Download citation

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

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-54502-6

  • Online ISBN: 978-3-540-38418-2

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics