design problems

ReSoM: Restructuring Software in Multi-language

Research Project, 2015 – 2016. In cooperation with University of Southern California (EUA), and University of California at Irvine (EUA)

ACM SIGSOFT Distinguished Paper Award

International Conference on Software Engineering (ICSE 2018) May 27 - June 3, 2018, Gothenburg, Sweden

Identifying Design Problems in the Source Code: A Grounded Theory

The prevalence of design problems may cause re-engineering or even discontinuation of the system. Due to missing, informal or outdated design documentation, developers often have to rely on the source code to identify design problems. Therefore, …

On the Identification of Design Problems in Stinky Code: Experiences and Tool Support

Background: Developers often have to locate design problems in the source code. Several types of design problems may manifest as code smells in the program. A code smell is a source code structure that may reveal a partial hint about the …

How Do Software Developers Identify Design Problems?: A Qualitative Analysis

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 …

Distinguished Paper Award

Proceedings of the 11th Brazilian Symposium on Software Components, Architectures, and Reuse (SBCARS '17), Sep 18-22, 2017, Fortaleza, Ceará, Brazil

Revealing design problems in stinky code: a mixed-method study

Developers often have to locate design problems in the source code. Several types of design problem may manifest as code smells in the program. A code smell is a source code structure that may reveal a partial hint about the manifestation of a design …