Finding refactorings via change metrics
By Serge Demeyer, Stéphane Ducasse, Oscar Nierstrasz. Conference on Object-Oriented Programming Systems, Languages, and Applications, 2000
345 citations recorded by the source corpus.
Subfields: Artificial Intelligence, Information Systems, Software
View Paper: https://www.semanticscholar.org/paper/f93098fd9a4c5382c361edccd0271b6e5c3c1433
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
- Nikolaos Tsantalis
- Matin Mansouri
- Danny Dig
- Eleni Stroulia
- Tom Mens
- Laleh Mousavi Eshkevari
- Davood Mazinanian
- Tom Tourwé
In Information Systems
- Nikolaos Tsantalis
- Danny Dig
- Matin Mansouri
- Eleni Stroulia
- Tom Mens
- Laleh Mousavi Eshkevari
- Davood Mazinanian
- Tom Tourwé
In Software
- Nikolaos Tsantalis
- Matin Mansouri
- Danny Dig
- Eleni Stroulia
- Tom Mens
- Laleh Mousavi Eshkevari
- Davood Mazinanian
- Tom Tourwé
Citations in the corpus
- A survey of software refactoring (2004, methodology): “Demeyer et al. propose using change metrics to detect refactorings between two successive software releases [60].”
- Accurate and Efficient Refactoring Detection in Commit History (2018, background): “A very active line of research focused on refactoring detection algorithms [4, 15, 18, 27, 31, 34–36, 46, 56, 62, 65, 74, 78] that compute a (likely) set of refactorings that developers applied on the source code.”
- UMLDiff: an algorithm for object-oriented design differencing (2005, background): “[2] define four heuristics based on the comparison of source-code metrics of two subsequent system snapshots to identify refactorings of three general categories.”