Fast Algorithms for Mining Association Rules in Large Databases
VLDB '94 Proceedings of the 20th International Conference on Very Large Data Bases
CVSSearch: Searching through Source Code using CVS Comments
ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
Detection of Logical Coupling Based on Product Release History
ICSM '98 Proceedings of the International Conference on Software Maintenance
How History Justifies System Architecture (or Not)
IWPSE '03 Proceedings of the 6th International Workshop on Principles of Software Evolution
CVS Release History Data for Detecting Logical Couplings
IWPSE '03 Proceedings of the 6th International Workshop on Principles of Software Evolution
Identification of Software Instabilities
WCRE '03 Proceedings of the 10th Working Conference on Reverse Engineering
Predicting Source Code Changes by Mining Change History
IEEE Transactions on Software Engineering
Using Origin Analysis to Detect Merging and Splitting of Source Code Entities
IEEE Transactions on Software Engineering
Visual data mining in software archives
SoftVis '05 Proceedings of the 2005 ACM symposium on Software visualization
Clustering Software Artifacts Based on Frequent Common Changes
IWPC '05 Proceedings of the 13th International Workshop on Program Comprehension
Mining Version Histories to Guide Software Changes
IEEE Transactions on Software Engineering
Toward Understanding the Rhetoric of Small Source Code Changes
IEEE Transactions on Software Engineering
MSR '05 Proceedings of the 2005 international workshop on Mining software repositories
When Functions Change Their Names: Automatic Detection of Origin Relationships
WCRE '05 Proceedings of the 12th Working Conference on Reverse Engineering
Fractal Figures: Visualizing Development Effort for CVS Entities
VISSOFT '05 Proceedings of the 3rd IEEE International Workshop on Visualizing Software for Understanding and Analysis
Identifying Changed Source Code Lines from Version Repositories
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Prioritizing Warning Categories by Analyzing Software History
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Branching and merging in the repository
Proceedings of the 2008 international working conference on Mining software repositories
SZZ revisited: verifying when changes induce fixes
DEFECTS '08 Proceedings of the 2008 workshop on Defects in large software systems
BUGINNINGS: identifying the origins of a bug
Proceedings of the 3rd India software engineering conference
Timesheet assistant: mining and reporting developer effort
Proceedings of the IEEE/ACM international conference on Automated software engineering
A study of language usage evolution in open source software
Proceedings of the 8th Working Conference on Mining Software Repositories
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
WhoseFault: automatic developer-to-fault assignment through fault localization
Proceedings of the 34th International Conference on Software Engineering
The storyteller version control system: tackling version control, code comments, and team learning
Proceedings of the 3rd annual conference on Systems, programming, and applications: software for humanity
History slicing: assisting code-evolution tasks
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
Are Developers Fixing Their Own Bugs?: Tracing Bug-Fixing and Bug-Seeding Committers
International Journal of Open Source Software and Processes
| Hi-index | 0.00 |
Files, classes, or methods have frequently been investigated in recent research on co-change. In this paper, we present a first study at the level of lines. To identify line changes across several versions, we define the annotation graph which captures how lines evolve over time. The annotation graph provides more fine-grained software evolution information such as life cycles of each line and related changes: "Whenever a developer changed line 1 of version.txt she also changed line 25 of Library.java."