Detection strategies: metrics-based rules for detecting design flaws
By Radu Marinescu. 20th IEEE International Conference on Software Maintenance, 2004. Proceedings., 2004
640 citations recorded by the source corpus.
Subfields: Artificial Intelligence, Information Systems, Software
View Paper: https://www.semanticscholar.org/paper/df6877edd1adfe419f3b2f5625749d0431767b55
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
- Michele Tufano
- Gabriele Bavota
- Rocco Oliveto
- Andrea De Lucia
- G. Antoniol
- Laurence Duchien
- Denys Poshyvanyk
- Foutse Khomh
In Information Systems
- Massimiliano Di Penta
- Denys Poshyvanyk
- Gabriele Bavota
- Michele Tufano
- Rocco Oliveto
- Andrea De Lucia
- Fabio Palomba
- Fausto Fasano
In Software
- Massimiliano Di Penta
- Gabriele Bavota
- Denys Poshyvanyk
- Michele Tufano
- Rocco Oliveto
- Andrea De Lucia
- Fabio Palomba
- Fausto Fasano
Citations in the corpus
- DECOR: A Method for the Specification and Detection of Code and Design Smells (2010, methodology): “Marinescu [17] presented a metric-based approach to detect code smells with detection strategies, implemented in the I P LASMA tool.”
- When and Why Your Code Starts to Smell Bad (and Whether the Smells Go Away) (2017, positive): “Marinescu [50] proposed a metric-based mechanism to capture deviations from good design principles and heuristics, called “detection strategies”.”
- On the diffuseness and the impact on maintainability of code smells: a large scale empirical investigation (2017, methodology): “Such tools exploitdifferenttypesofapproaches, including metrics-based detection (Lanza and Marinescu 2010; Moha et al. 2010; Marinescu 2004; Munro 2005), graph-based techniques (Tsantalis and Chatzigeorgiou 2009), mining of code changes (Palomba et al. 2015a), textual analysis of source code…”
- An Exploratory Study of the Impact of Code Smells on Software Change-proneness (2009, background): “They are usually revealed through particular metric values [4].”
- An Empirical Study of the Impact of Two Antipatterns, Blob and Spaghetti Code, on Program Comprehension (2011, methodology): “This questionnaire uses Likert scales for each of the mitigating variables and also include open questions about antipatterns, refactorings, and so on.”