A Software Engineering Graduate Curriculum

  • Authors:

  • Leon G. Stucki;Lawrence J. Peters

  • Affiliations:

  • -;-

  • Venue:
  • ACM '78 Proceedings of the 1978 annual conference
  • Year:
  • 1978

Quantified Score

Hi-index 0.00

Visualization

Abstract

Picking up any large city Sunday paper one cannot help but be impressed by the large demand for “software engineers.” Upon reflection, several questions are raised: Who are these mythical software engineers? What do they do? Where do they come from? Why are they here? Where are they going? Industry and government alike are crying out for software engineers while universities have yet to establish any real software engineering curricula. The state of affairs is actually even more complex than this in that we don't even really know who these mythical software engineers are. In fact, the term “software engineering” is not commonly agreed upon as to its exact meaning. People in the field are not sure what terminology best describes the nature of their work [1, 2]. During a recent software engineering conference approximately 500 attendees were asked their formal occupation; approximately 20% of those in attendance indicated that they were software engineers. The others used terms such as: Systems Analyst, Programmers, Managers, etc. All of these jobs contain elements (technical and managerial) of software engineering, and tend to point out the multi-faceted aspect of this field.