The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.05 - September/October (2009 vol.26)
pp: 94-101
Arthur Pyster , Stevens Institute of Technology
Richard Turner , Stevens Institute of Technology
Devanandham Henry , Stevens Institute of Technology
Kahina Lasfer , Stevens Institute of Technology
Larry Bernstein , Stevens Institute of Technology
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.
INDEX TERMS
software engineering, curriculum, Software Engineering Body of Knowledge, SWEBOK, computer science education
CITATION
Arthur Pyster, Richard Turner, Devanandham Henry, Kahina Lasfer, Larry Bernstein, "Master's Degrees in Software Engineering: An Analysis of 28 University Programs", IEEE Software, vol.26, no. 5, pp. 94-101, September/October 2009, doi:10.1109/MS.2009.133
REFERENCES
1. G. Ford, 1991 SEI Report on Graduate Software Engineering Education, tech. report CMU/SEI-91-TR-002, Software Eng. Inst., Carnegie Mellon Univ., 1991.
2. N. Meade, "Software Engineering Education: How Far We've Come and How Far We Have to Go," Proc. 21st Conf. Software Eng. Education and Training, IEEE CS Press, 2008, pp. 18–22.
3. B. Boehm, "A View of 20th and 21st Century Software Engineering," Proc. 28th Int'l Conf. Software Eng. (ICSE 06), ACM Press, 2006, pp. 12–29.
4. T.C. Lethbridge et al., "SE2004: Recommendations for Undergraduate Software Engineering Curricula," IEEE Software, vol. 23, no. 6, 2006, pp. 19–25.
5. A. Abran et al., Guide to the Software Engineering Body of Knowledge (SWEBOK), IEEE CS Press, 2004.
6. S. Zweben, "2006–2007 Taulbee Survey: Ph.D Production Exceeds 1,700; Undergraduate Enrollment Trends Still Unclear," Computing Research News, May 2008, pp. 6–17.
7. ISO 15288:2008, Systems and Software Engineering—System Life Cycle Processes, Int'l Organization for Standardization, 2008.
8. M. Maier, "System and Software Architecture Reconciliation," System Eng., vol. 9, no. 2, 2006, pp. 146–159.
24 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool