ConE: A Concurrent Edit Detection Tool for Large ScaleSoftware Development

@article{Maddila2022ConEAC,
  title={ConE: A Concurrent Edit Detection Tool for Large ScaleSoftware Development},
  author={Chandra Shekhar Maddila and Nachiappan Nagappan and Christian Bird and Georgios Gousios and Arie van Deursen},
  journal={ArXiv},
  year={2022},
  volume={abs/2101.06542}
}
Modern, complex software systems are being continuously extended and adjusted. The developers responsible for this may come from different teams or organizations, and may be distributed over the world. This may make it difficult to keep track of what other developers are doing, which may result in multiple developers concurrently editing the same code areas. This, in turn, may lead to hard-to-merge changes or even merge conflicts, logical bugs that are difficult to detect, duplication of work… 
A Systematic Comparison of Two Refactoring-aware Merging Techniques
TLDR
RefMerge is presented, a Java re-implementation of the first technique, which is an operation-based refactoring-aware merging algorithm, and a qualitative analysis of the differences between the three merging algorithms is conducted to provide insights of the strengths and weaknesses of each tool.

References

SHOWING 1-10 OF 53 REFERENCES
Palantir: raising awareness among configuration management workspaces
  • A. Sarma, Z. Noroozi, A. Hoek
  • Computer Science, Engineering
    25th International Conference on Software Engineering, 2003. Proceedings.
  • 2003
TLDR
Palantir is a novel workspace awareness tool that complements existing configuration management systems by providing developers with insight into other workspaces by informing a developer of which other developers change which other artifacts, calculates a simple measure of severity of those changes, and graphically displays the information in a configurable and generally non-obtrusive manner.
Predicting Merge Conflicts in Collaborative Software Development
TLDR
A machine-learning based conflict predictor that filters out the merge scenarios that are not likely to have conflicts, i.e. safe merge scenarios, is designed, based on 9 light-weight Git feature sets, for predicting merge conflicts.
Awareness and Merge Conflicts in Distributed Software Development
TLDR
Analysis of data from 105 student developers constituting 12 development teams located in different countries finds that lack of awareness occurs more frequently than merge conflicts, and information about remote team members is missing roughly as often as information about colocated ones.
Leveraging Change Intents for Characterizing and Identifying Large-Review-Effort Changes
TLDR
This paper presents the first study to leverage change intent to characterize and identify Large-Review-Effort (LRE) changes regarding review effort---changes with large review effort, and proposes a feedback-driven and heuristics-based approach to obtain change intents.
Supporting Developers' Coordination in the IDE
Teamwork in software engineering is time-consuming and problematic. In this paper, we explore how to better support developers' collaboration in teamwork, focusing on the software implementation
Planning for Untangling: Predicting the Difficulty of Merge Conflicts
TLDR
The ability to predict the difficulty of a merge conflict and to identify the underlying factors for its difficulty can help tool builders improve their conflict detection tools to prioritize and warn developers of difficult conflicts.
Semantic Conflict
  • Retrieved from https://martinfowler.com/bliki/SemanticConflict.html
  • 2020
Semantic Conflict. https://martinfowler.com/bliki/SemanticConflict.html
  • 2020
Software Engineering at Google: Lessons Learned from Programming
  • 2020
Software Engineering at Google: Lessons Learned from Programming Over Time
  • 2020
...
1
2
3
4
5
...