EOEdson Oliveira

Edson Oliveira

*This is an algorithmically generated author record based on publicly available information.

Edson Oliveira has a total of 37 co-authors. Here are the top co-authors by number of shared publications:


Latest Publications

  • Open Access

    Applying design thinking in research and development environment: Insights from a case study in a Brazilian R&D institute

    by Maria Alcimar Costa Meireles, Eriky Rodrigues, Luana Lobão, Edson Oliveira, Igor Steinmacher, José Carlos Maldonado, Tayana Conte


  • Open Access

    Applying Design Thinking in Research and Development Environment: Insights from a Case Study in a Brazilian R&D Institute

    by Maria Alcimar Meireles, Eriky Souza, Luana Lobao, Edson Oliveira, Igor Steinmacher, José Carlos Maldonado, Tayana Conte

    Context: Research and Development (R&D) organizations drives technological innovation and deliver customized software solutions. These environments face complex challenges in aligning technical development with user needs. Design Thinking (DT) stands out as an innovative approach in software development, fostering a deeper understanding of user needs and enabling the creation of more effective solutions. However, its implementation within R&D contexts poses challenges that remain underexplored in the literature. Objective: Explore how DT is integrated into software development processes within an R&D organization, focusing on uncovering benefits, challenges, and actionable recommendations. Method: We conducted a case study at Instituto de Desenvolvimento Tecnologico (INDT), a Brazilian R&D organization with a background in innovation-oriented software projects. We conducted semi-structured interviews with 16 practitioners who interacted within DT at INDT. We adopted Grounded Theory procedures, enabling a qualitative analysis of participants’ perceptions of DT use. Results: Adopting DT enhances the understanding of user needs, promotes effective collaboration between teams and clients, and results in solutions aligned with market expectations. Cultural resistance and lack of proficiency in DT techniques stand out as challenges. As recommendations for implementing DT, practitioners suggested adapting DT to the organization’s reality, incorporating the DT mindset among other practitioners, having people well-versed in DT to drive its use, mapping the project process, and aligning DT within the development process. Conclusion: DT emerges as a relevant approach for software development in R&D environments, capable of generating innovative, market-aligned solutions. Our findings reinforce DT potential to contribute to software development processes within R&D organizations.

  • Open Access

    UX-MAPPER: An automated approach to analyze app store reviews with a focus on UX

    by Walter T. Nakamura, Edson C. C. de Oliveira, Elaine H. T. de Oliveira, Tayana Conte

    The mobile app market has increased substantially in the past decades, and the myriad options in the app stores have made users less tolerant of low-quality apps. In this competitive scenario, User eXperience (UX) has emerged as an essential factor in standing out from competitors. By understanding what factors affect UX, practitioners could focus on factors that lead to positive UX while mitigating those that affect UX negatively. In this context, app store reviews emerged as a valuable resource for investigating these influential factors. However, analyzing millions of reviews can be costly and time-consuming. This article introduces UX-MAPPER, a tool designed to analyze app store reviews and assist practitioners in pinpointing factors that impact UX. We applied the Design Science Research method to develop UX-MAPPER iteratively and rooted in a robust theoretical background. We performed exploratory studies to investigate the problem, a systematic mapping study to identify UX-affecting factors, and an empirical study to ascertain practitioners’ relevance and acceptance of UX-MAPPER. In general, the participants recognized the relevance and utility of UX-MAPPER in enhancing the quality of existing apps and exploring reviews of competing apps to identify user preferences, requests, and critiques regarding functionalities and features. However, the output quality requires refinement to better convey the benefits of the results, especially for practitioners with prior experience with automated approaches. From the participants’ feedback, we defined a set of suggestions to extract more useful features, which can contribute to future studies involving user review analysis. Based on the results of this research, we present the contributions to the area of HCI and possible developments for future research.


  • Open Access

    UX-MAPPER: A User eXperience Method to Analyze App Store Reviews

    by Walter T. Nakamura, Edson César C. de Oliveira, Elaine H. T. de Oliveira, Tayana Conte

    The mobile app market has grown over the last decades. With the rise of app stores, users can easily choose an app from thousands, making them less tolerant of low-quality apps. More than ever, users are looking for apps that provide not only valuable functionalities but pleasurable experiences. Hence, User eXperience (UX) became the differential to stand out from competitors. By understanding what factors affect UX, practitioners could focus on factors that lead to positive UX while mitigating those that affect UX negatively. In this context, reviews from app stores emerged as a valuable source of information to investigate such factors. However, analyzing millions of reviews is costly and time-consuming. This paper presents UX-MAPPER, an approach to analyzing app store reviews and supporting practitioners in identifying factors affecting UX. We applied the Design Science Research method to design UX-MAPPER iteratively and grounded on a solid theoretical background. We performed exploratory studies to investigate the problem, a systematic mapping study to identify factors that affect UX, and an empirical study with 14 participants with experience in requirements engineering to determine the relevance and acceptance of our proposal from practitioners’ perspectives. The participants considered it useful to improve the quality of existing apps and explore the reviews of competing apps to identify functionalities and features that users are requesting, liking, or hating. They were also willing to use it when it became available, highlighting our proposal’s usefulness and relevance in software development.


  • Open Access

    Joy to the Work: How Does Software Team Formation Strategy Influence Job Satisfaction?

    by Sergio Ricardo De Oliveira Cavalcante, Bruno Gadelha, Edson Oliveira, Igor Steinmacher, Walter Nakamura, Tayana Conte


  • Code and commit metrics of developer productivity: a study on team leaders perceptions

    by Edson Oliveira, Eduardo Fernandes, Igor Steinmacher, Marco Cristo, Tayana Conte, Alessandro Garcia


  • Directives of Communicability: Teaching Students How to Improve Communication Through Software Modeling

    by Adriana Lopes, Edson Oliveira, Tayana Conte, Clarisse Sieckenius de Souza

    In the development process, software models are used to support communication among development team members. Failures of communication that is mediated by software models may generate inconsistencies in software behavior, generating rework to correct them. This may occur because producers usually focus only on model content, although they should also reflect on how other members of the development team will interpret their models. We should therefore teach software engineering students how to communicate better through software models. In an attempt to improve communication through software models, we have developed the Directives of Communicability (DCs), based on theories that investigate different kinds of communication. In this poster, we present the highlights of a study to find out whether DCs improve software engineering students' communication through software models. Our results confirm that DCs have improved the students' reflections on how their models' content will be interpreted during the software development process.


  • Influence Factors in Software Productivity — A Tertiary Literature Review

    by Edson Oliveira, Tayana Conte, Marco Cristo, Natasha Valentim

    Software organizations need to increase their productivity to stay competitive. Although there is a lot of research on productivity in software development, software organizations still do not know what are the most significant productivity factors in which they should invest. This paper presents a Tertiary Literature Review (TLR) that aims to identify and analyze Systematic Literature Reviews (SLR) on the influence factors of software productivity reported in the scientific literature. We extracted and classified the influence factors into organizational factors (organizational-dependent factors) and human factors (people-dependent factors). The relevance of the factors was extracted according to the amount of references found in the secondary studies. Using this information, software organizations can improve the productivity of their projects by evaluating the influence factors that best fit their context.


  • Open Access

    How Do Software Developers Identify Design Problems?

    by Leonardo Sousa, Roberto Oliveira, Alessandro Garcia, Jaejoon Lee, Tayana Conte, Willian Oizumi, Rafael de Mello, Adriana Lopes, Natasha Valentim, Edson Oliveira, et al.

    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


  • Collaborative Identification of Code Smells: A Multi-Case Study

    by Roberto Oliveira, Leonardo Sousa, Rafael de Mello, Natasha Valentim, Adriana Lopes, Tayana Conte, Alessandro Garcia, Edson Oliveira, 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.