Java quality assurance by detecting code smells
By Eva Van Emden, Leon Moonen. Ninth Working Conference on Reverse Engineering, 2002. Proceedings., 2002
456 citations recorded by the source corpus.
Subfields: Information Systems, Software, Signal Processing
View Paper: https://www.semanticscholar.org/paper/8edac7fd14549e11d1b98438e17d1567c3d764f6
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Information Systems
- Massimiliano Di Penta
- Yann-Gaël Guéhéneuc
- Foutse Khomh
- Laurence Duchien
- Naouel Moha
- Anne-Françoise Le Meur
- Pieter Van Gorp
- Tom Mens
In Software
- Massimiliano Di Penta
- Yann-Gaël Guéhéneuc
- Foutse Khomh
- Laurence Duchien
- Naouel Moha
- Anne-Françoise Le Meur
- Pieter Van Gorp
- Tom Mens
In Signal Processing
- Massimiliano Di Penta
- Foutse Khomh
- Pieter Van Gorp
- Yann-Gaël Guéhéneuc
- Tom Mens
- Radu Marinescu
- Tom Tourwé
Citations in the corpus
- A Taxonomy of Model Transformation (2006, methodology): “For example, a refactoring tool might not only apply refactoring transformations, but also suggest in which context a particular refactoring should be applied [18,19].”
- Detection strategies: metrics-based rules for detecting design flaws (2004, background): “Recently, an automatic approach of ”code smells” detection was proposed in [29], but it is quite much focused on implementation issues (e.”
- When and Why Your Code Starts to Smell Bad (and Whether the Smells Go Away) (2017, unknown): “Travassos et al. [78] define the ”reading techniques”, a mechanism suggesting manual inspection rules to identify defects in source code. van Emden and Moonen [83] presented jCOSMO, a code smell browser that visualizes the detected smells in the source code.”
- A survey of software refactoring (2004, methodology): “Van Emden and Moonen detect bad smells in Java code and visualize them using the Rigi software visualization tool [18].”
- DECOR: A Method for the Specification and Detection of Code and Design Smells (2010, background): “Relatedwork ondesign pattern identification (e.g., [12]) is beyond the scope of this paper.”
- An Exploratory Study of the Impact of Code Smells on Software Change-proneness (2009, methodology): “For independent samples (to be used in the context of unpaired analyses, as in our case), it is defined as the difference between the means (M1 andM2), divided by the pooled standard deviation (σ = √ (σ21 + σ 2 2)/2) of both groups:d = (M1 − M2)/σ.”