Edson Oliveira

Edson Oliveira

Auto-generated profile, based on publicly available information

Edson Oliveira

Amazonas State Treasury Department (SEFAZ/AM)

Research Focus & Metrics

Academic Career Length

12Years (2015-Present)

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

Representative Publications

View All Publications
1 July 2015
Verified
Conference Paper
Closed access
BFBruna Ferreira
Bruna Ferreira
WSWilliamson Silva
Williamson Silva
EOEdson Oliveira
Edson Oliveira
TCTayana Conte
Tayana Conte

13 April 2020 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
EOEdson Oliveira
Edson Oliveira
EFEduardo Fernandes
Eduardo Fernandes
ISIgor Steinmacher
Igor Steinmacher
MCMarco Cristo
Marco Cristo
TCTayana Conte
Tayana Conte
AGAlessandro Garcia
Alessandro Garcia

1 November 2018 in International Journal of Software Engineering and Knowledge Engineering
Verified
Journal Article
Closed access
PDF file
EOEdson Oliveira
Edson Oliveira
TCTayana Conte
Tayana Conte
MCMarco Cristo
Marco Cristo
NVNatasha Valentim
Natasha Valentim

8 September 2016
Verified
Conference Paper
Open access
PDF file
EOEdson Oliveira
Edson Oliveira
TCTayana Conte
Tayana Conte
MCMarco Cristo
Marco Cristo
EMEmilia Mendes
Emilia Mendes
Context -- Developers' productivity plays an important role in software development organizations; however, in many cases the management of such human capital is mainly based on how project managers perceive productivity. Therefore, it is important to investigate what these perceptions are in practice. Goal -- This study's main goal is to understand project managers' perception regarding developers' productivity. Method -- We employed a qualitative research methodology using semi-structured interviews for data collection. We interviewed 12 managers from three software development organizations in the city of Manaus (Brazil). Results -- We identified that the managers' perceptions about developers' productivity are influenced by four different factors: (1) tasks delivered on time, (2) produced artifacts that do not need rework, (3) products that meet stakeholders' expectations, and (4) personal behavior such as focus and proactivity. Conclusions -- This qualitative study shows a perception of developers' productivity different from that presented in other research papers, and suggests that human factors play an important role in managers' perceptions about productivity. Future work will investigate how these perceptions concretely influence developers' productivity, and how they relate to the existing developers' productivity factors in the literature.

20 September 2017
Verified
Conference Paper
Open access
LSLeonardo Sousa
Leonardo Sousa
RORoberto Oliveira
Roberto Oliveira
AGAlessandro Garcia
Alessandro Garcia
JLJaejoon Lee
Jaejoon Lee
TCTayana Conte
Tayana Conte
CLCarlos Lucena
Carlos Lucena
When a software design decision has a negative impact on one or more quality attributes, we call it a design problem. For example, the Fat Interface problem indicates that an interface exposes non-cohesive services Thus, clients and implementations of this interface may have to handle with services that they are not interested. A design problem such as this hampers the extensibility and maintainability of a software system. As illustrated by the example, a single design problem often affects several elements in the program. Despite its harmfulness, it is difficult to identify a design problem in a system. It is even more challenging to identify design problems when the source code is the only available artifact. In particular, no study has observed what strategy(ies) developers use in practice to identify design problems when the design documentation is unavailable. In order to address this gap, we conducted a qualitative analysis on how developers identify design problems in two different scenarios: when they are either familiar (Scenario 1) or unfamiliar (Scenario 2) with the analyzed systems. Developers familiar with the systems applied a diverse set of strategies during the identification of each design problem. Some strategies were frequently used to locate code elements for analysis, and other strategies were frequently used to confirm design problems in these elements. Developers unfamiliar with the systems relied only on the use of code smells along the task. Despite some differences among the subjects from both scenarios, we noticed that developers often search for multiple indicators during the identification of each design problem

1 May 2017
Verified
Conference Paper
Closed access
RORoberto Oliveira
Roberto Oliveira
LSLeonardo Sousa
Leonardo Sousa
RMRafael de Mello
Rafael de Mello
NVNatasha Valentim
Natasha Valentim
ALAdriana Lopes
Adriana Lopes
CLCarlos Lucena
Carlos Lucena
Code smells are anomalous program structures that may indicate software maintainability problems. God Classes and Feature Envies are examples of code smells that frequently become the target of software refactoring. However, smell identification might be harder than expected due to the subjectivity involved in the recognition of the apparently simple structure of each smell. Moreover, smell identification might require the knowledge of multiple program elements, which are better understood by different developers. Thus, the use of collaboration among developers may have the potential to improve effectiveness on smell identification. However, current knowledge, especially empirically developed and evaluated in the industry, is quite scarce. This paper reports an industrial case study aimed at observing how 13 developers individually and collaboratively performed smell identification in five software projects from two software development organizations. Our results suggest that collaboration contributes to improving effectiveness on the identification of a wide range of code smells. We also analyzed the factors contributing to such effectiveness improvement.