• DocumentCode
    2347169
  • Title

    Clones: What is that smell?

  • Author

    Rahman, Foyzur ; Bird, Christian ; Devanbu, Premkumar

  • Author_Institution
    Dept. of Comput. Sci., Univ. of California, Davis, Davis, CA, USA
  • fYear
    2010
  • fDate
    2-3 May 2010
  • Firstpage
    72
  • Lastpage
    81
  • Abstract
    Clones are generally considered bad programming practice in software engineering folklore. They are identified as a bad smell and a major contributor to project maintenance difficulties. Clones inherently cause code bloat, thus increasing project size and maintenance costs. In this work, we try to validate the conventional wisdom empirically to see whether cloning makes code more defect prone. This paper analyses relationship between cloning and defect proneness. We find that, first, the great majority of bugs are not significantly associated with clones. Second, we find that clones may be less defect prone than non-cloned code. Finally, we find little evidence that clones with more copies are actually more error prone. Our findings do not support the claim that clones are really a ¿bad smell¿. Perhaps we can clone, and breathe easy, at the same time.
  • Keywords
    program debugging; software maintenance; bugs; clones; code bloat; defect proneness; project maintenance; software engineering; Birds; Cloning; Computer bugs; Computer science; Costs; Productivity; Programming; Software engineering; Software maintenance; Taxonomy; empirical software engineering; software clone; software evolution; software maintenance;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Mining Software Repositories (MSR), 2010 7th IEEE Working Conference on
  • Conference_Location
    Cape Town
  • Print_ISBN
    978-1-4244-6802-7
  • Electronic_ISBN
    978-1-4244-6803-4
  • Type

    conf

  • DOI
    10.1109/MSR.2010.5463343
  • Filename
    5463343