Willian Oizumi
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Previous Organizations / Institutes
The organizations / institutes from the scholar's other articles in the past ten years
Research Subjects
Willian Oizumi has a total of 65 co-authors. Here are the top co-authors by number of shared publications:
Alessandro Garcia
14 shared publicationsRoberto Oliveira
8 shared publicationsLeonardo Sousa
PUC-Rio
7 shared publicationsAnderson Oliveira
PUC-Rio
6 shared publications- Alessandro Garcia
Pontifical Catholic University of Rio de Janeiro, Rio de Janeiro, Brazil
5 shared publications Carlos Lucena
Opus Research Group, Informatics Department, PUC-Rio, Rio de Janeiro, RJ, Brazil
4 shared publications
Latest Publications
- 27 September 2022
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Software
- Vol. 40 (2) , 90-98
Recommendations for Developers Identifying Code Smells
The outcomes of this work provide a comprehensive view of the task and emerging findings, such as the developers’ major beliefs, values, and ideas about identifying code smells. Based on these outcomes, we present practical recommendations to developers to optimize efforts in identifying code smells.
- 27 September 2022
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Software
- Vol. 40 (2) , 90-98
Recommendations for Developers Identifying Code Smells
The outcomes of this work provide a comprehensive view of the task and emerging findings, such as the developers’ major beliefs, values, and ideas about identifying code smells. Based on these outcomes, we present practical recommendations to developers to optimize efforts in identifying code smells.
- Open Access
- 4 April 2022
- Published by Sociedade Brasileira de Computação in Journal of Software Engineering Research and Development
- Vol. 10, 6:1-6:23
OPLA-Tool-ASP: a Tool to Prevent Architectural Smells in Search-based Product Line Architecture Design
Search-based algorithms have been successfully employed in Product Line Architecture (PLA) design in the seminal approach named Multi-Objective Approach for Product-Line Architecture Design (MOA4PLA). This approach generates a set of alternative PLA designs, which optimize different architectural properties. In addition to these properties, the alternative PLA designs should have as few architectural smells as possible. Architectural smells can negatively impact PLA variability, PLA extensibility, SPL maintainability, and other non-functional attributes. However, one of the main findings of a previous study is that the tool that automates the application of MOA4PLA adversely introduces architectural smells in the automatically generated solutions. In this work, we present OPLA-Tool-ASP, which is a tool that implements guidelines to detect and prevent the architectural smells Unused Interface, Unused Brick, Concern Overload, and Link Overload in the context of MOA4PLA. An empirical study was carried out to assess the effectiveness of OPLA-Tool-ASP in preventing the aforementioned smells in the resulting PLA designs. The obtained results pointed out that the proposed tool is effective in both preventing the smells and improving the architectural properties selected for optimization.
- 4 April 2022
- Published by Sociedade Brasileira de Computação in Journal of Software Engineering Research and Development
- Vol. 10, 6:1-6:23
Open AccessOPLA-Tool-ASP: a Tool to Prevent Architectural Smells in Search-based Product Line Architecture Design
Search-based algorithms have been successfully employed in Product Line Architecture (PLA) design in the seminal approach named Multi-Objective Approach for Product-Line Architecture Design (MOA4PLA). This approach generates a set of alternative PLA designs, which optimize different architectural properties. In addition to these properties, the alternative PLA designs should have as few architectural smells as possible. Architectural smells can negatively impact PLA variability, PLA extensibility, SPL maintainability, and other non-functional attributes. However, one of the main findings of a previous study is that the tool that automates the application of MOA4PLA adversely introduces architectural smells in the automatically generated solutions. In this work, we present OPLA-Tool-ASP, which is a tool that implements guidelines to detect and prevent the architectural smells Unused Interface, Unused Brick, Concern Overload, and Link Overload in the context of MOA4PLA. An empirical study was carried out to assess the effectiveness of OPLA-Tool-ASP in preventing the aforementioned smells in the resulting PLA designs. The obtained results pointed out that the proposed tool is effective in both preventing the smells and improving the architectural properties selected for optimization.
- 1 October 2020
- Published by Elsevier in Information and Software Technology
- Vol. 126
Refactoring effect on internal quality attributes: What haven’t they told you yet?
- 1 October 2020
- Published by Elsevier in Information and Software Technology
- Vol. 126
Refactoring effect on internal quality attributes: What haven’t they told you yet?
- 1 October 2019
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 89-92
Recommendation of Refactorings for Improving Dependability Attributes
The incidence of design problems (DP) in systems is associated with the quality decay of dependability attributes such as maintainability and robustness. This often results in negative consequences such as rework and error proneness. Thus, there are many techniques for supporting the resolution of DPs through refactoring recommendations. However, in practice, deciding where and when to refactor is still a challenging task. In addition, existing techniques fail to provide effective support. Thus, we aim at advancing the state-of-the-art through a flexible refactoring recommendation technique. Our technique is intended to help practitioners in improving multiple dependability attributes. We hypothesize that our recommendation technique will be able to overcome existing limitations by using empirically validated heuristics. Our heuristics will use information such as the density, diversity, and granularity of symptoms to recommend refactoring opportunities. The effectiveness of our technique will be evaluated through empirical studies involving heterogeneous software projects and experienced software practitioners.
- 1 October 2019
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 89-92
Recommendation of Refactorings for Improving Dependability Attributes
The incidence of design problems (DP) in systems is associated with the quality decay of dependability attributes such as maintainability and robustness. This often results in negative consequences such as rework and error proneness. Thus, there are many techniques for supporting the resolution of DPs through refactoring recommendations. However, in practice, deciding where and when to refactor is still a challenging task. In addition, existing techniques fail to provide effective support. Thus, we aim at advancing the state-of-the-art through a flexible refactoring recommendation technique. Our technique is intended to help practitioners in improving multiple dependability attributes. We hypothesize that our recommendation technique will be able to overcome existing limitations by using empirically validated heuristics. Our heuristics will use information such as the density, diversity, and granularity of symptoms to recommend refactoring opportunities. The effectiveness of our technique will be evaluated through empirical studies involving heterogeneous software projects and experienced software practitioners.
- 1 October 2019
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 346-357
On the Density and Diversity of Degradation Symptoms in Refactored Classes: A Multi-case Study
Root canal refactoring is a software development activity that is intended to improve dependability-related attributes such as modifiability and reusability. Despite being an activity that contributes to these attributes, deciding when applying root canal refactoring is far from trivial. In fact, finding which elements should be refactored is not a cut-and-dried task. One of the main reasons is the lack of consensus on which characteristics indicate the presence of structural degradation. Thus, we evaluated whether the density and diversity of multiple automatically detected symptoms can be used as consistent indicators of the need for root canal refactoring. To achieve our goal, we conducted a multi-case exploratory study involving 6 open source systems and 2 systems from our industry partners. For each system, we identified the classes that were changed through one or more root canal refactorings. After that, we compared refactored and non-refactored classes with respect to the density and diversity of degradation symptoms. We also investigated if the most recurrent combinations of symptoms in refactored classes can be used as strong indicators of structural degradation. Our results show that refactored classes usually present higher density and diversity of symptoms than non-refactored classes. However, root canal refactorings that are performed by developers in practice may not be enough for reducing degradation, since the vast majority had little to no impact on the density and diversity of symptoms. Finally, we observed that symptom combinations in refactored classes are similar to the combinations in non-refactored classes. Based on our findings, we elicited an initial set of requirements for automatically recommending root canal refactorings.
- 1 October 2019
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 346-357
On the Density and Diversity of Degradation Symptoms in Refactored Classes: A Multi-case Study
Root canal refactoring is a software development activity that is intended to improve dependability-related attributes such as modifiability and reusability. Despite being an activity that contributes to these attributes, deciding when applying root canal refactoring is far from trivial. In fact, finding which elements should be refactored is not a cut-and-dried task. One of the main reasons is the lack of consensus on which characteristics indicate the presence of structural degradation. Thus, we evaluated whether the density and diversity of multiple automatically detected symptoms can be used as consistent indicators of the need for root canal refactoring. To achieve our goal, we conducted a multi-case exploratory study involving 6 open source systems and 2 systems from our industry partners. For each system, we identified the classes that were changed through one or more root canal refactorings. After that, we compared refactored and non-refactored classes with respect to the density and diversity of degradation symptoms. We also investigated if the most recurrent combinations of symptoms in refactored classes can be used as strong indicators of structural degradation. Our results show that refactored classes usually present higher density and diversity of symptoms than non-refactored classes. However, root canal refactorings that are performed by developers in practice may not be enough for reducing degradation, since the vast majority had little to no impact on the density and diversity of symptoms. Finally, we observed that symptom combinations in refactored classes are similar to the combinations in non-refactored classes. Based on our findings, we elicited an initial set of requirements for automatically recommending root canal refactorings.
- Open Access
- 23 September 2019
- Published by Association for Computing Machinery (ACM)
- p. 457-466
Investigating the Social Representations of the Identification of Code Smells by Practitioners and Students from Brazil
- 23 September 2019
- Published by Association for Computing Machinery (ACM)
- p. 457-466
Open AccessInvestigating the Social Representations of the Identification of Code Smells by Practitioners and Students from Brazil
- Open Access
- 23 September 2019
- Published by Association for Computing Machinery (ACM)
- p. 83-92
On the Prioritization of Design-Relevant Smelly Elements
- 23 September 2019
- Published by Association for Computing Machinery (ACM)
- p. 83-92
Open AccessOn the Prioritization of Design-Relevant Smelly Elements
- 1 September 2019
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 1-6
Do Research and Practice of Code Smell Identification Walk Together? A Social Representations Analysis
Context: It is frequently claimed the need for bridging the gap between software engineering research and practice. In this sense, the theory of social representations may be useful to characterize the actual concerns of software developers. It comprises the system of values, behaviors, and practices of communities regarding a particular social object, such as the task of smell identification. Aim: To characterize the social representations of smell identification by software developers. Method: Based on the answers given to a question-naire, we analyzed the associations made by the developers about smell identification, i.e., what immediately comes to their minds when they think about this task. Results: We found that developers strongly associate smell identification with the practice of smell removal and with the incidence of bugs. They also frequently associate the task with the practice of inspection and with the need of having individual skills. Besides, we verified that the current state of the art on smell identification partially address the social representations of the software developers. Conclusion: There is a considerable gap between the research of smell identification and its practice. We propose directions to mitigating this gap.
- 1 September 2019
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 1-6
Do Research and Practice of Code Smell Identification Walk Together? A Social Representations Analysis
Context: It is frequently claimed the need for bridging the gap between software engineering research and practice. In this sense, the theory of social representations may be useful to characterize the actual concerns of software developers. It comprises the system of values, behaviors, and practices of communities regarding a particular social object, such as the task of smell identification. Aim: To characterize the social representations of smell identification by software developers. Method: Based on the answers given to a question-naire, we analyzed the associations made by the developers about smell identification, i.e., what immediately comes to their minds when they think about this task. Results: We found that developers strongly associate smell identification with the practice of smell removal and with the incidence of bugs. They also frequently associate the task with the practice of inspection and with the need of having individual skills. Besides, we verified that the current state of the art on smell identification partially address the social representations of the software developers. Conclusion: There is a considerable gap between the research of smell identification and its practice. We propose directions to mitigating this gap.
- 1 August 2019
- Published by Elsevier in Science of Computer Programming
- Vol. 182, 64-85
Ranking architecturally critical agglomerations of code smells
- 1 August 2019
- Published by Elsevier in Science of Computer Programming
- Vol. 182, 64-85
Ranking architecturally critical agglomerations of code smells
- 1 May 2019
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 148-153
Removal of Design Problems through Refactorings: Are We Looking at the Right Symptoms?
A design problem is the result of design decisions that negatively impact quality attributes. For example, a stakeholder introduces a design problem when he decides to addresses multiple unrelated responsibilities in a single class, impacting the modifiability and reusability of the system. Given their negative consequences, design problems should be identified and refactored. The literature still lacks evidence on which symptoms' characteristics can be used as strong indicators of design problems. For example, it is unknown if the density and diversity of certain symptoms (e.g., violations of object-oriented principles) are correlated with the occurrence of design problems. Thus, in this paper, we report a case study involving two C# systems. We evaluated the impact of refactoring, focused on removing design problems, on the density and diversity of symptoms. Results indicate that refactored classes usually present higher density and diversity of symptoms. However, the density and diversity of some symptoms, such as the violation of object-oriented principles, was not predominantly higher in refactored classes. Moreover, contrary to our expectations, refactorings caused almost no positive impact on the density and diversity of symptoms.
- 1 May 2019
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 148-153
Removal of Design Problems through Refactorings: Are We Looking at the Right Symptoms?
A design problem is the result of design decisions that negatively impact quality attributes. For example, a stakeholder introduces a design problem when he decides to addresses multiple unrelated responsibilities in a single class, impacting the modifiability and reusability of the system. Given their negative consequences, design problems should be identified and refactored. The literature still lacks evidence on which symptoms' characteristics can be used as strong indicators of design problems. For example, it is unknown if the density and diversity of certain symptoms (e.g., violations of object-oriented principles) are correlated with the occurrence of design problems. Thus, in this paper, we report a case study involving two C# systems. We evaluated the impact of refactoring, focused on removing design problems, on the density and diversity of symptoms. Results indicate that refactored classes usually present higher density and diversity of symptoms. However, the density and diversity of some symptoms, such as the violation of object-oriented principles, was not predominantly higher in refactored classes. Moreover, contrary to our expectations, refactorings caused almost no positive impact on the density and diversity of symptoms.