Evaluation of Semantic Interference Detection in Parallel Changes: an Exploratory Experiment

Shao, Danhua; Khurshid, Sarfraz; Perry, Dewayne E.

doi:10.1109/icsm.2007.4362620

Cited by 12 publications

(13 citation statements)

References 24 publications

(28 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In this study, the statistical analysis of correlation coefficients, significant levels, and t-tests shows a strong correlation between change size and change impact size. The matching between change impact and faults has already been successfully used in the previous study on change interference [24]. These consistencies are strong support for the internal validity.…”

Section: Validity Analysissupporting

confidence: 62%

“…Such a compromise can reduce the cost and improve the applicability in large programs. The benefits of our approach have been demonstrated in Shao et al [24].…”

Section: Related Workmentioning

confidence: 71%

“…If a piece of code added by one change was impacted by another change, the two changes interfere with each other. Our previous study [24] shows that such interferences between changes are important in predicting potential faults.…”

Section: Validity Analysismentioning

confidence: 98%

“…Local data-flow analysis was used in our previous work to detect semantic interference and predict faults [24]. However, we studied change impact and its relation to faults according to change intervals rather than change size as we have done in this study.…”

Section: Related Workmentioning

confidence: 99%

See 3 more Smart Citations

Semantic Impact and Faults in Source Code Changes: An Empirical Study

Shao

Khurshid

Perry

2009

2009 Australian Software Engineering Conference

Self Cite

View full text Add to dashboard Cite

show abstract

Section: Validity Analysissupporting

confidence: 62%

“…Such a compromise can reduce the cost and improve the applicability in large programs. The benefits of our approach have been demonstrated in Shao et al [24].…”

Section: Related Workmentioning

confidence: 71%

Section: Validity Analysismentioning

confidence: 98%

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Semantic Impact and Faults in Source Code Changes: An Empirical Study

Shao

Khurshid

Perry

2009

2009 Australian Software Engineering Conference

Self Cite

View full text Add to dashboard Cite

show abstract

“…Most closely-related is the use of data dependencies and program slicing to perform semantic interference detection between changes made in parallel [24].…”

Section: Collaborative Editingmentioning

confidence: 99%

Real-time collaborative coding in a web IDE

Goldman

Little

Miller

2011

Proceedings of the 24th Annual ACM Symposium on User Interface Software and Technology

100

View full text Add to dashboard Cite

This paper describes Collabode, a web-based Java integrated development environment designed to support close, synchronous collaboration between programmers. We examine the problem of collaborative coding in the face of program compilation errors introduced by other users which make collaboration more difficult, and describe an algorithm for errormediated integration of program code. Concurrent editors see the text of changes made by collaborators, but the errors reported in their view are based only on their own changes. Editors may run the program at any time, using only errorfree edits supplied so far, and ignoring incomplete or otherwise error-generating changes. We evaluate this algorithm and interface on recorded data from previous pilot experiments with Collabode, and via a user study with student and professional programmers. We conclude that it offers appreciable benefits over naive continuous synchronization without regard to errors and over manual version control.

show abstract

Build conflicts in the wild

Silva

Borba

Pires

2022

J Software Evolu Process

View full text Add to dashboard Cite

When collaborating, developers often create and change software artifacts without being fully aware of team members' work. While such independence is essential for increasing development productivity, it might also result in conflicts when integrating developers' contributions. To better understand the conflicts revealed by failures when building integrated code, we investigate their frequency and structure and adopted resolution patterns in 451 open-source Java projects. To detect such build conflicts, we select merge scenarios from git repositories, parse their Travis build logs, and check whether the build error messages are related to the merged changes. We find and classify 239 build conflicts and their resolution patterns. Most build conflicts are caused by missing declarations removed or renamed by one developer but referenced by another developer. Conflicts caused by renaming are often resolved by updating the missing reference, whereas removed declarations are often reintroduced. Most fix commits are authored by one of the merge scenario contributors. Based on our catalogue of conflict causes, awareness tools could alert developers about the risk of conflict situations. Program repair tools could benefit from our catalogue of resolution patterns to automatically fix conflicts; we illustrate that with a proof of concept implementation of a tool that fixes conflicts.

show abstract

Evaluation of Semantic Interference Detection in Parallel Changes: an Exploratory Experiment

Abstract: Abstract

Cited by 12 publications

References 24 publications

Semantic Impact and Faults in Source Code Changes: An Empirical Study

Semantic Impact and Faults in Source Code Changes: An Empirical Study

Real-time collaborative coding in a web IDE

Build conflicts in the wild

Contact Info

Product

Resources

About