Relevant bibliographies by topics / Software refactoring

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers

Academic literature on the topic 'Software refactoring'

Author: Grafiati
Published: 4 June 2021
Last updated: 25 July 2025

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software refactoring.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Software refactoring"

1

Traini, Luca, Daniele Di Pompeo, Michele Tucci, et al. "How Software Refactoring Impacts Execution Time." ACM Transactions on Software Engineering and Methodology 31, no. 2 (2022): 1–23. http://dx.doi.org/10.1145/3485136.

Full text
Abstract:
Refactoring aims at improving the maintainability of source code without modifying its external behavior. Previous works proposed approaches to recommend refactoring solutions to software developers. The generation of the recommended solutions is guided by metrics acting as proxy for maintainability (e.g., number of code smells removed by the recommended solution). These approaches ignore the impact of the recommended refactorings on other non-functional requirements, such as performance, energy consumption, and so forth. Little is known about the impact of refactoring operations on non-functi
APA, Harvard, Vancouver, ISO, and other styles
2

Gheyi, Rohit, Tiago Massoni, and Paulo Borba. "Algebraic Laws for Feature Models." JUCS - Journal of Universal Computer Science 14, no. (21) (2008): 3573–91. https://doi.org/10.3217/jucs-014-21-3573.

Full text
Abstract:
Software Product Lines (SPL) may be adopted by either bootstrapping existing software products into a SPL, or extending an existing SPL to encompass an additional software product. Program refactorings are usually applied for carrying out those tasks. The notion of SPL refactoring is an extension of the traditional definition of refactoring; it involves not only program refactorings, but also Feature Model (FM) refactorings, in order to improve configurability. However, FM refactorings are hard to define, due to the incompleteness of the refactoring catalogs developed as of today. In this pape
APA, Harvard, Vancouver, ISO, and other styles
3

Ribeiro, Tayse Virgulino. "Android Applications based on software repository analysis." Singular Engenharia, Tecnologia e Gestão 1, no. 2 (2019): 6–13. http://dx.doi.org/10.33911/singular-etg.v1i2.55.

Full text
Abstract:
Context: Software repositories have been a source for studies about software evolution and its relation to software defects. In addition, the context of repositories has also been used for the purpose of analyzing refactoring practiced by programmers throughout the development process. Objective: Our objective is based on android projects stored in software repositories, to determine what types of transformations, that is, which refactorings are used, seeking to relate them to quality and security factors. Method: This research uses as an approach an exploratory study of a qualitative characte
APA, Harvard, Vancouver, ISO, and other styles
4

Kanwal, Jaweria, Onaiza Maqbool, Hamid Abdul Basit, Muddassar Azam Sindhu, and Katsuro Inoue. "Historical perspective of code clone refactorings in evolving software." PLOS ONE 17, no. 12 (2022): e0277216. http://dx.doi.org/10.1371/journal.pone.0277216.

Full text
Abstract:
Cloning in software is generally perceived as a threat to its maintenance and that is why it needs to be managed properly. Understanding clones from a historical perspective is essential for effective clone management. Analysis of code refactorings performed on clones in previous releases will help developers in taking decisions about clone refactoring in future releases. In this paper we perform a longitudinal study on the evolution of clone refactorings in various versions of five software systems. To perform a systematic study on clone refactoring evolution, we define clone evolution patter
APA, Harvard, Vancouver, ISO, and other styles
5

SEREBRENIK, ALEXANDER, TOM SCHRIJVERS, and BART DEMOEN. "Improving Prolog programs: Refactoring for Prolog." Theory and Practice of Logic Programming 8, no. 2 (2008): 201–15. http://dx.doi.org/10.1017/s1471068407003134.

Full text
Abstract:
AbstractRefactoring is an established technique from the object-oriented (OO) programming community to restructure code: it aims at improving software readability, maintainability, and extensibility. Although refactoring is not tied to the OO-paradigm in particular, its ideas have not been applied to logic programming until now. This paper applies the ideas of refactoring to Prolog programs. A catalogue is presented listing refactorings classified according to scope. Some of the refactorings have been adapted from the OO-paradigm, while others have been specifically designed for Prolog. The di
APA, Harvard, Vancouver, ISO, and other styles
6

Berciu, Liviu-Marian, and Vasilica Moldovan. "Software Maintainability and Refactorings Prediction Based on Technical Debt Issues." Studia Universitatis Babeș-Bolyai Informatica 68, no. 2 (2023): 22–40. http://dx.doi.org/10.24193/subbi.2023.2.02.

Full text
Abstract:
Software maintainability is a crucial factor impacting cost, time and resource allocation for software development. Code refactorings greatly enhance code quality, readability, understandability and extensibility. Hence, accurate prediction methods for both maintainability and refactorings are vital for long-term project sustainability and success, offering substantial benefits to the software community as a whole. This article focuses on prediction of software maintainability and the number of needed code refactorings using technical debt data. Two approaches were explored, one compressing te
APA, Harvard, Vancouver, ISO, and other styles
7

Akhtar, Salwa Muhammad, Makia Nazir, Arshad Ali, Ahmad Salman Khan, Muhammad Atif, and Mudassar Naseer. "A Systematic Literature Review on Software- refactoring Techniques, Challenges, and Practices." VFAST Transactions on Software Engineering 10, no. 4 (2022): 93–103. http://dx.doi.org/10.21015/vtse.v10i4.1275.

Full text
Abstract:
Software-refactoring improves the quality and reduces the complexity during the whole life cycle of the software system. The objective of this work is to elicit the existing challenges and refactoring techniques and practices to counter those challenges. This study presents a systematic literature review based upon the scientific literature published since January 2000. After rigorously applying the SLR protocol defined by Barbara Kitchenham, we identify 36 articles discussing software- refactoring challenges, techniques, and practices. We point out complexity, understandability, and maintaina
APA, Harvard, Vancouver, ISO, and other styles
8

Almogahed, Abdullah, and Mazni Omar. "Refactoring Techniques for Improving Software Quality: Practitioners’ Perspectives." Journal of Information and Communication Technology 20, No.4 (2021): 511–39. http://dx.doi.org/10.32890/jict2021.20.4.3.

Full text
Abstract:
Refactoring is a critical task in software maintenance and is commonly applied to improve system design or to cope with design defects. There are 68 different types of refactoring techniques and each technique has a particular purpose and effect. However, most prior studies have selected refactoring techniques based on their common use in academic research without obtaining evidence from the software industry. This is a shortcoming that points to the existence of a clear gap between academic research and the corresponding industry practices. Therefore, to bridge this gap, this study identified
APA, Harvard, Vancouver, ISO, and other styles
9

Hodovychenko, Mykola A., and Dmytro D. Kurinko. "Analysis of existing approaches to automated refactoring of object-oriented software systems." Herald of Advanced Information Technology 8, no. 2 (2025): 179–96. https://doi.org/10.15276/hait.08.2025.11.

Full text
Abstract:
Automated refactoring plays a crucial role in the maintenance and evolution of object-oriented software systems, where improving internal code structure directly impacts maintainability, scalability, and technical debt reduction. This paper presents an extended review of current approaches to automated refactoring, emphasizing methodological foundations, automation levels, the application of artificial intelligence, and practical integration into CI/CD workflows. We examine rule-based, graph-based, machine learning–based (CNNs, GNNs, LLMs), and history-aware (MSR) techniques, along with hybrid
APA, Harvard, Vancouver, ISO, and other styles
10

Sharma, Divya, and Shikha Lohchab. "Search based Software Engineering of Software Metrics, Code Smells and Refactoring Techniques Using Optimization Algorithms." NeuroQuantology 20, no. 5 (2022): 195–203. http://dx.doi.org/10.14704/nq.2022.20.5.nq22163.

Full text
Abstract:
Software refactoring is a technique for reorganising and improving the efficiency of existing software code. By refining the non-functional aspects of software, numerous refactoring methods are currently being employed to build more intelligible and less composite codes. By applying multiple systems to the source code, refactoring can improve code maintainability even further, preserving the behaviour of the code. Refactoring allows for the eradication of bugs and the expansion of the program's capabilities. This paper provides a comprehensive assessment of source code with foul odours, the in
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Software refactoring"

1

Haendler, Thorsten, and Gustaf Neumann. "Serious Games for Software Refactoring." IEEE, 2019. http://epub.wu.ac.at/6973/1/0767.pdf.

Full text
Abstract:
Software design issues can severely impede software development and maintenance. Thus, it is important for the success of software projects that developers are aware of bad smells in code artifacts and improve their skills to reduce these issues via refactoring. However, software refactoring is a complex activity and involves multiple tasks and aspects. Therefore, imparting competences for identifying bad smells and refactoring code efficiently is challenging for software engineering education and training. The approaches proposed for teaching software refactoring in recent years mostly conce
APA, Harvard, Vancouver, ISO, and other styles
2

Murphy-Hill, Emerson. "Programmer Friendly Refactoring Tools." PDXScholar, 2009. https://pdxscholar.library.pdx.edu/open_access_etds/2672.

Full text
Abstract:
Tools that perform semi-automated refactoring are currently under-utilized by programmers. If more programmers adopted refactoring tools, software projects could make enormous productivity gains. However, as more advanced refactoring tools are designed, a great chasm widens between how the tools must be used and how programmers want to use them. This dissertation begins to bridge this chasm by exposing usability guidelines to direct the design of the next generation of programmer-friendly refactoring tools, so that refactoring tools fit the way programmers behave, not vice-versa.
APA, Harvard, Vancouver, ISO, and other styles
3

Li, Huiqing. "Refactoring Haskell programs." Thesis, University of Kent, 2006. https://kar.kent.ac.uk/14425/.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Mohan, Michael. "Automated software maintenance using search-based refactoring." Thesis, Queen's University Belfast, 2018. https://pure.qub.ac.uk/portal/en/theses/automated-software-maintenance-using-searchbased-refactoring(f3e1a3fd-7150-45d8-b29d-4b973ba38137).html.

Full text
Abstract:
Search-based software maintenance (SBSM) is an area of research that uses refactorings, software metrics and search-based optimisation algorithms to automate aspects of the software maintenance process. Refactorings are used to improve the structure of software without affecting its functionality. Search-based optimisation algorithms can be adapted to use refactorings to modify software, relying on metrics to deduce how successful the refactorings have been along the way. The research conducted in this thesis aims to explore the research area of SBSM and experiment with methods to automate sof
APA, Harvard, Vancouver, ISO, and other styles
5

SABINO, Melina Mongiovi Cunha Lima. "Scaling testing of refactoring engines." Universidade Federal de Campina Grande, 2016. http://dspace.sti.ufcg.edu.br:8080/jspui/handle/riufcg/883.

Full text
Abstract:
Submitted by Maria Medeiros (maria.dilva1@ufcg.edu.br) on 2018-06-05T13:58:29Z No. of bitstreams: 1 MELINA MONGIOVI CUNHA LIMA SABINO - TESE (PPGCC) 2016.pdf: 4752189 bytes, checksum: e1034c42632a733df07a498a7eea6d0b (MD5)<br>Made available in DSpace on 2018-06-05T13:58:29Z (GMT). No. of bitstreams: 1 MELINA MONGIOVI CUNHA LIMA SABINO - TESE (PPGCC) 2016.pdf: 4752189 bytes, checksum: e1034c42632a733df07a498a7eea6d0b (MD5) Previous issue date: 2016<br>Capes<br>Definir e implementar refatoramentos não é uma tarefa trivial, pois é difícil definir todas as pré-condições necessárias para garantir q
APA, Harvard, Vancouver, ISO, and other styles
6

REGO, DIEGO CEDRIM GOMES. "UNDERSTANDING AND IMPROVING BATCH REFACTORING IN SOFTWARE SYSTEMS." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2018. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=36103@1.

Full text
Abstract:
PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO<br>COORDENAÇÃO DE APERFEIÇOAMENTO DO PESSOAL DE ENSINO SUPERIOR<br>CONSELHO NACIONAL DE DESENVOLVIMENTO CIENTÍFICO E TECNOLÓGICO<br>PROGRAMA DE EXCELENCIA ACADEMICA<br>Em um sistema de software, as anomalias de código indicam problemas estruturais que podem ser resolvidos através da refatoração. No entanto, desenvolvedores podem negligenciar ou acabar criando novas anomalias ao refatorar. Pouco foi relatado sobre os efeitos benéficos e prejudiciais da refatoração de anomalias de código. Evidências sugerem que os desenvolvedores frequentemente
APA, Harvard, Vancouver, ISO, and other styles
7

Paixao, Matheus. "Software restructuring : understanding longitudinal architectural changes and refactoring." Thesis, University College London (University of London), 2018. http://discovery.ucl.ac.uk/10060511/.

Full text
Abstract:
The complexity of software systems increases as the systems evolve. As the degradation of the system's structure accumulates, maintenance effort and defect-proneness tend to increase. In addition, developers often opt to employ sub-optimal solutions in order to achieve short-time goals, in a phenomenon that has been recently called technical debt. In this context, software restructuring serves as a way to alleviate and/or prevent structural degradation. Restructuring of software is usually performed in either higher or lower levels of granularity, where the first indicates broader changes in t
APA, Harvard, Vancouver, ISO, and other styles
8

Gilliland, Sean M. (Sean Michael). "Empirical analysis of software refactoring motivation and effects." Thesis, Massachusetts Institute of Technology, 2015. http://hdl.handle.net/1721.1/100376.

Full text
Abstract:
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, System Design and Management Program, 2015.<br>Cataloged from PDF version of thesis.<br>Includes bibliographical references (pages 68-69).<br>As complexity and levels of technical debt within software systems increase over time the incentive of an organization to refactor legacy software likewise increases. However, the opportunity cost of such refactoring in terms of engineering time and monetary investment have proven difficult to effectively trade against the long term benefits o
APA, Harvard, Vancouver, ISO, and other styles
9

Zheng, Yilei. "IFSO: A Integrated Framework For Automatic/Semi-automatic Software Refactoring and Analysis." Digital WPI, 2004. https://digitalcommons.wpi.edu/etd-theses/241.

Full text
Abstract:
To automatically/semi-automatically improve internal structures of a legacy system, there are several challenges: most available software analysis algorithms focus on only one particular granularity level (e.g., method level, class level) without considering possible side effects on other levels during the process; the quality of a software system cannot be judged by a single algorithm; software analysis is a time-consuming process which typically requires lengthy interactions. In this thesis, we present a framework, IFSO (Integrated Framework for automatic/semi-automatic Software refactoring
APA, Harvard, Vancouver, ISO, and other styles
10

Kesseli, Pascal. "Semantic refactorings." Thesis, University of Oxford, 2017. http://ora.ox.ac.uk/objects/uuid:0c74954e-dc83-463f-bcd4-519d98c3dcca.

Full text
Abstract:
Refactorings are structured changes to existing software that leave its externally observable behaviour unchanged. The intent is to improve readability, performance or other non-behavioural properties of a program. Agile software engineering processes stress the importance of refactoring to keep program code extensible and maintainable. Despite their apparent benefits, manual refactorings are time-consuming and prone to introducing unintended side effects. Research efforts seek to support and automate refactoring tasks to overcome these limitations. Current research in automatic refactoring, a
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software refactoring"

1

Fields, Jay. Refactoring. Addison-Wesley, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Fields, Jay. Refactoring. Addison-Wesley, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Lippert, Martin. Refactoring in Large Software Projects. John Wiley & Sons, Ltd., 2006.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Wake, William C. Refactoring in Ruby. Addison-Wesley, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Wake, William C. Refactoring in Ruby. Addison-Wesley, 2009.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Wake, William C. Refactoring in Ruby. Addison-Wesley, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Laplante, Phillip A. AntiPatterns: Identification, refactoring, and management. Taylor & Francis, 2005.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Shane, Harvie, and Fowler Martin, eds. Refactoring: Ruby edition. Addison-Wesley Professional, 2009.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

1954-, Brown William J., ed. AntiPatterns: Refactoring software, architectures, and projects in crisis. Wiley, 1998.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Malveau, Raphael C. AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis. John Wiley & Sons, 1998.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software refactoring"

1

Crookshanks, Edward. "Refactoring." In Practical Software Development Techniques. Apress, 2014. http://dx.doi.org/10.1007/978-1-4842-0728-4_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Gähler, Marco. "Refactoring." In Software Engineering Made Easy. Apress, 2025. https://doi.org/10.1007/979-8-8688-1386-3_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Crookshanks, Edward. "Refactoring." In Practical Enterprise Software Development Techniques. Apress, 2015. http://dx.doi.org/10.1007/978-1-4842-0620-1_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Parsa, Saeed. "Automatic Refactoring." In Software Testing Automation. Springer International Publishing, 2023. http://dx.doi.org/10.1007/978-3-031-22057-9_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Power, Ken. "Refactoring the Organization." In Lean Enterprise Software and Systems. Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-16416-3_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

McComb, Tim. "Refactoring Object-Z Specifications." In Fundamental Approaches to Software Engineering. Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-24721-0_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Adams, Mark. "Refactoring Proofs with Tactician." In Software Engineering and Formal Methods. Springer Berlin Heidelberg, 2015. http://dx.doi.org/10.1007/978-3-662-49224-6_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Miller, Granville. "Refactoring with Aspects." In Extreme Programming and Agile Processes in Software Engineering. Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/3-540-44870-5_47.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Apel, Sven, Don Batory, Christian Kästner, and Gunter Saake. "Refactoring of Software Product Lines." In Feature-Oriented Software Product Lines. Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-37521-7_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Wynn-Williams, Stephen, Zinovy Diskin, Vera Pantelic, et al. "SL2SF: Refactoring Simulink to Stateflow." In Fundamental Approaches to Software Engineering. Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-16722-6_15.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software refactoring"

1

Brito, Aline, Andre Hora, and Marco Tulio Valente. "Understanding Refactoring Tasks over Time: A Study Using Refactoring Graphs." In Congresso Ibero-Americano em Engenharia de Software. Sociedade Brasileira de Computação, 2022. http://dx.doi.org/10.5753/cibse.2022.20982.

Full text
Abstract:
Refactoring is a fundamental practice in modern software development. Therefore, it is essential that practitioners have a solid understanding of refactoring, both in theory and in practice. In this paper, we rely on a graph-based abstraction — called refactoring graphs — to visualize and analyze refactorings performed by students in a canonical refactoring application: the Video Store System, proposed by Fowler. We asked 46 students to perform the refactorings included in this example under two scenarios: according to a list of explicit guidelines, where most students performed the tasks succ
APA, Harvard, Vancouver, ISO, and other styles
2

Silva, Bruno C. da, Eduardo Figueiredo, Alessandro Garcia, and Daltro J. Nunes. "On the Support and Application of Macro-Refactorings for Crosscutting Concerns." In Simpósio Brasileiro de Componentes, Arquiteturas e Reutilização de Software. Sociedade Brasileira de Computação, 2009. http://dx.doi.org/10.5753/sbcars.2009.24104.

Full text
Abstract:
Crosscutting concerns hinder software stability and reuse and, hence, refactorings have been proposed to modularise them using aspect-oriented programming technology. However, refactoring of crosscutting concerns is challenging and time-consuming because it involves many inter-dependent micro-refactorings. It may also be a repetitive task as recent studies have pointed out that most crosscutting concerns share a limited number of recurring shape patterns. This paper presents a family of macro-refactorings for modularising crosscutting concerns which share similar forms and patterns. It also pr
APA, Harvard, Vancouver, ISO, and other styles
3

Armijo, Guisella A., and Valter V. de Camargo. "Refactoring Recommendations with Machine Learning." In Anais Estendidos do Simpósio Brasileiro de Qualidade de Software. Sociedade Brasileira de Computação - SBC, 2022. http://dx.doi.org/10.5753/sbqs_estendido.2022.227650.

Full text
Abstract:
Refactoring is a well-known activity in software engineering that aims at changing a source-code snippet to improve structural quality attributes without changing the external behavior. It is known that manual refactoring is a common practice, but it is a time-consuming and error-prone activity. In literature it is possible to find approaches whose goal is to automatically recommend refactorings to software engineers. The goal is mainly to improve the productivity and internal quality of systems. However, we have observed that refactoring recommendations approaches are still immature, even tho
APA, Harvard, Vancouver, ISO, and other styles
4

Brito, Rodrigo, and Marco Tulio Valente. "RAID: Tool Support for Refactoring-Aware Code Reviews." In Congresso Brasileiro de Software: Teoria e Prática. Sociedade Brasileira de Computação - SBC, 2022. http://dx.doi.org/10.5753/cbsoft_estendido.2022.224945.

Full text
Abstract:
Code review is a key development practice that contributes to improve software quality and to foster knowledge sharing among developers. However, code review usually takes time and demands detailed and time-consuming analysis of textual diffs. Particularly, detecting refactorings during code reviews is not a trivial task, since they are not explicitly represented in diffs. For example, a Move Function refactoring is represented by deleted (-) and added lines (+) of code which can be located in different and distant source code files. To tackle this problem, we introduce RAID, a refactoring-awa
APA, Harvard, Vancouver, ISO, and other styles
5

Bezerra, Carla, Victor Anthony Alves, Antônio Hugo Lobo, João Paulo Queiroz, Lara Lima, and Paulo Meirelles. "Contributing to open-source projects in refactoring code smells: A practical experience in teaching Software Maintenance." In Simpósio Brasileiro de Engenharia de Software. Sociedade Brasileira de Computação, 2024. http://dx.doi.org/10.5753/sbes.2024.3507.

Full text
Abstract:
Code smells are inadequate code structures that can harm quality and maintainability. To remove these deficient structures, developers use refactoring techniques. Refactoring helps code be easier to understand and modify by eliminating potential problems and improving internal quality attributes. Most refactoring activities are usually performed manually and undisciplined, which can cause code degradation. Concepts, practices, software refactoring tools, and code smells are rarely discussed in undergraduate computing courses. This problem is reflected in the software industry, which generally
APA, Harvard, Vancouver, ISO, and other styles
6

Bibiano, Ana Carla, Alessandro Garcia, and Wesley K. G. Assunção. "A Large-Scale Study on Recommendations of Composite Refactorings in Practice." In Anais Estendidos do Congresso Brasileiro de Software: Teoria e Prática. Sociedade Brasileira de Computação - SBC, 2024. http://dx.doi.org/10.5753/cbsoft_estendido.2024.4116.

Full text
Abstract:
Refactoring is a non-trivial maintenance activity. Developers spend time and effort refactoring code to remove structural problems, i.e., code smells. Recent studies indicated that developers often apply composite refactoring (composite, for short), i.e., two or more interrelated refactorings. However, previous studies revealed that only 10% of composite refactorings in practice are considered complete, i.e., those fully removing code smells. However, the literature is scarce to catalog the most common complete composites and their side effects. Aim: To fill this gap, we performed a mixed-meth
APA, Harvard, Vancouver, ISO, and other styles
7

Bibiano, Ana Carla, and Alessandro Garcia. "On the Characterization, Detection and Impact of Batch Refactoring in Practice." In XI Congresso Brasileiro de Software: Teoria e Prática. Sociedade Brasileira de Computação - SBC, 2020. http://dx.doi.org/10.5753/cbsoft_estendido.2020.14626.

Full text
Abstract:
Up to 60% of the refactorings in software projects are constituted of a set of interrelated transformations, the so-called batches (or composite refactoring), rather than single transformations applied in isolation. However, a systematic characterization of batch characterization is missing, which hampers the elaboration of proper tooling support and empirical studies of how (batch) refactoring is applied in practice. This paper summarizes the research performed under the context of a Master's dissertation, which aimed at taming the aforementioned problems. To the best of our knowledge, our re
APA, Harvard, Vancouver, ISO, and other styles
8

Carneiro, Glauco de Figueiredo, and Manoel Gomes de Mendonça Neto. "Relacionando Refactorings e Métricas de Código Fonte - Um Primeiro Passo para Detecção Automática de Oportunidades de Refactoring." In Simpósio Brasileiro de Engenharia de Software. Sociedade Brasileira de Computação, 2003. http://dx.doi.org/10.5753/sbes.2003.23852.

Full text
Abstract:
Refactoring – melhorar a estrutura interna do software sem modificação no seu comportamento observável – é um mecanismo importante para se evitar a degradação da qualidade do software. Fundamental para tal finalidade é a identificação de trechos do código fonte que apresentam oportunidades de refactoring – comumente chamados de bad smells. Este artigo propõe uma abordagem para auxiliar na detecção de bad smells através de medição de código fonte e seu foco é a apresentação de um primeiro passo no sentido implementar esta abordagem. Para tal finalidade foi realizado um estudo que relaciona métr
APA, Harvard, Vancouver, ISO, and other styles
9

Ramos, Ricardo, Eduardo K. Piveta, Jaelson Castro, et al. "Improving the Quality of Requirements with Refactoring." In Simpósio Brasileiro de Qualidade de Software. Sociedade Brasileira de Computação - SBC, 2007. http://dx.doi.org/10.5753/sbqs.2007.15573.

Full text
Abstract:
Requirements specification can often exhibit some shortcomings, regarding contents and organization of its partial specification elements. Sometimes, modularization is deficient, with modules dealing with too much information, or the same functionality being specified in different modules. Left unchecked, these inadequacies will propagate themselves to the subsequent phases of the software development and cause problems during maintenance. We have been able to identify a collection of typical deficiencies in the specification of structured documents and we propose a collection of refactorings
APA, Harvard, Vancouver, ISO, and other styles
10

Counsell, S., and S. Swift. "Refactoring Steps, Java Refactorings and Empirical Evidence." In 2008 32nd Annual IEEE International Computer Software and Applications Conference. IEEE, 2008. http://dx.doi.org/10.1109/compsac.2008.148.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software refactoring' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography