Author of the publication

Please choose a person to relate this publication to

To differ between persons with the same name, the academic degree and the title of an important publication will be displayed. You can also use the button next to the name to display some publications already assigned to the person.

 

Other publications of authors with the same name

Revealing Developers' Arguments on Validating the Incidence of Code Smells: A Focus Group Experience., , , , , and . VEM, page 31-35. Sociedade Brasileira de Computação, (2021)Understanding the impact of refactoring on smells: a longitudinal study of 23 software projects., , , , , , , , and . ESEC/SIGSOFT FSE, page 465-475. ACM, (2017)Towards Effective Teams for the Identification of Code Smells., , , and . CHASE@ICSE, page 62-65. IEEE Computer Society, (2017)Tracking Dengue Epidemics Using Twitter Content Classification and Topic Modelling., , , , , , , and . ICWE Workshops, volume 9881 of Lecture Notes in Computer Science, page 80-92. (2016)No Code Anomaly is an Island - Anomaly Agglomeration as Sign of Product Line Instabilities., , , , , and . ICSR, volume 10221 of Lecture Notes in Computer Science, page 48-64. (2017)How Do Software Developers Identify Design Problems?: A Qualitative Analysis., , , , , , , , , and 1 other author(s). SBES, page 54-63. ACM, (2017)Evolução de software livre baseada em métricas de qualidade: Um estudo de caso., , , , , , and . SBSI, page 815-826. (2013)Code anomalies flock together: exploring code anomaly agglomerations for locating design problems., , , , and . ICSE, page 440-451. ACM, (2016)Collaborative Identification of Code Smells: A Multi-Case Study., , , , , , , , and . ICSE-SEIP, page 33-42. IEEE Computer Society, (2017)Spotting design problems with smell agglomerations.. ICSE (Companion Volume), page 863-866. ACM, (2016)