Seven habits of a highly effective smell detector
Authors:
Open Access
- 9 November 2008
- conference paper
- Published by Association for Computing Machinery (ACM)
- p. 36-40
Abstract
The process of refactoring code---changing its structure while preserving its meaning---has been identified as an important way of maintaining code quality over time. However, it is sometimes difficult for progammers to identify which pieces of code are in need of refactoring. "Smell detectors" are designed to help programmers in this task, but most smell detectors do not mesh well with "floss refactoring," the recommended tactic in which refactoring and programming are finely interleaved. In this paper we present a smell detector that we have built with floss refactoring in mind by combining seven habits that we postulate are important to consider when designing usable smell detectors. We hope that this combination can help the designers of future smell detectors build tools that align with the way that programmers refactor.Keywords
Funding Information
- Division of Computing and Communication Foundations (CCF-0520346)
This publication has 11 references indexed in Scilit:
- A catalogue of lightweight visualizations to support code smell inspection2008
- Refactoring Tools: Fitness for PurposeIEEE Software, 2008
- JDeodorant: Identification and Removal of Type-Checking Bad Smells2008
- Design Guidelines for Ambient Software Visualization in the Workplace2007
- Refactoring Practice: How it is and How it Should be Supported - An Eclipse Case Study2007 IEEE International Conference on Software Maintenance, 2006
- Building Usage Contexts During Program Comprehension2006
- Supporting Refactoring Activities Using Histories of Program ModificationIEICE Transactions on Information and Systems, 2006
- An experiment on subjective evolvability evaluation of object-oriented software: explaining factors and interrater agreement2005
- Mylar2005
- A case study in refactoring a legacy component for reuse in a product line2005