Metrics based refactoring

By Frank Simon, Frank Steinbrückner, Claus Lewerentz. Proceedings Fifth European Conference on Software Maintenance and Reengineering, 2001

400 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

An Exploratory Study of the Impact of Code Smells on Software Change-proneness (2009, methodology): “Rules may also be defined using fuzzy logic and executed by means of a rule-inference engine [1] or using visualisation techniques [9, 27].”
Identification of Move Method Refactoring Opportunities (2009, background): “Maintain the consistency between the refactored code and other software artifacts (such as documentation, design documents, tests, etc.).”
When and Why Your Code Starts to Smell Bad (and Whether the Smells Go Away) (2017, neutral): “[71] provided a metric-based visualization tool able to discover design defects representing refactoring opportunities.”
DECOR: A Method for the Specification and Detection of Code and Design Smells (2010, methodology): “Some approaches for complex software analysis use visualization techniques [20], [21].”
A survey of software refactoring (2004, methodology): “Simon et al. use object-oriented metrics to identify bad smells and propose adequate refactorings [20].”