Advertisement

Engineering principles and software engineering

  • Alfs T. Berztiss
Session 13: Funding, Practica, and Principles
Part of the Lecture Notes in Computer Science book series (LNCS, volume 640)

Abstract

We identify the principal activities of engineers, formulate twelve principles of engineering in general, and establish that the problems of software engineering differ little from problems in traditional engineering. This leads to a discussion of software engineering education based on general engineering principles. Although our primary aim is to give improved structure to software engineering education, we discuss also the importance of computer science to software engineering, and show how the concepts of concurrent engineering manifest themselves in software engineering.

Keywords

Software Development Software Engineering Traditional Engineering Concurrent Engineering Engineering Principle 
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.
    M. Shaw: Prospects for an engineering discipline of software. IEEE Software 7, 6, 15–24 (Nov. 1990).Google Scholar
  2. 2.
    D.L. Parnas: Education for computing professionals. Computer 23, 1, 17–22 (Jan. 1990).Google Scholar
  3. 3.
    R. Kerr: A materialistic view of the software “engineering” analogy. ACM SIGPLAN Notices 22, 3, 123–125 (Mar. 1987).Google Scholar
  4. 4.
    W.A. Wulf: SE programs won't solve our problems. Computing Research News 3, 5, 2 (Nov. 1991).Google Scholar
  5. 5.
    B.W. Cohen, W.T. Harwood, M.I. Jackson: The Specification of Complex Systems. Wokingham, England: Addison-Wesley 1986.Google Scholar
  6. 6.
    A. Spector, D. Gifford: A computer science perspective on bridge design. Comm. ACM 29, 268–283 (1986).Google Scholar
  7. 7.
    R.H. Thayer, A.B. Pyster, R.C. Wood: Major issues in software engineering project management. IEEE Trans. Software Eng. SE-7, 333–342 (1981).Google Scholar
  8. 8.
    B. Curtis, H. Krasner, B. Iscoe: A field study of the software design process for large systems. Comm. ACM 31, 1268–1287 (1988).Google Scholar
  9. 9.
    R.N. Charette: Software Engineering Risk Analysis and Management. New York: McGraw-Hill 1989.Google Scholar
  10. 10.
    W.S. Humphrey: Managing the Software Process. Reading, MA: Addison-Wesley 1989.Google Scholar
  11. 11.
    W. Swartout, R. Balzer: On the inevitable intertwining of specification and implementation. Comm. ACM 25, 438–440 (1982).Google Scholar
  12. 12.
    R. Balzer, T.E. Cheatham, C. Green: Software technology in the 1990's: using a new paradigm. Computer 16, 11, 39–45 (Nov. 1983).Google Scholar
  13. 13.
    S.G. Shina: Concurrent Engineering and Design for Manufacture of Electronic Products. New York: Van Nostrand Reinhold 1991.Google Scholar
  14. 14.
    D.J. Yang: Boeing knocks down the wall between the dreamers and the doers. Business Week, Oct. 28, 1991, 120–121.Google Scholar
  15. 15.
    R.S. D'Ippolito, C.P. Plinta: Software development using models. Proc. 5th Workshop Software Spec. and Design, 1989, pp.140–142.Google Scholar
  16. 16.
    F.P. Brooks: No silver bullet-essence and accidents of software engineering. Proc. IFIP Congress 86, pp.1069–1076.Google Scholar
  17. 17.
    J. Rumbaugh, M. Blaha, W. Premerlani, F. Eddy, W. Lorensen: Object-Oriented Modeling and Design. Englewood Cliffs, NJ: Prentice-Hall 1991.Google Scholar
  18. 18.
    D.C. Gause, G.M. Weinberg: Exploring Requirements: Quality Before Design. New York: Dorset House 1989.Google Scholar
  19. 19.
    J.H. August: Joint Application Design. Englewood Cliffs, NJ: Yourdon Press 1991.Google Scholar
  20. 20.
    C.U. Smith: Performance Engineering of Software Systems. Reading, MA: Addison-Wesley 1990.Google Scholar
  21. 21.
    P.B. Crosby: Quality Without Tears. New York: McGraw-Hill 1984.Google Scholar
  22. 22.
    T. Anderson, P.A. Lee: Fault Tolerance: Principles and Practice. Englewood Cliffs, NJ: Prentice-Hall 1981.Google Scholar
  23. 23.
    C. Lins: The Modula-2 Software Component Library, Vols. 1–4. New York: Springer-Verlag 1989–1990.Google Scholar
  24. 24.
    J.D. Musa, A. Iannino, K. Okumoto: Software Reliability — Measurement, Prediction, Application. New York: McGraw-Hill 1987.Google Scholar
  25. 25.
    N.G. Leveson: Software safety: what, why, and how. ACM Comp. Surveys 18, 125–163 (1986).Google Scholar
  26. 26.
    R.H. Cobb, H.D. Mills: Engineering software under statistical quality control. IEEE Software 7, 6, 44–54 (Nov. 1990).Google Scholar
  27. 27.
    M. Dyer: The Cleanroom Approach to Quality Software Development. New York: Wiley 1992.Google Scholar
  28. 28.
    J.W. Duran, S.C. Ntafos: An evaluation of random testing. IEEE Trans. Software Eng. SE-10, 438–444 (1984).Google Scholar
  29. 29.
    P.A. Currit, M. Dyer, H.D. Mills: Certifying the reliability of software. IEEE Trans. Software Eng. SE-12 (1986), 3–11.Google Scholar
  30. 30.
    H.R. Berlack: Software Configuration Management. New York: Wiley 1992.Google Scholar
  31. 31.
    B.W. Boehm (ed.): Software Risk Management. Washington, DC: IEEE Computer Society Press 1989.Google Scholar
  32. 32.
    Staff of QED Information Sciences: CASE: The Potential and the Pitfalls. Wellesley, MA: QED Information Sciences 1989.Google Scholar
  33. 33.
    A. Berztiss: A mathematically focused curriculum for computer science. Comm. ACM 30, 356–365 (1987).Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1992

Authors and Affiliations

  • Alfs T. Berztiss
    • 1
    • 2
  1. 1.Department of Computer ScienceUniversity of PittsburghPittsburghUSA
  2. 2.SYSLABUniversity of StockholmSweden

Personalised recommendations