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 ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<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 />
be seen as boundary objects. This perspective helps identify challenges <strong>and</strong> <strong>learning</strong><br />
potential associated with student teams‟ interaction with the different stakeholders, <strong>and</strong><br />
what support might be adequate to help the student teams in this interaction.<br />
<strong>The</strong> paper ends with the recommendation that in the organization <strong>of</strong> the course <strong>and</strong><br />
supervision <strong>of</strong> the projects one should put explicit focus on the role <strong>and</strong> purpose <strong>of</strong><br />
project artifacts serving a role as boundary objects. Consciousness <strong>of</strong> the purpose <strong>of</strong><br />
such artifacts helps shed light on stakeholders‟ different objectives for project<br />
participation <strong>and</strong> the potential role <strong>of</strong> the artifacts in supporting these objectives – two<br />
issues that are, as shown in P1, frequently unclear to the students. As an example,<br />
students typically regard some project artifacts as „school‟ deliverables <strong>and</strong> some as<br />
„real‟ project artifacts relevant to the customer. Documentation <strong>of</strong> the product, for<br />
example, conceptual models describing possible use scenarios, are frequently taken by<br />
the students as belonging to the first category, but may in fact be useful when the<br />
customer wants to continue developing the product. An open discussion between team<br />
<strong>and</strong> customer about such issues may benefit collaboration <strong>and</strong> the project result. <strong>The</strong><br />
current use <strong>of</strong> a number <strong>of</strong> different collaboration tools in the projects point to a<br />
potential for providing shared access among the collaborating stakeholders to boundary<br />
objects <strong>and</strong> descriptions <strong>of</strong> the role <strong>and</strong> design <strong>of</strong> these objects<br />
It is further proposed in P1 that if the students are fully aware <strong>of</strong> the purpose <strong>and</strong> role <strong>of</strong><br />
an artifact in collaboration, they may be allowed to determine for themselves (in<br />
collaboration with the other stakeholder) what is the appropriate form <strong>and</strong> content <strong>of</strong> the<br />
artefact. This contrasts with the m<strong>and</strong>atory use <strong>of</strong> pre-specified templates for, for<br />
example, product requirements or status reports.<br />
5.2 P2: Power through brokering. OSS participation in SE<br />
projects<br />
Author: Krogstie, Birgit<br />
Published in: Proceedings <strong>of</strong> the International Conference on S<strong>of</strong>tware Engineering<br />
(ICSE) 2008<br />
Many s<strong>of</strong>tware engineering projects use open source s<strong>of</strong>tware tools or components. <strong>The</strong> project team’s<br />
active participation in the open source community may be necessary for the team to use the technology.<br />
Based on an in-depth field study <strong>of</strong> industry s<strong>of</strong>tware engineering project students interacting with an<br />
open source community, we find that participation in the community may affect the team’s <strong>work</strong> <strong>and</strong><br />
<strong>learning</strong> by strengthening the power <strong>of</strong> the broker between the team <strong>and</strong> the community. We outline<br />
pitfalls <strong>and</strong> benefits <strong>of</strong> having student teams acquire development-related knowledge from open source<br />
communities. <strong>The</strong> findings are relevant to the organization <strong>and</strong> supervision <strong>of</strong> s<strong>of</strong>tware engineering<br />
student projects interacting with open source communities.<br />
38