240 likes | 363 Views
Using GSwE2009 in the Creation and Modification of Graduate Software Engineering Programs and Related Curricula. Mark Ardis, Stevens Institute of Technology, USA Shawn Bohner, Rose-Hulman Institute of Technology, USA Lucia Camilloni, Universidad de la República, Uruguay
E N D
Using GSwE2009 in the Creation and Modification of Graduate Software Engineering Programs and Related Curricula Mark Ardis, Stevens Institute of Technology, USA Shawn Bohner, Rose-Hulman Institute of Technology, USA Lucia Camilloni, Universidad de la República, Uruguay Diego Vallespir, Universidad de la República, Uruguay Sylvia Ilieva, University of Sofia, Bulgaria
Outline • Overview of GSwE2009 • Using GSwE2009 • MSwA project • Stevens Institute of Technology, USA • Rose-Hulman Institute of Technology, USA • University of Sofia, Bulgaria • UdelaR, Uruguay • Summary
GSwE2009 Overview • Created in 2007-2009 by an international team of authors • Studied several existing programs and curriculum resources • Adopted by ACM and IEEE Computer Society in 2009 http://www.gswe2009.org/
Body of knowledge - SWEBOK • Software Requirements Analysis • Software Design • Software Construction • Software Testing • Software Maintenance • Software Configuration Management • Software Engineering Management • Software Engineering Process • Software Engineering Tools and Methods • Software Quality
GSwE2009 Author Team • Rick Adcock, Cranfield University and INCOSE participant • Mark Ardis, Rochester Institute of Technology • Larry Bernstein, Stevens Institute of Technology • Barry Boehm, University of Southern California • Pierre Bourque, École de technologie supérieure and SWEBOK volunteer • John Bracket, Boston University • Murray Cantor, IBM • Lillian Cassel, Villanova and ACM participant • Robert Edson, ANSER • Richard Fairley, Colorado Technical University • Dennis Frailey, Raytheon & Southern Methodist University • Gary Hafen, Lockheed Martin and NDIA participant • Thomas Hilburn, Embry-Riddle Aeronautical University • Greg Hislop, Drexel University and IEEE Computer Society participant • Dave Klappholz, Stevens Institute of Technology • Philippe Kruchten, University of British Columbia • Phil Laplante, Pennsylvania State University, Great Valley • Scott Lucero, Department of Defense • Qiaoyun (Liz) Li, Wuhan University, China • James McDonald, Monmouth University • John McDermid, University of York, UK • Ernest McDuffie, National Coordination Office for NITRD • Bret Michael, Naval Postgraduate School • Ken Nidiffer, Software Engineering Institute • Art Pyster, Stevens Institute of Technology • Mary Shaw, Carnegie Mellon University • Robert Suritis, IBM • Richard Thayer, California State University at Sacramento • Barrie Thompson, Sunderland University, UK • Guilherme Travassos, Brazilian Computer Society, Brazil • Richard Turner, Stevens Institute of Technology • Joseph Urban, Texas Technical University • Ricardo Valerdi, MIT & INCOSE participant • David Weiss, Avaya • Mary Jane Willshire, Colorado Technical University
Expectations at Entry • Degree • undergraduate degree in computing or in an engineering or scientific field • SwE course • an introductory course in software engineering • Experience • at least two years of practical experience
Outcomes at Graduation • CBOK • master the Core Body of Knowledge • Domain • apply software engineering in at least one application domain • Depth • master one area at deeper level • Ethics • make ethical professional decisions • Systems Engineering • apply systems engineering principles and practices • Team • work effectively as part of a team • Reconciliation • reconcile conflicting project objectives • Perspective • communication and negotiation with stakeholders • Learning • apply new models, techniques, and technologies • Technology • analyze current software technology
Curriculum Architecture BSEE and BSCS grads Business grads Old degree,recent experience BSSE and BSCS grads Other degree,some experience BS + extensive experience Prep Material Baseline: Expected capability of CS and SE Grads Core Materials University-Specific Materials Elective Materials Capstone Experience
MSwA Project • Software Assurance Curriculum project • Master of Software Assurance (MSwA) similar to GSwE2009: • Entry expectations • Curriculum architecture
Stevens Institute of Technology • Founded 1870 • 5000 students
Stevens Institute of Technology • Existing MSwE • Participated in MSwE comparison study • Updated our coverage of some topics • Created 2 software assurance tracks within our MSwE program (developers/managers) • Created 2 certificates in software assurance (developers/managers)
University of Sofia • Founded 1888 • 14,000 students
University of Sofia • Existing MSwE • Updated core courses to better cover CBOK • Extended coverage of: • professional ethics • legal aspects of software engineering • research methodology • organizational behavior • teamwork skills • Currently working on • course materials • pedagogical style
Rose-Hulman Institute of Technology • Founded 1874 • 2000 students
Rose-Hulman Institute of Technology • New MSwE • GSwE2009 helpful in: • response to emerging needs of the software engineering community • lending external credibility • integration of systems engineering concepts • program educational objectives • Other advice also helpful: • marketing • acquiring needed resources • making effective use of adjunct faculty
UdelaR • Founded 1849 • 40,000 students
UdelaR • Created a new program in 2011 based on GSwE2009 • Entering students not required to have work experience, but most do • Students expected to master 9/10 of the GSwE2009 outcomes • Domain specialization is not included • Software professionals in Uruguay often change domain areas • Capstone experience is a thesis, but students work on teams in program • Currently working to include all the KAs from GSwE2009
Summary • GSwE2009 useful for • existing programs • new programs • other curriculum efforts http://www.gswe2009.org/