Vreda Pieterse
Lisa Thompson
ABSTRACT
We describe how we presented a year-long Software Engineering (SE) module. The first part of the module entailed a process we call rocking the boat. Our objective was to create an opportunity for our students to experience a complete software engineering project (from specification to delivery) within six weeks. During the second part students worked in self-selected teams on an industry-based SE project. Again they were required to undergo the complete SE lifecycle.
We firstly describe the design of our module. We then describe how we gathered and analysed information on how the students behaved in their teams as well as about what they experienced while participating in the module. Finally, we discuss our observations. We conclude with remarks about the potential success and possible improvement of our teaching strategies and future research directions.
- Aladwani, A. M. 2002. An integrated performance model of information systems projects. Journal of Management Information Systems 19, 1, 185--210. Google Scholar
Digital Library
- Bacon, D. R., Stewart, K. A., and Silver, W. S. 1999. Lessons from the best and worst student team experiences: How a teacher can make the difference. Journal of Management Education 23, 5, 467--488.Google ScholarCross Ref
- Belbin, R. M. 2010. Management Teams: Why They Succeed or Fail, 3rd ed. Elsevier, Burlington.Google ScholarCross Ref
- Csikszentmihalyi, M. 1991. Flow: The psychology of optimal experience. Harper Perennial, New York.Google Scholar
- Drake, R., Goldsmith, G., and Strachan, R. 2006. A novel approach to teaching teamwork. Teaching in Higher Education 11, 1, 33--46.Google ScholarCross Ref
- Gibbs, G. and Simpson, C. 2004. Conditions under which assessment supports students' learning. Learning and Teaching in Higher Education 1, 1, 1--31.Google Scholar
- Hedges, L. E. 2001. Is FFA the Teachable Moment? The Agricultural Education Magazine 74, 2 (September-October), 10--11.Google Scholar
- Hoegl, M. 2005. Smaller teams -- better teamwork: How to keep project teams small. Business Horizons 48, 3, 209--214.Google ScholarCross Ref
- Houser, M. L. and Frymier, A. B. 2009. The role of student characteristics and teacher behaviors in students learner empowerment. Communication Education 58, 1, 35--53.Google ScholarCross Ref
- Jefferies, P., Grodzinsky, F., and Griffin, J. 2003. Advantages and problems in using information communication technologies to support the teaching of a multi-institutional computer ethics course. Journal of Educational Media 28, 2, 191--202.Google ScholarCross Ref
- Kolb, D. A. 1984. Experiential learning: Experience as the source of learning and development. Prentice Hall, London.Google Scholar
- Koppenhaver, G. D. and Shrader, C. B. 2003. Structuring the classroom for performance: Cooperative learning with instructor-assigned teams. Decision Sciences Journal of Innovative Education 1, 1, 1--21.Google ScholarCross Ref
- Locke, E. A. and Latham, G. P. 2002. Building a practically useful theory of goal setting and task motivation: A 35-year odyssey. American Psychologist 57, 9 (September), 705--717.Google ScholarCross Ref
- Mello, J. 1993. Improving individual member accountability in small group settings. Journal of Management Education 17, 2, 253.Google ScholarCross Ref
- Parikh, A., McReelis, K., and Hodges, B. 2001. Student feedback in problem based learning: a survey of 103 final year students across five ontario medical schools. Medical Education 35, 7, 632--636.Google ScholarCross Ref
- Pausch, R. 2008. They just blew me away. In The Last Lecture. Hyperion, New York. Google ScholarDigital Library
- Pieterse, V. and Thompson, L. 2010. Academic alignment to reduce the presence of 'social loafers' and 'diligent isolates' in student teams. Teaching in Higher Education 15, 4, 355--367.Google ScholarCross Ref
- Pieterse, V., Thompson, L., Marshall, L., and Venter, D. M. 2012. Participation patterns in student teams. In Proceedings of the 43rd ACM technical symposium on Computer Science Education. SIGCSE '12. ACM, New York, NY, USA, 265--270. Google ScholarDigital Library
- Ramsden, P. 2003. Learning to teach in higher education, 2nd ed. SIAM, Philadelphia.Google Scholar
- Salas, E., Cooke, N. J., and Rosen, M. A. 2008. On teams, teamwork, and team performance: Discoveries and developments. Human Factors: The Journal of the Human Factors and Ergonomics Society 50, 3, 540--547.Google ScholarCross Ref
- Steenkamp, A. L. 2004. A standards-based approach to team-based student projects in an information technology curriculum. In Proceedings of the International Academy for Information Management (IAIM). 17th International Conference on Informatics Education Research (ICIER). 54--62.Google Scholar
Index Terms
- An intensive software engineering learning experience
Recommendations
Success with the project-intensive model for an undergraduate software engineering course
There is a tremendously increasing need for software in all areas of society (the software crisis) and hence a need for increased numbers of software engineers as well as increased productivity of the current software engineers [1]. Improving the ...
Towards an effective software engineering course project
ICSE '05: Proceedings of the 27th international conference on Software engineeringSoftware engineering instructors face many challenges. Among these challenges is the course project. Instructors are required to train their students on the professional skills to be ready for the real world business, which requires the students to work ...
Success with the project-intensive model for an undergraduate software engineering course
SIGCSE '89: Proceedings of the twentieth SIGCSE technical symposium on Computer science educationThere is a tremendously increasing need for software in all areas of society (the software crisis) and hence a need for increased numbers of software engineers as well as increased productivity of the current software engineers [1]. Improving the ...
Comments