|Title||Early detection of collaboration conflicts and risks|
|Publication Type||Journal Article|
|Year of Publication||2013|
|Authors||Brun Y, Holmes R, Ernst MD, Notkin D|
|Journal||IEEE Transactions on Software Engineering|
|Date or Month Published||October|
Conflicts among developers' inconsistent copies of a shared project arise in collaborative development and can slow progress and decrease quality. Identifying and resolving such conflicts early can help. Identifying situations which may lead to conflicts can prevent some conflicts altogether. By studying nine open-source systems totaling 3.4 million lines of code, we establish that conflicts are frequent, persistent, and appear not only as overlapping textual edits but also as subsequent build and test failures. Motivated by this finding, we develop a speculative analysis technique that uses previously unexploited information from version control operations to precisely diagnose important classes of conflicts. Then, we design and implement Crystal, a publicly available tool that helps developers identify, manage, and prevent conflicts. Crystal uses speculative analysis to make concrete advice unobtrusively available to developers.
|Downloads||http://homes.cs.washington.edu/~mernst/pubs/vc-conflicts-fse2011-slides.pdf ESEC/FSE 2011 slides (PDF) http://homes.cs.washington.edu/~mernst/pubs/vc-conflicts-fse2011-tooldem... tool demo paper (PDF) https://github.com/brunyuriy/crystalvc Crystal implementation http://homes.cs.washington.edu/~mernst/pubs/vc-conflicts-tse2013.pdf PDF|