Show simple item record

dc.contributor.authorZhang, Min
dc.contributor.authorBaddoo, N.
dc.contributor.authorWernick, P.
dc.contributor.authorHall, T.
dc.date.accessioned2011-11-02T11:01:27Z
dc.date.available2011-11-02T11:01:27Z
dc.date.issued2011-01-01
dc.identifier.citationZhang , M , Baddoo , N , Wernick , P & Hall , T 2011 , Prioritising refactoring using code bad smells . in Proceedings - 4th IEEE International Conference on Software Testing, Verification, and Validation Workshops, ICSTW 2011 . Institute of Electrical and Electronics Engineers (IEEE) , pp. 458-464 , ICSTW 2011, 4th IEEE International Conference on Software Testing, Verification, and Validation Workshops , Berlin , Germany , 21/03/11 . https://doi.org/10.1109/ICSTW.2011.69
dc.identifier.citationconference
dc.identifier.isbn978-076954345-1
dc.identifier.otherPURE: 437723
dc.identifier.otherPURE UUID: ed256763-90a4-4e12-8fd2-a95d6be6a179
dc.identifier.otherScopus: 80051658713
dc.identifier.urihttp://hdl.handle.net/2299/6883
dc.description“This material is presented to ensure timely dissemination of scholarly and technical work. Copyright and all rights therein are retained by authors or by other copyright holders. All persons copying this information are expected to adhere to the terms and constraints invoked by each author's copyright. In most cases, these works may not be reposted without the explicit permission of the copyright holder." “Copyright IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.”
dc.description.abstractWe investigated the relationship between six of Fowler et al.'s Code Bad Smells (Duplicated Code, Data Clumps, Switch Statements, Speculative Generality, Message Chains, and Middle Man) and software faults. In this paper we discuss how our results can be used by software developers to prioritise refactoring. In particular we suggest that source code containing Duplicated Code is likely to be associated with more faults than source code containing the other five Code Bad Smells. As a consequence, Duplicated Code should be prioritised for refactoring. Source code containing Message Chains seems to be associated with a high number of faults in some situations. Consequently it is another Code Bad Smell which should be prioritised for refactoring. Source code containing only one of the Data Clumps, Switch Statements, Speculative Generality, or Middle Man Bad Smell is not likely to be fault-prone. As a result these Code Bad Smells could be put into a lower refactoring priority.en
dc.format.extent7
dc.language.isoeng
dc.publisherInstitute of Electrical and Electronics Engineers (IEEE)
dc.relation.ispartofProceedings - 4th IEEE International Conference on Software Testing, Verification, and Validation Workshops, ICSTW 2011
dc.subjectcode bad smells
dc.subjectfault
dc.subjectrefactoring
dc.titlePrioritising refactoring using code bad smellsen
dc.contributor.institutionScience & Technology Research Institute
dc.contributor.institutionSchool of Computer Science
dc.identifier.urlhttp://www.scopus.com/inward/record.url?scp=80051658713&partnerID=8YFLogxK
dc.identifier.urlhttp://sites.google.com/site/icst2011/
rioxxterms.versionofrecordhttps://doi.org/10.1109/ICSTW.2011.69
rioxxterms.typeOther
herts.preservation.rarelyaccessedtrue


Files in this item

FilesSizeFormatView

There are no files associated with this item.

This item appears in the following Collection(s)

Show simple item record