Refactoring improving the design of existing code
The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
The present document contains the most relevant results obtained in the study of refactoring. Mainly it addresses the general aspects of refactoring and the basic concepts that make it up, then it details the how, why and when to apply refactoring in computer systems that have been poorly designed, this in order to a better performance and maintenance of the constituent components. Finally, it is emphasized the importance of the refactoring process as such in software development.
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
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
Cited by
DECOR: A Method for the Specification and Detection of Code and Design Smells
Moha, N., Gueheneuc, Y.-G., Duchien, L., & Le Meur, A.-F. (2010) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2009.50 · Cited by 803
Detection strategies: metrics-based rules for detecting design flaws
Marinescu, R. (2004) · 20th IEEE International Conference on Software Maintenance, 2004. Proceedings. · doi:10.1109/icsm.2004.1357820 · Cited by 551
Roy, C. K., & Cordy, J. R. (2008) · 2008 16th IEEE International Conference on Program Comprehension · doi:10.1109/icpc.2008.41 · Cited by 533
A systematic literature review on agile requirements engineering practices and challenges
Inayat, I., Salim, S. S., Marczak, S., Daneva, M., & Shamshirband, S. (2015) · Computers in Human Behavior · doi:10.1016/j.chb.2014.10.046 · Cited by 521
Refactoring the nitrogen fixation gene cluster from Klebsiella oxytoca
Temme, K., Zhao, D., & Voigt, C. A. (2012) · Proceedings of the National Academy of Sciences · doi:10.1073/pnas.1120788109 · Cited by 419
Metadata
- Authors
- Saca, M. A.
- Venue
- 2017 IEEE 37th Central America and Panama Convention (CONCAPAN XXXVII)
- Publisher
- IEEE
- Published
- 2017-11
- Pages
- 1-3
- OpenAlex
- W2787379525
- Cited by
- 2,054
- References
- 1
- FWCI
- 90.85
- Type
- conference paper
- Language
- en
- Open access
- closed
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.