The DOI matches its Crossref record; 37 of the 37 references it cites were found in a registry or an index.
A survey of software refactoring
Open accessAbstract
We provide an extensive overview of existing research in the field of software refactoring. This research is compared and discussed based on a number of different criteria: the refactoring activities that are supported, the specific techniques and formalisms that are used for supporting these activities, the types of software artifacts that are being refactored, the important issues that need to be taken into account when building refactoring tool support, and the effect of refactoring on the software process. A running example is used to explain and illustrate the main concepts.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
(1994) · Cited by 21,711
Extreme Programming Explained: Embrace Change
Beck, K. L., & Andres, C. (2000) · Cited by 5,902
Refactoring: Improving the Design of Existing Code
Fowler, M. (2002) · Lecture Notes in Computer Science · doi:10.1007/3-540-45672-4_31 · Cited by 5,591
Formal Concept Analysis: Mathematical Foundations
Ganter, B., Wille, R., & Franzke, C. (1998) · CERN Document Server (European Organization for Nuclear Research) · Cited by 4,245
Weiser, M. (1984) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1984.5010248 · Cited by 3,204
Reverse engineering and design recovery: a taxonomy
Chikofsky, E. J., & Cross, J. H. (1990) · IEEE Software · doi:10.1109/52.43044 · Cited by 2,012
Program development by stepwise refinement
Wirth, N. (1971) · Communications of the ACM · doi:10.1145/362575.362577 · Cited by 960
A language independent approach for detecting duplicated code
Ducasse, S., Rieger, M., & Demeyer, S. (1999) · Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360) · doi:10.1109/icsm.1999.792593 · Cited by 615
Software maintenance management
Lientz, B. P., & Swanson, E. B. (1980) · CERN Document Server (European Organization for Nuclear Research) · Cited by 604
Using metrics to evaluate software system maintainability
Coleman, D., Ash, D., Lowther, B., & Oman, P. (1994) · Computer · doi:10.1109/2.303623 · Cited by 431
Cited by
Enabling Flexibility in Process-Aware Information Systems
Reichert, M., & Weber, B. (2012) · Springer eBooks · doi:10.1007/978-3-642-30409-5 · Cited by 414
Identification of Move Method Refactoring Opportunities
Tsantalis, N., & Chatzigeorgiou, A. (2009) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2009.1 · Cited by 339
Quantifying the Effect of Code Smells on Maintenance Effort
Sjoberg, D. I. K., Yamashita, A., Anda, B. C. D., Mockus, A., & Dyba, T. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2012.89 · Cited by 316
Why we refactor? confessions of GitHub contributors
Silva, D., Tsantalis, N., & Valente, M. T. (2016) · Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering · doi:10.1145/2950290.2950305 · Cited by 280
CatchUp!: capturing and replaying refactorings to support API evolution
Henkel, J., & Diwan, A. (2005) · Proceedings of the 27th international conference on Software engineering - ICSE '05 · doi:10.1145/1062455.1062512 · Cited by 269
(2012) · doi:10.1145/2393596.2393655 · Cited by 239
An Empirical Study of RefactoringChallenges and Benefits at Microsoft
Kim, M., Zimmermann, T., & Nagappan, N. (2014) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2014.2318734 · Cited by 231
“In this paper, we address the following research questions: (1) What is the definition of refactoring from developers’ perspectives? By refactoring, do developers indeedmean behavior-preserving code transformations that modify a program structure [1], [10]? (2) What is the developers’ perception about refactoring bene…”
BackgroundInfluentialSubjective evaluation of software evolvability using code smells: An empirical study
Mäntylä, M. V., & Lassenius, C. (2007) · Empirical Software Engineering · doi:10.1007/s10664-006-9002-8 · Cited by 171
Adaptive user interfaces and universal usability through plasticity of user interface design
Miraz, M. H., Ali, M., & Excell, P. S. (2021) · Computer Science Review · doi:10.1016/j.cosrev.2021.100363 · Cited by 158
Challenges to and Solutions for Refactoring Adoption: An Industrial Perspective
Sharma, T., Suryanarayana, G., & Samarthyam, G. (2015) · IEEE Software · doi:10.1109/ms.2015.105 · Cited by 46
Learning Performance-Improving Code Edits
Shypula, A., Madaan, A., Zeng, Y., Alon, U., Gardner, J., Hashemi, M., Neubig, G., Ranganathan, P., Bastani, O., & Yazdanbakhsh, A. (2023) · arXiv · doi:10.48550/arxiv.2302.07867 · Cited by 146
“Machine learning has been applied to improve performance by refactoring code (Mens & Tourwé, 2004; Ag-nihotri & Chug, 2020), identify compiler transformations (Bacon et al., 1994; Talaashrafi, 2022; Mammadli et al., 2021), perform parameter search (Hamadi, 2013; Huang et al., 2019; Kaufman et al.,…”
Method
Metadata
- Authors
- Mens, T., & Tourwe, T.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2004-02
- Volume
- 30
- Issue
- 2
- Pages
- 126-139
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2171383742
- Cited by
- 1,193
- References
- 37
- FWCI
- 142.10
- Type
- journal article
- Language
- en
- Open access
- green
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.