Mikel Robredo
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Mikel Robredo has a total of 21 co-authors. Here are the top co-authors by number of shared publications:
- Valentina Lenarduzzi
University of Oulu
14 shared publications - Matteo Esposito
University of Oulu
12 shared publications - Davide Taibi
University of Southern Denmark
6 shared publications - Rafael Peñaloza
University of Milano-Bicocca, Milano, Italy
5 shared publications - Fabio Palomba
University of Salerno
4 shared publications - Murali Sridharan
University of Oulu
3 shared publications
Latest Publications
- Open Access
- 7 May 2026
- Published by Springer Nature in Empirical Software Engineering
- Vol. 31 (5) , 134
Analyzing the ripple effects of refactoring
Context: Short development cycles and continuous delivery pressure often push developers toward expedients that lead to poor design and hard-to-maintain systems. A common remedy is code refactoring, which reduces complexity and improves maintainability, though often seen as costly and risky. Objective: We investigate the long-term effects of refactoring to provide recommendations that support strategic development decisions. Method: We assess refactoring impact through change- and defect-proneness analysis, as well as benefit/effort evaluation. Results: Most refactorings have short-lived effects, persisting for fewer than 10 changes. Structural refactorings may last over 190 changes, with significant differences across families. Medium-lived refactorings (9–19 changes) prove the most stable and efficient, while longer-lasting ones become increasingly defect-prone and costly. Conclusions: Refactorings differ in sustainability. Medium-duration refactorings strike the best balance between stability and maintenance cost, while structural ones, though impactful, pose higher long-term risks. These insights guide prioritization of refactoring types to maximize benefit and minimize technical debt.
- 7 May 2026
- Published by Springer Nature in Empirical Software Engineering
- Vol. 31 (5) , 134
Open AccessAnalyzing the ripple effects of refactoring
Context: Short development cycles and continuous delivery pressure often push developers toward expedients that lead to poor design and hard-to-maintain systems. A common remedy is code refactoring, which reduces complexity and improves maintainability, though often seen as costly and risky. Objective: We investigate the long-term effects of refactoring to provide recommendations that support strategic development decisions. Method: We assess refactoring impact through change- and defect-proneness analysis, as well as benefit/effort evaluation. Results: Most refactorings have short-lived effects, persisting for fewer than 10 changes. Structural refactorings may last over 190 changes, with significant differences across families. Medium-lived refactorings (9–19 changes) prove the most stable and efficient, while longer-lasting ones become increasingly defect-prone and costly. Conclusions: Refactorings differ in sustainability. Medium-duration refactorings strike the best balance between stability and maintenance cost, while structural ones, though impactful, pose higher long-term risks. These insights guide prioritization of refactoring types to maximize benefit and minimize technical debt.
- Open Access
- 13 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 615-619
SQuaD: The Software Quality Dataset
Software quality research increasingly relies on large-scale datasets that measure both the product and process aspects of software systems. However, existing resources often focus on limited dimensions, such as code smells, technical debt, or refactoring activity, thereby restricting comprehensive analyses across isolated quality dimensions. To address this gap, we present the Software Quality Dataset (SQuaD), a multi-dimensional, time-aware collection of software quality metrics extracted from 450 mature open-source projects across diverse ecosystems, including Apache, Mozilla, FFmpeg, and the Linux kernel. By integrating nine state-of-the-art static analysis tools, i.e., SonarQube, CodeScene, PMD, Understand, CK, JaSoMe, RefactoringMiner, RefactoringMiner++, and PyRef, our dataset unifies over 700 unique metrics at method, class, file, and project levels. Covering a total of 63,586 analyzed project releases, SQuaD also provides version control and issue-tracking histories, software vulnerability data (CVE/CWE), and process metrics proven to enhance Just-In-Time (JIT) defect prediction. The SQuaD enables empirical research on maintainability, technical debt, software evolution, and quality assessment at unprecedented scale. We also outline emerging research directions, including automated dataset updates and cross-project quality modeling to support the continuous evolution of software analytics. The dataset is publicly available on ZENODO (DOI: 10.5281/zenodo.17566690).
- 13 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 615-619
Open AccessSQuaD: The Software Quality Dataset
Software quality research increasingly relies on large-scale datasets that measure both the product and process aspects of software systems. However, existing resources often focus on limited dimensions, such as code smells, technical debt, or refactoring activity, thereby restricting comprehensive analyses across isolated quality dimensions. To address this gap, we present the Software Quality Dataset (SQuaD), a multi-dimensional, time-aware collection of software quality metrics extracted from 450 mature open-source projects across diverse ecosystems, including Apache, Mozilla, FFmpeg, and the Linux kernel. By integrating nine state-of-the-art static analysis tools, i.e., SonarQube, CodeScene, PMD, Understand, CK, JaSoMe, RefactoringMiner, RefactoringMiner++, and PyRef, our dataset unifies over 700 unique metrics at method, class, file, and project levels. Covering a total of 63,586 analyzed project releases, SQuaD also provides version control and issue-tracking histories, software vulnerability data (CVE/CWE), and process metrics proven to enhance Just-In-Time (JIT) defect prediction. The SQuaD enables empirical research on maintainability, technical debt, software evolution, and quality assessment at unprecedented scale. We also outline emerging research directions, including automated dataset updates and cross-project quality modeling to support the continuous evolution of software analytics. The dataset is publicly available on ZENODO (DOI: 10.5281/zenodo.17566690).
- Open Access
- 28 February 2026
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Software Engineering and Methodology
A Critical Reflection on the State of Data Analysis in Empirical Software Engineering
Context. Empirical Software Engineering drives innovation in SE through qualitative and quantitative studies. Since the 2006 Dagstuhl seminar, concerns about methodological rigor persist. Recent studies have highlighted misconceptions in statistical practices in ESE, yet their impact on the field’s progress and verifiability remains uninvestigated. Aim. To analyze three decades of SE research to uncover flaws in statistical methods used for data analysis in empirical studies. Next, to observe the capability of current empirical software engineering experts to identify and address these issues. Method. We conducted a large-scale literature survey, collecting over 27,000 empirical SE papers. Using a Large Language Model (LLM), we categorized studies into methodologically adequate and not adequate categories, and selected 28 primary studies (14 from each category) for expert evaluation via a focus group-based workshop. Results. Our findings reveal widespread misuse of statistical methods in empirical SE studies. Additionally, experts often struggle to detect these flaws and provide proper corrections, raising concerns about methodological rigor in the field. Conclusions. This study highlights the risks of perpetuating statistical misconceptions and advocates for a critical reform in the approach to data analysis in ESE. We advocate for developing frameworks that foster methodological awareness and rigor.
- 28 February 2026
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Software Engineering and Methodology
Open AccessA Critical Reflection on the State of Data Analysis in Empirical Software Engineering
Context. Empirical Software Engineering drives innovation in SE through qualitative and quantitative studies. Since the 2006 Dagstuhl seminar, concerns about methodological rigor persist. Recent studies have highlighted misconceptions in statistical practices in ESE, yet their impact on the field’s progress and verifiability remains uninvestigated. Aim. To analyze three decades of SE research to uncover flaws in statistical methods used for data analysis in empirical studies. Next, to observe the capability of current empirical software engineering experts to identify and address these issues. Method. We conducted a large-scale literature survey, collecting over 27,000 empirical SE papers. Using a Large Language Model (LLM), we categorized studies into methodologically adequate and not adequate categories, and selected 28 primary studies (14 from each category) for expert evaluation via a focus group-based workshop. Results. Our findings reveal widespread misuse of statistical methods in empirical SE studies. Additionally, experts often struggle to detect these flaws and provide proper corrections, raising concerns about methodological rigor in the field. Conclusions. This study highlights the risks of perpetuating statistical misconceptions and advocates for a critical reform in the approach to data analysis in ESE. We advocate for developing frameworks that foster methodological awareness and rigor.
- Top Cited PapersOpen Access
- 28 February 2026
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Software Engineering and Methodology
What Were You Thinking? An LLM-Driven Large-Scale Study of Refactoring Motivations in Open-Source Projects
Context . Code refactoring improves software quality without changing external behavior. Despite its advantages, its benefits are hindered by the considerable cost of time, resources, and continuous effort it demands. Aim . Understanding why developers refactor, and which metrics capture these motivations, may support wider and more effective use of refactoring in practice. Method . We performed a large-scale empirical study to analyze developers’ refactoring activity, leveraging Large Language Models (LLMs) to identify underlying motivations from version control data, comparing our findings with previous motivations reported in the literature. Results . LLMs matched human judgment in 80% of cases, but aligned with literature-based motivations in only 47%. They enriched 22% of motivations with more detailed rationale, often highlighting readability, clarity, and structural improvements. Most motivations were pragmatic, focused on simplification and maintainability. While metrics related to developer experience and code readability ranked highest, their correlation with motivation categories was weak. Conclusions . We conclude that LLMs effectively capture surface-level motivations but struggle with architectural reasoning. Their value lies in providing localized explanations, which, when combined with software metrics, can form hybrid approaches. Such integration offers a promising path toward prioritizing refactoring more systematically and balancing short-term improvements with long-term architectural goals.
- 28 February 2026
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Software Engineering and Methodology
Top Cited PapersOpen AccessWhat Were You Thinking? An LLM-Driven Large-Scale Study of Refactoring Motivations in Open-Source Projects
Context . Code refactoring improves software quality without changing external behavior. Despite its advantages, its benefits are hindered by the considerable cost of time, resources, and continuous effort it demands. Aim . Understanding why developers refactor, and which metrics capture these motivations, may support wider and more effective use of refactoring in practice. Method . We performed a large-scale empirical study to analyze developers’ refactoring activity, leveraging Large Language Models (LLMs) to identify underlying motivations from version control data, comparing our findings with previous motivations reported in the literature. Results . LLMs matched human judgment in 80% of cases, but aligned with literature-based motivations in only 47%. They enriched 22% of motivations with more detailed rationale, often highlighting readability, clarity, and structural improvements. Most motivations were pragmatic, focused on simplification and maintainability. While metrics related to developer experience and code readability ranked highest, their correlation with motivation categories was weak. Conclusions . We conclude that LLMs effectively capture surface-level motivations but struggle with architectural reasoning. Their value lies in providing localized explanations, which, when combined with software metrics, can form hybrid approaches. Such integration offers a promising path toward prioritizing refactoring more systematically and balancing short-term improvements with long-term architectural goals.
- Open Access
- 27 February 2026
- Published by Springer Nature in Automated Software Engineering
- Vol. 33 (2) , 58
Generative AI as an infrastructure copilot: automating Infrastructure-As-Code across the DevSecOps lifecycle
Practitioners and researchers continuously focus on developing automation strategies to cope with the exponentially demanding need for the timely deployment of software projects in tight release schedules. Such automation techniques include Infrastructure-as-Code (IaC) and the DevOps and DevSecOps cycles. Recent studies investigated generative AI (GenAI) for generating infrastructure as code scripts. However, no studies have focused on using GenAI to generate IaC scripts based on DevSecOps stage artifacts. Different IaC tools serve varied purposes, requiring specific infrastructure setups for different project stages. We envision GenAI models leveraging artifacts from each DevSecOps stage to create and refine IaC scripts. We trust our approach to have an impact on practitioners to leverage it as an automatic copilot for infrastructure design and deployment, and for researchers to build on our vision and future empirical validation.
- 27 February 2026
- Published by Springer Nature in Automated Software Engineering
- Vol. 33 (2) , 58
Open AccessGenerative AI as an infrastructure copilot: automating Infrastructure-As-Code across the DevSecOps lifecycle
Practitioners and researchers continuously focus on developing automation strategies to cope with the exponentially demanding need for the timely deployment of software projects in tight release schedules. Such automation techniques include Infrastructure-as-Code (IaC) and the DevOps and DevSecOps cycles. Recent studies investigated generative AI (GenAI) for generating infrastructure as code scripts. However, no studies have focused on using GenAI to generate IaC scripts based on DevSecOps stage artifacts. Different IaC tools serve varied purposes, requiring specific infrastructure setups for different project stages. We envision GenAI models leveraging artifacts from each DevSecOps stage to create and refine IaC scripts. We trust our approach to have an impact on practitioners to leverage it as an automatic copilot for infrastructure design and deployment, and for researchers to build on our vision and future empirical validation.
- Open Access
A Defect is Being Born: How Close Are We? A Time Sensitive Forecasting Approach
Background. Defect prediction has been a highly active topic among researchers in the Empirical Software Engineering field. Previous literature has successfully achieved the most accurate prediction of an incoming fault and identified the features and anomalies that precede it through just-in-time prediction. As software systems evolve continuously, there is a growing need for time-sensitive methods capable of forecasting defects before they manifest. Aim. Our study seeks to explore the effectiveness of time-sensitive techniques for defect forecasting. Moreover, we aim to investigate the early indicators that precede the occurrence of a defect. Method. We will train multiple time-sensitive forecasting techniques to forecast the future bug density of a software project, as well as identify the early symptoms preceding the occurrence of a defect. Expected results. Our expected results are translated into empirical evidence on the effectiveness of our approach for early estimation of bug proneness.
Open AccessA Defect is Being Born: How Close Are We? A Time Sensitive Forecasting Approach
Background. Defect prediction has been a highly active topic among researchers in the Empirical Software Engineering field. Previous literature has successfully achieved the most accurate prediction of an incoming fault and identified the features and anomalies that precede it through just-in-time prediction. As software systems evolve continuously, there is a growing need for time-sensitive methods capable of forecasting defects before they manifest. Aim. Our study seeks to explore the effectiveness of time-sensitive techniques for defect forecasting. Moreover, we aim to investigate the early indicators that precede the occurrence of a defect. Method. We will train multiple time-sensitive forecasting techniques to forecast the future bug density of a software project, as well as identify the early symptoms preceding the occurrence of a defect. Expected results. Our expected results are translated into empirical evidence on the effectiveness of our approach for early estimation of bug proneness.
- Open Access
Hidden in Plain Sight: Where Developers Confess Self-Admitted Technical Debt
Context. Detecting Self-Admitted Technical Debt (SATD) is crucial for proactive software maintenance. Previous research has primarily targeted detecting and prioritizing SATD, with little focus on the source code afflicted with SATD. Our goal in this work is to connect the SATD comments with source code constructs that surround them. Method. We leverage the extensive SATD dataset PENTACET, containing code comments from over 9000 Java Open Source Software (OSS) repositories. We quantitatively infer where SATD most commonly occurs and which code constructs/statements it most frequently affects. Results and Conclusions. Our large-scale study links over 225,000 SATD comments to their surrounding code, showing that SATD mainly arises in inline code near definitions, conditionals, and exception handling, where developers face uncertainty and trade-offs, revealing it as an intentional signal of awareness during change rather than mere neglect.
Open AccessHidden in Plain Sight: Where Developers Confess Self-Admitted Technical Debt
Context. Detecting Self-Admitted Technical Debt (SATD) is crucial for proactive software maintenance. Previous research has primarily targeted detecting and prioritizing SATD, with little focus on the source code afflicted with SATD. Our goal in this work is to connect the SATD comments with source code constructs that surround them. Method. We leverage the extensive SATD dataset PENTACET, containing code comments from over 9000 Java Open Source Software (OSS) repositories. We quantitatively infer where SATD most commonly occurs and which code constructs/statements it most frequently affects. Results and Conclusions. Our large-scale study links over 225,000 SATD comments to their surrounding code, showing that SATD mainly arises in inline code near definitions, conditionals, and exception handling, where developers face uncertainty and trade-offs, revealing it as an intentional signal of awareness during change rather than mere neglect.
- Open Access
- 13 October 2025
- Published by Springer Nature in Software Quality Journal
- Vol. 33 (4) , 33
On the correlation between architectural smells and static analysis warnings
Software quality assurance is essential during software development and maintenance. Static Analysis Tools (SAT) are widely used for assessing code quality. Architectural smells are becoming more daunting to address and evaluate among quality issues. We aim to understand the relationships between Static Analysis Warnings (“warnings”) and Architectural Smells (“smell”) to guide developers/maintainers in focusing their effort on warnings more prone to co-occurring with smell. We performed an empirical study on 103 Java projects totaling 72 million LOC belonging to projects from a vast set of domains, and 785 warnings were detected by three SAT, Checkstyle, Findbugs, PMD, SonarQube, and 4 architectural smells were detected by the ARCAN tool. We analyzed how warnings influence smell presence. Finally, we proposed a smell remediation effort prioritization based on warning severity and warning proneness to specific smells. Our study reveals a moderate correlation between warnings and smells. Different combinations of SATs and warnings significantly affect smell occurrence, with certain warnings more Likely to co-occur with specific smells. Conversely, 33.79% of warnings are “non-co-occurring” with any of the smells in our dataset. This provides an early indicator for potential architectural concerns before resource-intensive architectural analysis is performed. Practitioners can ignore about a third of warnings and focus on those most likely to be associated with smells. Prioritizing smell remediation based on warning severity or warning proneness to specific smells results in effective rankings like those based on smell severity. While not a substitute for specialized tools like ARCAN, warning-based prioritization provides a pragmatic bridge between low-level warnings and high-level architectural issues, particularly useful in contexts lacking full architectural visibility.
- 13 October 2025
- Published by Springer Nature in Software Quality Journal
- Vol. 33 (4) , 33
Open AccessOn the correlation between architectural smells and static analysis warnings
Software quality assurance is essential during software development and maintenance. Static Analysis Tools (SAT) are widely used for assessing code quality. Architectural smells are becoming more daunting to address and evaluate among quality issues. We aim to understand the relationships between Static Analysis Warnings (“warnings”) and Architectural Smells (“smell”) to guide developers/maintainers in focusing their effort on warnings more prone to co-occurring with smell. We performed an empirical study on 103 Java projects totaling 72 million LOC belonging to projects from a vast set of domains, and 785 warnings were detected by three SAT, Checkstyle, Findbugs, PMD, SonarQube, and 4 architectural smells were detected by the ARCAN tool. We analyzed how warnings influence smell presence. Finally, we proposed a smell remediation effort prioritization based on warning severity and warning proneness to specific smells. Our study reveals a moderate correlation between warnings and smells. Different combinations of SATs and warnings significantly affect smell occurrence, with certain warnings more Likely to co-occur with specific smells. Conversely, 33.79% of warnings are “non-co-occurring” with any of the smells in our dataset. This provides an early indicator for potential architectural concerns before resource-intensive architectural analysis is performed. Practitioners can ignore about a third of warnings and focus on those most likely to be associated with smells. Prioritizing smell remediation based on warning severity or warning proneness to specific smells results in effective rankings like those based on smell severity. While not a substitute for specialized tools like ARCAN, warning-based prioritization provides a pragmatic bridge between low-level warnings and high-level architectural issues, particularly useful in contexts lacking full architectural visibility.
- 5 September 2025
- Published by Springer Nature
- p. 105-118
Autonomic Microservice Management via Agentic AI and MAPE-K Integration
- 5 September 2025
- Published by Springer Nature
- p. 105-118
Autonomic Microservice Management via Agentic AI and MAPE-K Integration
- Open Access
- 28 July 2025
- Published by Elsevier in Journal of Systems and Software
- Vol. 230
Evaluating time-dependent methods and seasonal effects in code technical debt prediction
- 28 July 2025
- Published by Elsevier in Journal of Systems and Software
- Vol. 230
Open AccessEvaluating time-dependent methods and seasonal effects in code technical debt prediction