Understanding the Open-Source Software Development Process : a Case Study with CVSChecker

The open-source process model is emerging as a new lightweight paradigm for software development and has already produced several successful products. This process is fundamentally different from more traditional analysisand design-driven processes, which raises a set of interesting research questions: what activities are carried out in open-source projects and by whom? Are there typical or exceptional patterns? CVSChecker is a tool designed to analyze the performance of individual developers and the work-distribution patterns of teams based on historical source-code repository data. In this paper, we report on a case study conducted using CVSChecker to examine a small open-source project. We discuss the insights that the CVSChecker analysis produced regarding this project and compare them to results from previous case studies performed with senior student teams.

[1]  Eleni Stroulia,et al.  Using CVS Historical Information to Understand How Students Develop Software , 2004, MSR.

[2]  F. Ashcroft,et al.  VIII. References , 1955 .

[3]  Gail C. Murphy,et al.  Hipikat: recommending pertinent software development artifacts , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[4]  Tomasz Imielinski,et al.  Mining association rules between sets of items in large databases , 1993, SIGMOD Conference.

[5]  Richard C. Holt,et al.  Studying the evolution of software systems using evolutionary code extractors , 2004, Proceedings. 7th International Workshop on Principles of Software Evolution, 2004..

[6]  Andreas Zeller,et al.  How history justifies system architecture (or not) , 2003, Sixth International Workshop on Principles of Software Evolution, 2003. Proceedings..

[7]  Harald C. Gall,et al.  CVS release history data for detecting logical couplings , 2003, Sixth International Workshop on Principles of Software Evolution, 2003. Proceedings..

[8]  Mike F. Winter,et al.  Developing a group model for student software engineering teams , 2004 .

[9]  Martin Michlmayr,et al.  USENIX Association Proceedings of the FREENIX Track : 2004 , 2004 .

[10]  Gregorio Robles,et al.  Remote analysis and measurement of libre software systems by means of the CVSAnalY tool , 2004, ICSE 2004.

[11]  Eleni Stroulia,et al.  JRefleX: towards supporting small student software teams , 2003, eclipse '03.

[12]  Eleni Stroulia,et al.  Reverse engineering the process of small novice software teams , 2003, 10th Working Conference on Reverse Engineering, 2003. WCRE 2003. Proceedings..

[13]  Audris Mockus,et al.  Automating the Measurement of Open Source Projects , 2003 .

[14]  Eleni Stroulia,et al.  Design mentoring based on design evolution analysis , 2004, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[15]  J. Kidd.  Management Teams: Why They Succeed or Fail , 1982 .

[16]  J. Herbsleb,et al.  Two case studies of open source software development: Apache and Mozilla , 2002, TSEM.

[17]  Qiang Tu,et al.  Growth, evolution, and structural change in open source software , 2001, IWPSE '01.