In a field as rapidly growing as software engineering, the education problem splits into two major parts-university education and industrial education. (Some of which is given at university locations, as short courses, but considered industrial education here.) Both parts draw on the same underlying disciplines and methodologies. But the people involved-both teachers and students-have different objectives and characteristics. At the university level students are young, inexperienced, and relatively homogeneous in background and abilities. At the industrial level, students are older, more experienced, and vary considerably in background and abilities. In this paper, we discuss the underlying commonalities and the overlaid differences of university and industrial education in software engineering. The commonalities in discipline and methodologies involve the study and understanding of the Software Process, as discussed in Section II of this special issue, and of the "Tools" and "Know How" discussed in Section III. The differences are due to the characteristics and objectives of students, and show up on curricula content and structure and in course definition.
[1]
Richard H. Austing,et al.
Curriculum '78: recommendations for the undergraduate program in computer science— a report of the ACM curriculum committee on computer science
,
1979,
CACM.
[2]
C. A. R. Hoare,et al.
Monitors: an operating system structuring concept
,
1974,
CACM.
[3]
Edsger W. Dijkstra,et al.
The structure of the “THE”-multiprogramming system
,
1968,
CACM.
[4]
Richard A. Kemmerer,et al.
Specification and verification of the UCLA Unix security kernel
,
1979,
CACM.
[5]
Niklaus Wirth,et al.
Toward a discipline of real-time programming
,
1977,
CACM.
[6]
F. T. Baker,et al.
Chief Programmer Team Management of Production Programming
,
1972,
IBM Syst. J..