iSSEc
The iSSEc project was started in Spring 2007 to develop curricula at the graduate level that combine elements of software and systems engineering. GSwE2009 is a model curriculum that reflects understanding in how to build software; how software engineering depends on systems engineering; and how software engineering education is influenced by specific technological domains, such as telecommunications and defense systems. The document was developed through collaboration of faculty from over 30 universities worldwide as well as practitioners from industry and government. (Click here to learn more about document development).
The next stage in the iSSEc project is the development of a body of knowledge and a model curriculum for systems engineering that will incorporate lessons learned from software development and its impact on systems. This effort is scheduled to begin in late 2009. The third iSSEc effort will be the development of a fully-integrated curriculum for software system engineering.
Why focus on software engineering?
Worldwide, most of the value in new products and systems is delivered through software. Much of the complexity of those products and systems resides in and is addressed by software. Most of the "surprises" that occur after product shipment and system deployment can be traced back to incorrect software implementation. Software is the underlying technology required to advance mobile phones, automobiles, and aircraft. The ability of any large company or government agency to manage its projects and organization depends heavily on sophisticated software that supports its business and technical processes, ranging from logistics systems to manufacturing or customer relationship management systems. Software is everywhere. Yet, reports from the Software Engineering Institute and others have painted the same story for years: creating and evolving large-scale software on schedule, on budget, with expected functionality, is uncommon.
Software engineering (SwE) is the acknowledged discipline by which large-scale and complex software is developed. Many universities teach software engineering at the undergraduate level. In 2004, the IEEE Computer Society and the ACM supported the development of curriculum guidelines for undergraduate degree programs in software engineering; more than 100 colleges and universities participated in this effort.
However, graduate programs have not been addressed since 1989, when the Software Engineering institute (SEI) published a model curriculum for graduate softare engineering education. Given the changes in technology and development methods since 1989, and update is sorely neded.
Document Development
In July 2007, the iSSEc established the early start team (EST) to begin exploration of the requirements for a software engineering reference curriculum, then called GSwERC. (Click here for a list of the EST members). The EST began development of the curriculum, including scoping of the project, developing comparisons with current programs, and conducting a survey of current programs. In April 2008, the EST published version 0.25 of GSwERC for international review. Upon this review, the EST received [number] comments from [number] reviewers, most of whom were from North America. These comments were used to improve the document and help drive further development. [Primary changes based on .25 review] (Click here for the adjudication matrix of comments received for the version 0.25 review)
In July 2008, the EST evolved into the Curriculum Author Team (CAT). (Click here for the list of CAT members). The CAT expanded to include additional universities, industry representatives, and additional representation from outside the U.S. The CAT continued development of the document, expanding it to include additional comparisons. As CAT members began implementing parts of GSwERC in their own programs, the CAT also began including guidance for implementation in the document.
Version 0.5 was released October 31, 2009 for international review. (Click here for the adjudication matrix of comments received for the version 0.5 review) The CAT collected over 800 comments from over 100 reviewers. Approximately 40% reviewers for version 0.5 were from outside North America. Based on this review, the CAT decided to divide the content of GSwERC into three separate but inter-related documents. These include guidelines and recommendations for graduate software engineering; comparisons to current projects; and guidance for implementation.
The CAT has sought endorsement of the curriculum by relevant professional societies. The NDIA SE Division agreed to endorse the project in 2007, and INCOSE in 2008. Based on feedback from the IEEE CS and the ACM, which are both reviewing proposals for sponsorship of the guidance document, the name of the document was changed from GSwERC to Graduate Software Engineering 2009 (GSwE2009). As of the publication of the guidelines document, the IEEE CS and the ACM are still considering sponsoring GSwE2009.