Iterative development and commercial tools in an undergraduate software engineering course
SIGCSE '97 Proceedings of the twenty-eighth SIGCSE technical symposium on Computer science education
ACE '04 Proceedings of the Sixth Australasian Conference on Computing Education - Volume 30
Tight spirals and industry clients: the modern SE education experience
ACE '05 Proceedings of the 7th Australasian conference on Computing education - Volume 42
Instructional design and assessment strategies for teaching global software development: a framework
Proceedings of the 28th international conference on Software engineering
Gathering Experience Knowledge from Iterative Software Development Processes
HICSS '08 Proceedings of the Proceedings of the 41st Annual Hawaii International Conference on System Sciences
Head first software development
Head first software development
Patterns and traceability in teaching software architecture
Proceedings of the 6th international symposium on Principles and practice of programming in Java
Software Engineering
SW development projects in academia
Proceedings of the 14th Western Canadian Conference on Computing Education
Dynamic group management in a software projects course
Journal of Computing Sciences in Colleges
Combining multiple pedagogies to boost learning and enthusiasm
Proceedings of the 16th annual joint conference on Innovation and technology in computer science education
| Hi-index | 0.00 |
In order to provide a realistic software development experience, the University of Mary Washington Computer Science Department offers a one semester project based software engineering course. We use realistic projects to help the students learn the entire software development process. However, during the period of 2004--2008 two issues became apparent. First, students were discouraged because of the failure to complete projects, even though they were relatively small in nature. Second, viable clients began decreasing since word had gotten out that students were unlikely to deliver working products at the end of the semester. In this paper we report on how we changed the course to use the iterative software process model and simultaneously changed our team management technique to require student teams to change membership over the semester. The original focus of this research was to investigate methods to increase the quantity of projects completed and increase student satisfaction at the end of the semester. This paper presents a combination of old and new research. The older portion of the research, creating dynamic teams, was implemented in the academic year of 2008--2009 and results were previously published. Combining dynamic teams and using iterative software development was used in academic year of 2009--2010, background and results are presented in this paper. Overall, both changes improved the client experience and added a touch of reality in the software engineering course.