arrow
Return

Barriers to Refactoring

delete2017-09-25
delete15
PRE
AI
E
Ewan Tempero *
T
Tony Gorschek
L
Lefteris Angelis
DOI:10.1145/3131873delete
deleteOriginal
deleteOriginal request for help
deleteShare
deleteSave
Abstract

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.
Keywords:
METRICS
SOFTWARE
AI Summary

AI Summary

Key information extracted from the uploaded paper, including a brief overview, abstract, background, key highlights, visual analysis, and future outlook.

Journal

Communications of the ACM cover
Communications of the ACM
IF:
12.2
Papers:
1.2W
Citations:
3.7W

Organization

U
University of Auckland
Scholars:
2.3W
Papers: 2.4W
Citations: 3.3W
B
blekinge institute technology
Scholars:
744
Papers: 760
Citations: 5
A
aristotle university of thessaloniki
Scholars:
2.6W
Papers: 2.0W
Citations: 19
researcher View more organizations