Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Barriers to Refactoring
Univ Auckland, NZL.
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.
Aristotle Univ Thessaloniki, GRC.
2017 (English)In: Communications of the ACM, ISSN 0001-0782, E-ISSN 1557-7317, Vol. 60, no 10, p. 54-61Article in journal (Refereed) Published
Abstract [en]

REFACTORING(6) IS SOMETHING software developers like to do. They refactor a lot. But do they refactor as much as they would like? Are there barriers that prevent them from doing so? Refactoring is an important tool for improving quality. Many development methodologies rely on refactoring, especially for agile methodologies but also in more plan-driven organizations. If barriers exist, they would undermine the effectiveness of many product-development organizations. We conducted a large-scale survey in 2009 of 3,785 practitioners' use of object-oriented concepts, 7 including questions as to whether they would refactor to deal with certain design problems. We expected either that practitioners would tell us our choice of design principles was inappropriate for basing a refactoring decision or that refactoring is the right decision to take when designs were believed to have quality problems. However, we were told the decision of whether or not to refactor was due to non-design considerations. It is now eight years since the survey, but little has changed in integrated development environment (IDE) support for refactoring, and what has changed has done little to address the barriers we identified.

Place, publisher, year, edition, pages
ASSOC COMPUTING MACHINERY , 2017. Vol. 60, no 10, p. 54-61
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-15364DOI: 10.1145/3131873ISI: 000411817600022OAI: oai:DiVA.org:bth-15364DiVA, id: diva2:1151187
Available from: 2017-10-23 Created: 2017-10-23 Last updated: 2018-01-13Bibliographically approved

Open Access in DiVA

No full text in DiVA

Other links

Publisher's full text

Authority records BETA

Gorschek, Tony

Search in DiVA

By author/editor
Gorschek, Tony
By organisation
Department of Software Engineering
In the same journal
Communications of the ACM
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 37 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf