Master's Degrees in Software Engineering: An Analysis of 28 University Programs

  • Authors:
  • Arthur Pyster;Richard Turner;Devanandham Henry;Kahina Lasfer;Larry Bernstein

  • Affiliations:
  • Stevens Institute of Technology;Stevens Institute of Technology;Stevens Institute of Technology;Stevens Institute of Technology;Stevens Institute of Technology

  • Venue:
  • IEEE Software
  • Year:
  • 2009

Quantified Score

Hi-index 0.00

Visualization

Abstract

The Software Engineering Institute published the last reference curriculum for a master's in software engineering in 1991. In 2007, a coalition from academia, industry, and government began creating a new reference curriculum. An early step was to establish a baseline of graduate education by surveying 28 master's programs in software engineering. The survey was largely limited to US schools. Key findings showed that the universities viewed software engineering largely as a specialization of computer science, that faculty size is generally small with few dedicated professors, and that new master's programs continue to start despite the decrease in computer science majors over the past few years. We used the IEEE Computer Society's Software Engineering Body of Knowledge (SWEBOK) to structure our analysis of the 28 curricula, focusing primarily on courses and topics required or semirequired of all students. (A course is semirequired if there is at least a 50 percent chance a student must take it.) Major findings show wide variation in the depth and breadth of SWEBOK coverage in required and semirequired courses, less than 40 percent of all programs requiring an introductory course on software engineering, and many universities having required and semirequired courses that are peripheral to SWEBOK.