Do bad smells indicate "trouble" in code?

M. Zhang, T. Hall, N. Baddoo, P. Wernick

Research output: Chapter in Book/Report/Conference proceedingConference contribution

9 Citations (Scopus)

Abstract

In 1999 Fowler et al. identified 22 Bad Smells in code to direct the effective refactoring. These are increasingly being used by software engineers. However, the empirical basis of using Bad Smells to direct refactoring and to address 'trouble' in code is not clear. Our project aims to empirically investigate the impact of Bad Smells on software in terms of their relationship to faults.
Original languageEnglish
Title of host publicationProceedings of the 2008 workshop on Defects in Large Software Systems (DEFECTS '08)
PublisherACM Press
Pages43-44
ISBN (Print)978-1-60558-051-7
DOIs
Publication statusPublished - 2008

Fingerprint

Dive into the research topics of 'Do bad smells indicate "trouble" in code?'. Together they form a unique fingerprint.

Cite this