Advertisement

Essential knowledge for the practising software engineer and the responsibilities of university and industry for her education

  • Lin Zucconi
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 895)

Abstract

It is becoming quite apparent that knowledge of computer science and software engineering alone is inadequate for the practising software engineer to be truly successful in an industrial setting. Often in practice, “programmers” lack knowledge of the foundation concepts of computer science and software engineering. The result is that it is difficult to guarantee the production of high quality systems to fixed deadlines. Through discussions with members of an industry-university coalition and more than twenty years of observation, the author has observed that in order for a software engineer to be successful in all aspects, she requires a good amount of knowledge beyond that of computer science and software engineering.

In this paper the author proposes a five item set of essential knowledge for the practising software engineer. These five areas of knowledge and capability are necessary for the software engineer to achieve broad competency. They are:
  1. 1.

    Systems and software engineering and computer science

     
  2. 2.

    Hardware platform-specific knowledge,

     
  3. 3.

    Application domain,

     
  4. 4.

    Personal and interpersonal skills, ethics, and

     
  5. 5.

    Business culture.

     

The features of this knowledge base are elaborated. Additionally a partitioning of educational responsibility is proposed between university and industry. The author discusses some preliminary concepts for a university-industry education collaboration which would benefit both classes of institutions as well as noticeably increase the first time success of new software engineering graduates.

Keywords

Software Engineering Software Engineer Lawrence Livermore National Laboratory Business Culture Software Process Improvement 
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]
    “ACM Code of Ethics and Professional Conduct, draft”, CACM, Vol. 35, No. 5, May 1992Google Scholar
  2. [2]
    “ACM Model High School Computer Science Curriculum, Task Force of the Pre-College Commission of the Education Board of the ACM,” CACM, Vol. 36, No. 5, May 1993Google Scholar
  3. [3]
    Mark Ardis, “The Evolution of Wang Institute's Master of Software Engineering Program,” IEEE Trans. on Software Engineering, Vol. SE-13, No. 11, Nov. 1987 pp. 1149–1155Google Scholar
  4. [4]
    Victor Basili, Frank McGarry, and Dana Hall, “Starting an Experience Factory,” special tutorial at the 17th Annual Software Engineering Workshop, Dec. 1992, NASA GSFC, Greenbelt, MarylandGoogle Scholar
  5. [5]
    Frank P. Coyle, Edward Forest, and Murat M. Tanik, “Meeting the Needs of Industry: SMU's Master's Degree,” Proc. of the 7th SEI CSEE Conference, Jan. 1994, Springer-Verlag, Lecture Notes in Computer Science 750, Jorge L. Diaz-Herrera (Ed.), 1994Google Scholar
  6. [6]
    —, Scaling Up: A Research Agenda for Software Engineering, Computer Science and Technology Board, National Research Council, National Academy Press, Washington, D.C., 1989Google Scholar
  7. [7]
    Richard G. Epstein, “The Use of Computer Ethics Scenarios in Software Engineering Education: The Case of the Killer Robot,” Proc. of the 7th SEI CSEE Conference, Jan. 1994, Springer-Verlag, Lecture Notes in Computer Science 750, Jorge L. Diaz-Herrera (Ed.), 1994Google Scholar
  8. [8]
    Norman Fenton, Shari Lawrence Pfleeger, and Robert Glass, “Science and Substance: A Challenge to Software Engineers,” IEEE Software, Vol. 11, No. 4, July 1994, pp. 86–95Google Scholar
  9. [9]
    Gary Ford, “1990 SEI Report on Undergraduate Software Engineering Education, ”CMU/SEI-90-TR-3, Software Engineering Institute, March 1990Google Scholar
  10. [10]
    Gary Ford, “1991 SEI Report on Graduate Software Engineering Education,” CMU/SEI-91-TR-2, Software Engineering Institute, April 1991Google Scholar
  11. [11]
    Peter Freeman, “Essential Elements of Software Engineering Education Revisited,” IEEE Trans. on Software Engineering, Vol. SE-13, No. 11, Nov. 1987, pp. 1143–1148Google Scholar
  12. [12]
    Batya Friedman and Peter H. Kahn, Jr., “Educating Computer Scientists: Linking the Social and the Technical,” CACM, Vol. 37, No. 1, January 1994, pp. 65–70Google Scholar
  13. [13]
    Jared T. Freeman, Thomas R. Riedl, Julian S. Weitzenfeld, Gary A. Klein, and John Musa, “Instruction for Software Engineering Expertise,” Proc. of the Software Engineering Education SEI Conference, October 1991, Springer-Verlag, Lecture Notes in Computer Science 536, J.E. Tomayko (Ed.)Google Scholar
  14. [14]
    Douglas D. Grant, “Software Engineering Education in the 1990s — The Way Forward,” Proc. of the Software Engineering Education SEI Conference, Oct. 1992, Springer-Verlag, Lecture Notes in Computer Science 640, C. Sledge (Ed.)Google Scholar
  15. [15]
    Horning, J.J. and Wortman, D.B. “Software Hut: A computer program engineering project in the form of a game”, IEEE Trans. on Software Engineering vol. SE-3, No. 4, July 1977, pp. 325–330Google Scholar
  16. [16]
    —, “Software Engineering Education Resources — Proceedings of the ACM/IEEE International Workshop on Software Engineering Education,” May 21, 1994, Sorrento, ItalyGoogle Scholar
  17. [17]
    Frank McGarry, “Experimental Software Engineering — 17 Years of Lessons in the SEL,” Proc. of the 17th Annual Software Engineering Workshop, Dec. 1992, NASA GSFC, Greenbelt, MarylandGoogle Scholar
  18. [18]
    John W. Priest, Wayne Bodensteiner, and Nan K. Muir, “A Survey of Educational and Training Needs for Transition of a Product from Development to Manufacturing,” IEEE Trans. on Education, Vol. 37, No. 1, February 1994, pp. 13–22Google Scholar
  19. [19]
    Karl Reed and Tharam S. Dillon, “An Undergraduate Software Engineering Major Embedded in a Computer Systems Engineering Degree,” Proc. Software Engineering Education SEI Conference 1990, Pittsburgh, PA, April 1990, pp. 49–66Google Scholar
  20. [20]
    Allen B. Tucker, Ed, “A Summary of the ACM/EEEE-CS Joint Task Force Report-Computing Curricula 1991”, CACM, Vol. 34. No. 6, June 1991, pp. 68–84Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1995

Authors and Affiliations

  • Lin Zucconi
    • 1
    • 2
  1. 1.Collaborative Information Technology Institute Royal Melbourne Institute of TechnologyCarltonAustralia
  2. 2.Software Technology CenterLawrence Livermore National LaboratoryLivermoreUSA

Personalised recommendations