The work-reflection-learning cycle - Department of Computer and ...
The work-reflection-learning cycle - Department of Computer and ... The work-reflection-learning cycle - Department of Computer and ...
The work-reflection-learning cycle in SE student projects: Use of collaboration tools 108
Power Through Brokering: Open Source Community Participation in Software Engineering Student Projects Birgit R. Krogstie Norwegian University of Science and Technology Sem Sælands vei 5-7, 7034 Trondheim, Norway birgitkr@idi.ntnu.no ABSTRACT Many software engineering projects use open source software tools or components. The project team’s active participation in the open source community may be necessary for the team to use the technology. Based on an in-depth field study of industry software engineering project students interacting with an open source community, we find that participation in the community may affect the team’s work and learning by strengthening the power of the broker between the team and the community. We outline pitfalls and benefits of having student teams acquire development-related knowledge from open source communities. The findings are relevant to the organization and supervision of software engineering student projects interacting with open source communities. Categories and Subject Descriptors K.3.2. [Computing Milieux]: Computer and Information Science Education General Terms: Human Factors Keywords: FLOSS, open source, software engineering, software engineering education, computer science education, communities of practice 1. INTRODUCTION Student SE industry projects, also known as customer-driven projects, are designed to provide SE students with realistic experience from software development work. The projects require that students relate to various stakeholders and engage in crosscommunity interaction [1]. Desired learning outcomes span both social and technical skills. The latter includes being flexible to customers’ technology requirements, which may be outside the team’s current experience and preference [2]. Through the pedagogical organization of SE project courses, student teams are provided with scaffolding for their learning process [3, 4], which might include guidance on the use of particular technology. Sometimes in the case of industry projects, neither course staff nor the customer is familiar with technology required in the project. The Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. ICSE’08, May 10-18, 2008, Leipzig, Germany. Copyright 2008 ACM 978-1-60558-079-1/08/05…$5.00. students have to demonstrate independence in coping with such situations. Requirements to learn and apply specific technologies may force SE teams to interact with user and/or developer communities through different degrees of community participation. For instance, involvement with open source software (OSS) communities may be needed. In what follows, we will talk about open source software communities for simplicity – tacitly assuming that similar considerations apply to free, libre and open source software (FLOSS) communities. OSS communities are a relatively new arena for information acquisition and knowledge building in SE student projects. Supervisors might be in doubt about what is going on and what advice to give in such cases, feeling that their possibility to impact on the project process is diminished. On part of the students, having to participate in a different community in accordance with the practices of that community may result in increased knowledge as well as self confidence. Involvement with an OSS community in the pursuit of knowledge may thus benefit the SE student team. However, with an increased numbers of stakeholders to relate to, the complexity of project work [5] increases, and coordination becomes more challenging. Also, the introduction of unfamiliar, third party OSS components introduces difficulties in terms of providing a system design early in the SD lifecycle [6]. This makes planning and estimation harder. Generally, there is very limited experience in student teams in respect of project management. Programmingrelated tasks, as will be argued, tend to be given priority, and programmers given strong influence on the project process. We believe that project managers as well as supervisors of SE student teams may benefit from insights on how OSS participation can affect the projects, in order to be prepared to take adequate measures. With this as our point of departure, in this paper we explore why and how the interaction between a group of students, involved in an SE industry project, and an OSS developer community evolves over time. We further address how such interaction might influence the project process, particularly in respect of the power structures in the team. The paper is based on an in-depth exploratory study of the work and learning of a student SE team during the spring term of 2007. We demonstrate how the interaction of the team with an OSS developer community can be paramount to the success of a SE project. In our case, we found that the OSS community readily responded to the students’ requests for assistance on the use of the OSS, and that issues of contribution from the team to the OSS community quickly arose. Also, we found that the team member responsible for 791 109
- Page 76 and 77: The work-reflection-learning cycle
- Page 78 and 79: The work-reflection-learning cycle
- Page 81 and 82: 7 Evaluation In this chapter, I eva
- Page 83 and 84: Evaluation adds to the CSCW literat
- Page 85 and 86: Evaluation 7.3 Evaluation of the re
- Page 87 and 88: Evaluation In the longitudinal stud
- Page 89 and 90: Evaluation According to the princip
- Page 91 and 92: Evaluation However, only some of th
- Page 93 and 94: Evaluation to design is problematic
- Page 95 and 96: 8 Conclusion and further work This
- Page 97 and 98: Conclusion and recommendations for
- Page 99 and 100: 9 References Abran, A., Moore, J. W
- Page 101 and 102: References Cobb, P. (1994). "Where
- Page 103 and 104: References Herbsleb, J. D., Mockus,
- Page 105 and 106: References Leont'ev, A. N. (1981).
- Page 107 and 108: References Stahl, G. (2002). "Build
- Page 109 and 110: Glossary B Boundary object - artifa
- Page 111 and 112: Glossary maintaining the system aft
- Page 113 and 114: Appendix A: Research papers P1 P2 P
- Page 115 and 116: Research paper P1 Title: Cross-Comm
- Page 117 and 118: Cross-Community Collaboration and L
- Page 119 and 120: the course staff may improve the co
- Page 121 and 122: 4: Case findings: students’ view
- Page 123 and 124: own account of why each artifact is
- Page 125: Research paper P2 Title: Power Thro
- Page 129 and 130: Due to the openness of OSS communit
- Page 131 and 132: 5.1.2 Second phase (February-May):
- Page 133 and 134: Getting from the second to the thir
- Page 135 and 136: 6.2.1 Benefits for SE student proje
- Page 137 and 138: Research paper P3 Title: Do’s and
- Page 139 and 140: DO‟S AND DON‟TS OF INSTANT MESS
- Page 141 and 142: a chat window is opened. As soon as
- Page 143 and 144: three examples in the form of excer
- Page 145 and 146: Example 2. Excerpt from an IM log s
- Page 147 and 148: Example 3. Excerpt from an IM log s
- Page 149 and 150: immediate feedback in the heated di
- Page 151 and 152: Acknowledgements Thanks to Monica D
- Page 153 and 154: Research paper P4 Title: The wiki a
- Page 155 and 156: The wiki as an integrative tool in
- Page 157 and 158: type of use can be seen as an examp
- Page 159 and 160: ecome integration, and we identifie
- Page 161 and 162: project. Typically, a clean-up was
- Page 163 and 164: 5.1 The wiki as a knowledge reposit
- Page 165 and 166: 6. Conclusion We have shown how pro
- Page 167 and 168: Research paper P5 Title: Using Proj
- Page 169 and 170: Proceedings of the 42nd Hawaii Inte
- Page 171 and 172: Proceedings of the 42nd Hawaii Inte
- Page 173 and 174: Proceedings of the 42nd Hawaii Inte
- Page 175 and 176: Proceedings of the 42nd Hawaii Inte
<strong>The</strong> <strong>work</strong>-<strong>reflection</strong>-<strong>learning</strong> <strong>cycle</strong> in SE student projects: Use <strong>of</strong> collaboration tools<br />
108