• 主题
高级搜索  >
历史搜索 清空历史
首页> 外文会议>Annual Conference on Frontiers in Education >Comparison of Student Experiences with Plan-Driven and Agile Methodologies
【24h】

Comparison of Student Experiences with Plan-Driven and Agile Methodologies

机译：计划驱动和敏捷方法的学生经验比较

获取原文
页面导航
  • 摘要
  • 著录项
  • 相似文献
  • 相关主题

摘要

In Fall of 2004, we offered two software engineering courses: one in plan-driven methodologies and one in agile methodologies. In these courses, the students work on large projects in teams of 14 to 16 students using variants of Team Software Process (TSP) or Extreme Programming (XP). In order to compare the students' experiences with these methodologies, the team in the plan-driven course and one of the agile teams were given the same problem statement. Throughout the semester, we measured team cohesion and individuals' attachment to the project. To measure team cohesion, we modified the Group Environment Questionnaire that has been shown to accurately reflect team cohesion in sports teams. We also developed some of our own cohesion metrics and a measure of attachment to the project. While the GEQ showed no significant difference between the teams, our measures showed higher overall cohesion in XP, but higher sub-team cohesion in TSP. At the end of the semester, we also compared the functionality of the applications the teams developed and a variety of code metrics measuring the quality of their code and its design. While the team's developed approximately the same amount of functionality, in general, the XP team's code had better metrics. The TSP team required much more code to accomplish the same functionality because, although they had a strong design, their implementation did not leverage inheritance as the design expected.
机译：在2004年下来，我们提供了两个软件工程课程：一个在计划驱动的方法中，一个敏捷方法。在这些课程中，学生使用团队软件过程（TSP）或极端编程（XP）的变体为14至16名学生的大型项目。为了比较这些方法的学生的经验，计划驱动课程中的团队和其中一个敏捷团队的问题陈述了。在整个学期，我们测量了团队凝聚力和个人对项目的依恋。为了衡量团队凝聚力，我们修改了集团环境问卷，已被证明可以准确地反映运动队的团队凝聚力。我们还开发了我们自己的一些凝聚度量和项目附件的衡量标准。虽然GEQ与团队之间没有显着差异，但我们的措施在XP中显示出更高的整体凝聚力，但TSP中的亚队凝聚力更高。在学期结束时，我们还将对该团队开发的应用程序的功能和各种代码指标进行了比较了测量其代码的质量及其设计。虽然该团队发达了大约相同数量的功能，但总的来说，XP团队的代码具有更好的指标。 TSP团队需要更多的代码来完成相同的功能，因为它们具有强大的设计，但他们的实施没有利用遗产，因为设计预期。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱：kefu@zhangqiaokeyan.com

京公网安备：11010802029741号 ICP备案号：京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有

  • 客服微信

  • 服务号