Willian Oizumi

Willian Oizumi

Auto-generated profile, based on publicly available information

Willian Oizumi

PUC-Rio

Research Focus & Metrics

Academic Career Length

15Years (2012-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
14 May 2016
Verified
Conference Paper
Open access
WOWillian Oizumi
Willian Oizumi
AGAlessandro Garcia
Alessandro Garcia
LSLeonardo da Silva Sousa
Leonardo da Silva Sousa
BCBruno Cafeo
Bruno Cafeo
YZYixue Zhao
Yixue Zhao
Design problems affect every software system. Diverse software systems have been discontinued or reengineered due to design problems. As design documentation is often informal or nonexistent, design problems need to be located in the source code. The main difficulty to identify a design problem in the implementation stems from the fact that such problem is often scattered through several program elements. Previous work assumed that code anomalies -- popularly known as code smells -- may provide sufficient hints about the location of a design problem. However, each code anomaly alone may represent only a partial embodiment of a design problem. In this paper, we hypothesize that code anomalies tend to "flock together" to realize a design problem. We analyze to what extent groups of inter-related code anomalies, named agglomerations, suffice to locate design problems. We analyze more than 2200 agglomerations found in seven software systems of different sizes and from different domains. Our analysis indicates that certain forms of agglomerations are consistent indicators of both congenital and evolutionary design problems, with accuracy often higher than 80%.

1 November 2015
Verified
Conference Paper
Closed access
SVSantiago Vidal
Santiago Vidal
HVHernan Vazquez
Hernan Vazquez
JDJ. Andres Diaz-Pace
J. Andres Diaz-Pace
CMClaudia Marcos
Claudia Marcos
AGAlessandro Garcia
Alessandro Garcia
WOWillian Oizumi
Willian Oizumi
Code smells are a popular mechanism to identify structural design problems in software systems. Since it is generally not feasible to fix all the smells arising in the code, some of them are often postponed by developers to be resolved in the future. One reason for this decision is that the improvement of the code structure, to achieve modifability goals, requires extra effort from developers. Therefore, they might not always spend this additional effort, particularly when they are focused on delivering customer-visible features. This postponement of code smells are seen as a source of technical debt. Furthermore, not all the code smells may be urgent to fix in the context of the system's modifability and business goals. While there are a number of tools to detect smells, they do not allow developers to discover the most urgent smells according to their goals. In this article, we present a fexible tool to prioritize technical debt in the form of code smells. The tool is flexible to allow developer s to add new smell detection strategies and to prioritize smells, and groups of smells, based on the confguration of their manifold criteria. To illustrate this flexibility, we present an application example of our tool. The results suggest that our tool can be easily extended to be aligned with the developer's goals.

1 October 2020 in Information and Software Technology
Verified
Journal Article
Closed access
EFEduardo Fernandes
Eduardo Fernandes
ACAlexander Chávez
Alexander Chávez
AGAlessandro Garcia
Alessandro Garcia
IFIsabella Ferreira
Isabella Ferreira
DCDiego Cedrim
Diego Cedrim
WOWillian Oizumi
Willian Oizumi

10 July 2015 in Journal of Software Engineering Research and Development
Verified
Journal Article
Open access
PDF file
WOWillian N. Oizumi
Willian N. Oizumi
AGAlessandro F. Garcia
Alessandro F. Garcia
TCThelma E. Colanzi
Thelma E. Colanzi
MFManuele Ferreira
Manuele Ferreira
ASArndt V. Staa
Arndt V. Staa
Several projects have been discontinued in the history of the software industry due to the presence of software architecture problems. The identification of such problems in source code is often required in real project settings, but it is a time-consuming and challenging task. Some authors assume that architectural problems are reflected in source code through individual code anomalies. However, each architectural problem may be realized by multiple code anomalies, which are intertwined in several program elements. The relationships of these various code anomalies and their architecture problems’ counterparts are hard to reveal and characterize. To overcome this limitation, we are studying the architecture impact of a wide range of code-anomaly agglomerations. An agglomeration is a group of code anomalies that are explicitly related to each other in the implementation – e.g. two or more anomalies affecting the same class or method in the program. In our empirical study, we analyzed a total of 5418 code anomalies and 2229 agglomerations within 7 systems. In particular, our analysis focused in understanding (i) how agglomerations and architectural problems relate to each other, and (ii) how agglomerations can support the diagnosis of well-known architectural problems. We observed that most of the anomalous code elements related to architectural problems are members of one or more agglomerations. In addition, this study revealed that, for each agglomeration related to an architectural problem, an average of 2 to 4 anomalous code elements contribute to the architectural problem. Finally, the result of our study suggests that certain types of agglomerations are better indicators of architectural problems than others.

27 May 2018
Verified
Conference Paper
Open access
PDF file
LSLeonardo Sousa
Leonardo Sousa
AOAnderson Oliveira
Anderson Oliveira
WOWillian Oizumi
Willian Oizumi
SBSimone Barbosa
Simone Barbosa
AGAlessandro Garcia
Alessandro Garcia
RPRodrigo Paes
Rodrigo Paes

15 September 2014
Verified
Conference Paper
Open access
TCThelma Elita Colanzi
Thelma Elita Colanzi
SVSilvia Regina Vergilio
Silvia Regina Vergilio
IGItana M. S. Gimenes
Itana M. S. Gimenes
WOWillian Nalepa Oizumi
Willian Nalepa Oizumi
The Product Line Architecture (PLA) can be improved by taking into account key factors such as feature modularization, and by continuously evaluating its design according to metrics. Search-Based Software Engineering (SBSE) principles can be used to support an informed-design of PLAs. However, existing search-based design works address only traditional software design not considering intrinsic Software Product Line aspects. This paper presents MOA4PLA, a search-based approach to support the PLA design. It gives a multi-objective treatment to the design problem based on specific PLA metrics. A metamodel to represent the PLA and a novel search operator to improve feature modularization are proposed. Results point out that the application of MOA4PLA leads to PLA designs with well modularized features, contributing to improve features reusability and extensibility. It raises a set of solutions with different design trade-offs that can be used to improve the PLA design.