Ricardo Britto
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Ricardo Britto has a total of 66 co-authors. Here are the top co-authors by number of shared publications:
- Lincoln Rocha
Federal University of Ceará
4 shared publications - Anita Sarma
Oregon State University, Corvallis, OR, USA
2 shared publications - Armando Sousa
UFPI
2 shared publications - Camilo Almendra
University of Ceará Fortaleza Ceará Brazil
2 shared publications - Igor Steinmacher
Northern Arizona University
2 shared publications - Igor Wiese
UTFPR
2 shared publications
Latest Publications
- Open Access
- 30 September 2026
- Published by Elsevier in Journal of Systems and Software
- Vol. 244
Large language models in software project management: A two-phase systematic literature review
- 30 September 2026
- Published by Elsevier in Journal of Systems and Software
- Vol. 244
Open AccessLarge language models in software project management: A two-phase systematic literature review
- Open Access
- 5 July 2026
- Published by Association for Computing Machinery (ACM)
- p. 101-110
MAS-SRE: A Multi-Agent System for Security Requirements Engineering
- 5 July 2026
- Published by Association for Computing Machinery (ACM)
- p. 101-110
Open AccessMAS-SRE: A Multi-Agent System for Security Requirements Engineering
- Open Access
- 22 September 2025
- Published by Sociedade Brasileira de Computação
- p. 337-347
Automatic Identification of Machine Learning-Specific Code Smells
Machine learning (ML) has rapidly grown in popularity, becoming vital to many industries. Currently, the research on code smells in ML applications lacks tools and studies that address the identification and validity of ML-specific code smells. This work investigates suitable methods and tools to design and develop a static code analysis tool (MLpylint) based on code smell criteria. This research employed the Design Science Methodology. In the problem identification phase, a literature review was conducted to identify ML-specific code smells. In solution design, a secondary literature review and consultations with experts were performed to select methods and tools for implementing the tool.We evaluated the tool on data from 160 open-source ML applications sourced from GitHub. We also conducted a static validation through an expert survey involving 15 ML professionals. The results indicate the effectiveness and usefulness of the MLpylint. We aim to extend our current approach by investigating ways to introduce MLpylint seamlessly into development workflows, fostering a more productive and innovative developer environment.
- 22 September 2025
- Published by Sociedade Brasileira de Computação
- p. 337-347
Open AccessAutomatic Identification of Machine Learning-Specific Code Smells
Machine learning (ML) has rapidly grown in popularity, becoming vital to many industries. Currently, the research on code smells in ML applications lacks tools and studies that address the identification and validity of ML-specific code smells. This work investigates suitable methods and tools to design and develop a static code analysis tool (MLpylint) based on code smell criteria. This research employed the Design Science Methodology. In the problem identification phase, a literature review was conducted to identify ML-specific code smells. In solution design, a secondary literature review and consultations with experts were performed to select methods and tools for implementing the tool.We evaluated the tool on data from 160 open-source ML applications sourced from GitHub. We also conducted a static validation through an expert survey involving 15 ML professionals. The results indicate the effectiveness and usefulness of the MLpylint. We aim to extend our current approach by investigating ways to introduce MLpylint seamlessly into development workflows, fostering a more productive and innovative developer environment.
- Open Access
Automatic Identification of Machine Learning-Specific Code Smells
Machine learning (ML) has rapidly grown in popularity, becoming vital to many industries. Currently, the research on code smells in ML applications lacks tools and studies that address the identification and validity of ML-specific code smells. This work investigates suitable methods and tools to design and develop a static code analysis tool (MLpylint) based on code smell criteria. This research employed the Design Science Methodology. In the problem identification phase, a literature review was conducted to identify ML-specific code smells. In solution design, a secondary literature review and consultations with experts were performed to select methods and tools for implementing the tool. We evaluated the tool on data from 160 open-source ML applications sourced from GitHub. We also conducted a static validation through an expert survey involving 15 ML professionals. The results indicate the effectiveness and usefulness of the MLpylint. We aim to extend our current approach by investigating ways to introduce MLpylint seamlessly into development workflows, fostering a more productive and innovative developer environment.
Open AccessAutomatic Identification of Machine Learning-Specific Code Smells
Machine learning (ML) has rapidly grown in popularity, becoming vital to many industries. Currently, the research on code smells in ML applications lacks tools and studies that address the identification and validity of ML-specific code smells. This work investigates suitable methods and tools to design and develop a static code analysis tool (MLpylint) based on code smell criteria. This research employed the Design Science Methodology. In the problem identification phase, a literature review was conducted to identify ML-specific code smells. In solution design, a secondary literature review and consultations with experts were performed to select methods and tools for implementing the tool. We evaluated the tool on data from 160 open-source ML applications sourced from GitHub. We also conducted a static validation through an expert survey involving 15 ML professionals. The results indicate the effectiveness and usefulness of the MLpylint. We aim to extend our current approach by investigating ways to introduce MLpylint seamlessly into development workflows, fostering a more productive and innovative developer environment.
- Open Access
- 18 December 2024
- Published by Association for Computing Machinery (ACM)
- p. 279-283
Static Program Analysis Guided LLM Based Unit Test Generation
- 18 December 2024
- Published by Association for Computing Machinery (ACM)
- p. 279-283
Open AccessStatic Program Analysis Guided LLM Based Unit Test Generation
- 27 November 2024
- Published by Springer Nature
- p. 100-115
An Automated Approach to Identify Source Code Files Affected by Architectural Technical Debt
- 27 November 2024
- Published by Springer Nature
- p. 100-115
An Automated Approach to Identify Source Code Files Affected by Architectural Technical Debt
- Open Access
Icing on the Cake: Automatic Code Summarization at Ericsson
This paper presents our findings on the automatic summarization of Java methods within Ericsson, a global telecommunications company. We evaluate the performance of an approach called Automatic Semantic Augmentation of Prompts (ASAP), which uses a Large Language Model (LLM) to generate leading summary comments for Java methods. ASAP enhances the $LLM's$ prompt context by integrating static program analysis and information retrieval techniques to identify similar exemplar methods along with their developer-written Javadocs, and serves as the baseline in our study. In contrast, we explore and compare the performance of four simpler approaches that do not require static program analysis, information retrieval, or the presence of exemplars as in the ASAP method. Our methods rely solely on the Java method body as input, making them lightweight and more suitable for rapid deployment in commercial software development environments. We conducted experiments on an Ericsson software project and replicated the study using two widely-used open-source Java projects, Guava and Elasticsearch, to ensure the reliability of our results. Performance was measured across eight metrics that capture various aspects of similarity. Notably, one of our simpler approaches performed as well as or better than the ASAP method on both the Ericsson project and the open-source projects. Additionally, we performed an ablation study to examine the impact of method names on Javadoc summary generation across our four proposed approaches and the ASAP method. By masking the method names and observing the generated summaries, we found that our approaches were statistically significantly less influenced by the absence of method names compared to the baseline. This suggests that our methods are more robust to variations in method names and may derive summaries more comprehensively from the method body than the ASAP approach.Open AccessIcing on the Cake: Automatic Code Summarization at Ericsson
This paper presents our findings on the automatic summarization of Java methods within Ericsson, a global telecommunications company. We evaluate the performance of an approach called Automatic Semantic Augmentation of Prompts (ASAP), which uses a Large Language Model (LLM) to generate leading summary comments for Java methods. ASAP enhances the $LLM's$ prompt context by integrating static program analysis and information retrieval techniques to identify similar exemplar methods along with their developer-written Javadocs, and serves as the baseline in our study. In contrast, we explore and compare the performance of four simpler approaches that do not require static program analysis, information retrieval, or the presence of exemplars as in the ASAP method. Our methods rely solely on the Java method body as input, making them lightweight and more suitable for rapid deployment in commercial software development environments. We conducted experiments on an Ericsson software project and replicated the study using two widely-used open-source Java projects, Guava and Elasticsearch, to ensure the reliability of our results. Performance was measured across eight metrics that capture various aspects of similarity. Notably, one of our simpler approaches performed as well as or better than the ASAP method on both the Ericsson project and the open-source projects. Additionally, we performed an ablation study to examine the impact of method names on Javadoc summary generation across our four proposed approaches and the ASAP method. By masking the method names and observing the generated summaries, we found that our approaches were statistically significantly less influenced by the absence of method names compared to the baseline. This suggests that our methods are more robust to variations in method names and may derive summaries more comprehensively from the method body than the ASAP approach. - 16 March 2024
- Published by Elsevier in Information and Software Technology
- Vol. 170
Source code expert identification: Models and application
- 16 March 2024
- Published by Elsevier in Information and Software Technology
- Vol. 170
Source code expert identification: Models and application
- Open Access
- 25 September 2023
- Published by Association for Computing Machinery (ACM)
- p. 196-205
Architectural Technical Debt - A Systematic Mapping Study
- 25 September 2023
- Published by Association for Computing Machinery (ACM)
- p. 196-205
Open AccessArchitectural Technical Debt - A Systematic Mapping Study
- 31 August 2023
- Published by Springer Nature in Empirical Software Engineering
- Vol. 28 (5) , 1-52
Tag that issue: applying API-domain labels in issue tracking systems
- 31 August 2023
- Published by Springer Nature in Empirical Software Engineering
- Vol. 28 (5) , 1-52
Tag that issue: applying API-domain labels in issue tracking systems