Abstract
The original ACM/IEEE Curriculum Guidelines for undergraduate degree programs in software engineering were issued in 2004. In 2010 the two professional bodies set up a task force to review these and see what changes might be needed, and following the report of this group, then set up another task force in 2012 to revise the guidelines. We describe the processes that the two task forces followed, and outline the main areas of change in the revised curriculum model that resulted from these. This is then followed by a review of the elements making up the model, to explain the roles that each of them can perform for those who may be developing a software engineering degree program. Finally, there are a few observations about both the processes and the outcome (the Curriculum Model).
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
