This Article 
 Bibliographic References 
 Add to: 
Advancing Software Engineering Professional Education
July/August 2011 (vol. 28 no. 4)
pp. 58-63
Mark Ardis, Stevens Institute of Technology
Pierre Bourque, École de Technologie Supérieure
Thomas Hilburn, Embry-Riddle Aeronautical University
Kahina Lasfer, Stevens Institute of Technology
Scott Lucero, US Department of Defense
James McDonald, Monmouth University
Art Pyster, Stevens Institute of Technology
Mary Shaw, Carnegie Mellon University
The importance and complexity of software systems require software engineers who possess the appropriate skills, knowledge, and experience to develop, maintain, and acquire such systems. Graduate education is key in advancing professional software engineering. The "Graduate Software Engineering 2009 (GSwE2009): Curriculum Guidelines for Graduate Degree Programs in Software Engineering" is a new reference curriculum for master's programs. It features the GSwE2009 guiding principles, preparatory knowledge, student outcomes, curriculum architecture, and a core body of knowledge.

1. M. Ardis and G. Ford, SEI Report on Graduate Software Engineering Education, CMU/SEI 89-TR-21, Software Eng. Inst., Carnegie Mellon Univ., 1989.
2. Software Engineering: Report of a Conference Sponsored by the NATO Science Committee, P. Naur and B. Randell eds., NATO, 1968.
3. P. Freeman, A.I. Wasserman, and R.E. Fairley, "Essential Elements of Software Engineering Education," Proc. 2nd Int'l Conf. Software Eng. (ICSE 76), IEEE Press, 1976, pp. 116–122.
4. P. Freeman and A.I. Wasserman, "A Proposed Curriculum for Software Engineering Education," Proc. 3rd Int'l Conf. Software Eng. (ICSE 78), IEEE Press, 1978, pp. 56–62.
5. Guide to the Software Engineering Body of Knowledge (SWEBOK), A. Abran et al., eds, IEEE CS Press;
6. Software Engineering Code of Ethics and Professional Practice, v. 5.2, ACM/IEEE-CS Joint Task Force on Software Engineering Ethics and Professional Practices, ACM Press, 1999;
7. Criteria for Accrediting Engineering Programs (Effective for Evaluations during the 2010-2011 Accreditation Cycle), Accreditation Board for Engineering and Technology, 2009; www.abet.orgforms.shtml.
8. Software Engineering 2004: Curriculum Guidelines for Undergraduate Degree Programs in Software Engineering, ACM/IEEE CS Joint Task Force on Computing Curricula, ACM Press, 2004;
9. Graduate Software Eng. 2009 (GSwE2009): Curriculum Guidelines for Graduate Degree Programs in Software Eng., Integrated Software and Systems Eng. Curriculum Project, Stevens Inst. Technology, A. Pyster, ed., 2009;
10. Taxonomy of Educational Objectives: The Classification of Educational Goals, Handbook 1: Cognitive Domain, B.S. Bloom, ed., Longmans, 1956.
11. A. Pyster et al., "Master's Degrees in Software Engineering: An Analysis of 28 University Programs," IEEE Software, vol. 26, no. 5, 2009, pp. 94–101.
12. INCOSE Systems Engineering Handbook, v. 3.1, C. Haskins, ed., INCOSE-TP-2003-002-03.1, INCOSE, 2007.
13. Software Engineering for the 21st Century: A Basis for Rethinking the Curriculum, tech. report CMU-ISRI-05-108, M. Shaw, ed., Inst. for Software Research, Carnegie Mellon Univ., 2005.
14. S. Tockey, Return on Software: Maximizing the Return on Your Software Investment, Addison-Wesley, 2004.
15. Comparisons of GSwE2009 to Current Master's Programs in Software Engineering, D. Frailey, M. Ardis, and N. Hutchison eds., Integrated Software & Systems Engineering Curriculum Project, Stevens Inst., 2009.

Index Terms:
software engineering, computer and information science education, graduate programs, curriculum architecture, core body of knowledge, SWEBOK
Mark Ardis, Pierre Bourque, Thomas Hilburn, Kahina Lasfer, Scott Lucero, James McDonald, Art Pyster, Mary Shaw, "Advancing Software Engineering Professional Education," IEEE Software, vol. 28, no. 4, pp. 58-63, July-Aug. 2011, doi:10.1109/MS.2010.133
Usage of this product signifies your acceptance of the Terms of Use.