Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
How the Evolution of Emerging
Collaborations Relates to
Code Changes:
An Empirical Study
Sebastiano Gerardo Massimiliano R...
Outline
Analysis of Teams Evolution:
Teams identification from
Emergent Collaborations
Conclusion and Future Work
Context ...
Emergenging Teams in Open
Source Project
Emergenging Teams in Open
Source Project
Team
1
Team
2
Team
n
...
Emergenging Teams in Open
Source Project
Team
1
Team
2
Team
n
...
New Features
Bugs fixing
...................
..............
Previous Work...
Hong Et al. - ICSM 2011
Previous Work...
Bird Et al. - FSE 2008
Analysis of the evolution
of Teams: why?
Analysis of the evolution
of Teams: why?
1) To better understand the Reasons
Behind the teams reorganization
(split/merge ...
Analysis of the evolution
of Teams: why?
1) To better understand the Reasons
Behind the teams reorganization
(split/merge ...
Analysis of the evolution
of Teams: how?
Teams Identification from Emergent Collaborations
Analysis of the evolution
of Teams: how?
By use FUZZY
CLUSTER ALGORITHMS
Teams Identification from Emergent Collaborations
Analysis of the evolution
of Teams: how?
R1
By use FUZZY
CLUSTER ALGORITHMS
R2
Analysis of the evolution
of Teams: how?
TEAMS SPLIT
TEAMS MERGE
R1
By use FUZZY
CLUSTER ALGORITHMS
R2
Analysis of the evolution
of Teams: how?
R1
R2
By use FUZZY
CLUSTER ALGORITHMS
Analysis of the evolution
of Teams: how?
R1
R2
By use FUZZY
CLUSTER ALGORITHMS
Sub-system one Sub-system twoSub-systems two
Sub-System where developers working on....
R1
R2
By use FUZZY
CLUSTER ALGORITHMS
Sub-system one Sub-system twoSub-systems two
Sub-System where developers working on....
Apache HTTP Eclipse JDT Netbeans Samba
Period
considered
09/1998-03/2012
01/2002-
12/2011
01/2001-
08/2012
01/2000-09/2011...
Research Questions
RQ1: How do emerging collaborations change across
software releases?
RQ2: How does the evolution of eme...
RQ1: How do emerging collaborations change across
software releases?
Teams Split in a new release :
- In 15%-35% of the
cases
RQ1: How do emerging collaborations change across
software releas...
Teams Merge in a new release :
- in 20%-35% of the
cases
Teams Split in a new release :
- In 15%-35% of the
cases
RQ1: How...
Teams Merge in a new release :
- in 20%-35% of the
cases
Teams Split in a new release :
- In 15%-35% of the
cases
RQ1: How...
TEAMS
SPLIT
TEAMS
MERGED
RQ2 : How does the evolution of emerging collaboration relate to the cohesiveness
of files change...
TEAMS
SPLIT
TEAMS
MERGED
RQ2 : How does the evolution of emerging collaboration relate to the cohesiveness
of files change...
TEAMS
SPLIT
TEAMS
MERGED
RQ2 : How does the evolution of emerging collaboration relate to the cohesiveness
of files change...
TEAMS
SPLIT
TEAMS
MERGED
RQ2 : How does the evolution of emerging collaboration relate to the cohesiveness
of files change...
Future Work
How the Evolution of Emerging Collaborations Relates to Code Changes: An Empirical Study - ICPC 2014
Upcoming SlideShare
Loading in …5
×

How the Evolution of Emerging Collaborations Relates to Code Changes: An Empirical Study - ICPC 2014

531 views

Published on

Developers contributing to open source projects spontaneously group into "emerging" teams, re
ected by messages ex-changed over mailing lists, issue trackers and other communication means. Previous studies suggested that such teams somewhat mirror the software modularity. This paper empirically investigates how, when a project evolves, emerging teams re-organize themselves|e.g., by splitting or merging. We relate the evolution of teams to the les they change, to investigate whether teams split to work on cohesive groups
of fi les. Results of this study conducted on the evolution
history of four open source projects, namely Apache HTTPD, Eclipse JDT, Netbeans, and Samba provide indications of what happens in the project when teams reorganize. Specifically, we found that emerging team splits imply working on more cohesive groups of les and emerging team merges imply working on groups of les that are cohesive from structural perspective. Such indications serve to better understand the evolution of software projects. More important, the observation of how emerging teams change can serve to suggest software remodularization actions.

  • Be the first to comment

  • Be the first to like this

How the Evolution of Emerging Collaborations Relates to Code Changes: An Empirical Study - ICPC 2014

  1. 1. How the Evolution of Emerging Collaborations Relates to Code Changes: An Empirical Study Sebastiano Gerardo Massimiliano Rocco Panichella Canfora Di Penta Oliveto
  2. 2. Outline Analysis of Teams Evolution: Teams identification from Emergent Collaborations Conclusion and Future Work Context and Motivation: Open Source Projects
  3. 3. Emergenging Teams in Open Source Project
  4. 4. Emergenging Teams in Open Source Project Team 1 Team 2 Team n ...
  5. 5. Emergenging Teams in Open Source Project Team 1 Team 2 Team n ... New Features Bugs fixing ................... ................... ...................
  6. 6. Previous Work... Hong Et al. - ICSM 2011
  7. 7. Previous Work... Bird Et al. - FSE 2008
  8. 8. Analysis of the evolution of Teams: why?
  9. 9. Analysis of the evolution of Teams: why? 1) To better understand the Reasons Behind the teams reorganization (split/merge of developers teams)
  10. 10. Analysis of the evolution of Teams: why? 1) To better understand the Reasons Behind the teams reorganization (split/merge of developers teams) 2) Investigate whether emerging teams evolve with the aim of working on more cohesive groups of files
  11. 11. Analysis of the evolution of Teams: how?
  12. 12. Teams Identification from Emergent Collaborations Analysis of the evolution of Teams: how?
  13. 13. By use FUZZY CLUSTER ALGORITHMS Teams Identification from Emergent Collaborations Analysis of the evolution of Teams: how?
  14. 14. R1 By use FUZZY CLUSTER ALGORITHMS R2 Analysis of the evolution of Teams: how?
  15. 15. TEAMS SPLIT TEAMS MERGE R1 By use FUZZY CLUSTER ALGORITHMS R2 Analysis of the evolution of Teams: how?
  16. 16. R1 R2 By use FUZZY CLUSTER ALGORITHMS Analysis of the evolution of Teams: how?
  17. 17. R1 R2 By use FUZZY CLUSTER ALGORITHMS Sub-system one Sub-system twoSub-systems two Sub-System where developers working on.... Analysis of the evolution of Teams: how?
  18. 18. R1 R2 By use FUZZY CLUSTER ALGORITHMS Sub-system one Sub-system twoSub-systems two Sub-System where developers working on.... Mancoridis et al. Modul. Quality Poshyvanyk et al. CCBC Structure Persprective Conceptual Persprective Analysis of the evolution of Teams: how?
  19. 19. Apache HTTP Eclipse JDT Netbeans Samba Period considered 09/1998-03/2012 01/2002- 12/2011 01/2001- 08/2012 01/2000-09/2011 Releases Considered 2.0 2.2.0 2.2.4 2.2.12 2.4.1 3.0 3.2 3.4 3.6 4.2 3.4 3.6 5.5 6.9 7.2 2.3 3.0.20 3.0.25 3.5.0 4.0 Systems characteristics: Period of time and Releases Considered Case study • Goal: analyze data from mailing lists/issue trackers and versioning systems • Purpose: observe the reorganization of the teams between releases • MQ/CCBC: better understand (i) the reason behind the reorganization of teams
  20. 20. Research Questions RQ1: How do emerging collaborations change across software releases? RQ2: How does the evolution of emerging collaboration relate to the cohesiveness of files changed by emerging teams?
  21. 21. RQ1: How do emerging collaborations change across software releases?
  22. 22. Teams Split in a new release : - In 15%-35% of the cases RQ1: How do emerging collaborations change across software releases?
  23. 23. Teams Merge in a new release : - in 20%-35% of the cases Teams Split in a new release : - In 15%-35% of the cases RQ1: How do emerging collaborations change across software releases?
  24. 24. Teams Merge in a new release : - in 20%-35% of the cases Teams Split in a new release : - In 15%-35% of the cases RQ1: How do emerging collaborations change across software releases? Teams desappeared: 22%-45% Teams Survived: 50%-70%
  25. 25. TEAMS SPLIT TEAMS MERGED RQ2 : How does the evolution of emerging collaboration relate to the cohesiveness of files changed by emerging teams?
  26. 26. TEAMS SPLIT TEAMS MERGED RQ2 : How does the evolution of emerging collaboration relate to the cohesiveness of files changed by emerging teams? MQCCBC
  27. 27. TEAMS SPLIT TEAMS MERGED RQ2 : How does the evolution of emerging collaboration relate to the cohesiveness of files changed by emerging teams? MQCCBC MQCCBC
  28. 28. TEAMS SPLIT TEAMS MERGED RQ2 : How does the evolution of emerging collaboration relate to the cohesiveness of files changed by emerging teams? MQCCBC MQCCBC
  29. 29. Future Work

×