The capability maturity model: guidelines for improving the software process
The capability maturity model: guidelines for improving the software process
The Rational Unified Process: an introduction
The Rational Unified Process: an introduction
Planning Extreme Programming
Some Experiences with Evolution and Process-Focused Projects
CSEET '03 Proceedings of the 16th Conference on Software Engineering Education and Training
The Software Development Laboratory: Incorporating Industrial Practice in an Academic Environment
CSEET '02 Proceedings of the 15th Conference on Software Engineering Education and Training
Software Engineering (7th Edition)
Software Engineering (7th Edition)
Managing Software Projects
Assessment and comparison of local and global SW engineering practices in a classroom setting
Proceedings of the 13th annual conference on Innovation and technology in computer science education
A metaobject protocol for CLforJava
Proceedings of the 2007 International Lisp Conference
| Hi-index | 0.00 |
Often Software Engineering courses approach educating undergraduates in good processes and practices by using a simulated product development environment, following all of the steps for product development in a single semester. Some also create multi-semester projects to improve the student experience. We are in the group using multi-semester projects, but our approach differs in that we have only a single semester of project work per team, focused on the core actions used in all processes from waterfalls to XP. We call this foundational actions. Using industrial tools, processes, and evaluation methods, the students develop and integrate components of a well-specified, but major product. Emphasis is placed on teamwork, communication, and ultimately, working production code created with the foundational actions. The approach has also spun off related independent study opportunities for advanced students and even non-CS majors.