Eduardo Guerra

Eduardo Guerra

Auto-generated profile, based on publicly available information

Eduardo Guerra

Free University of Bozen-Bolzano

Research Focus & Metrics

Academic Career Length

20Years (2007-Present)

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

Representative Publications

View All Publications
1 August 2007
Verified
Conference Paper
Closed access
EGEduardo Martins Guerra
Eduardo Martins Guerra
CFClovis Torres Fernandes
Clovis Torres Fernandes
Test driven development is a technique in which the refactoring occurs all the time, in the application code and in the test code. But there is not a method to guarantee that the test code behavior after one refactoring remains unchanged. This paper presents a representation based on the JUnit unit test structure, as well as a classification of test code refactorings that may ease the analysis to verify if the test code refactoring was carried out safely, i.e., if the observable behavior of the refactored test code has been kept unchanged. The use of this proposed technique may safely improve and speed up the production of test code refactorings.

28 August 2009
Verified
Conference Paper
Open access
PDF file
EGEduardo M. Guerra
Eduardo M. Guerra
JSJerffeson T. de Souza
Jerffeson T. de Souza
CFClovis T. Fernandes
Clovis T. Fernandes
Metadata-based frameworks are those that process their logic based on the metadata of the classes whose instances they are working with. Many recent frameworks use this to get a higher reuse level and to be more suitably adapted to the application needs. However, there is not yet a complete best practices documentation or reference architecture for the development of frameworks by using the metadata approach. As a result, this paper presents a pattern language that addresses preliminarily the internal structure of metadata-based frameworks, helping in the understanding and development of such kind of framework.

1 March 2018 in Journal of Systems and Software
Verified
Journal Article
Closed access
PLPhyllipe Lima
Phyllipe Lima
EGEduardo Guerra
Eduardo Guerra
PMPaulo Meirelles
Paulo Meirelles
LKLucas Kanashiro
Lucas Kanashiro
HSHélio Silva
Hélio Silva
FSFabio Fagundes Silveira
Fabio Fagundes Silveira

1 May 2013 in Journal of Systems and Software
Verified
Journal Article
Closed access
EGEduardo Guerra
Eduardo Guerra
FAFelipe Alves
Felipe Alves
UKUirá Kulesza
Uirá Kulesza
CFClovis Fernandes
Clovis Fernandes

1 January 2016
Verified
Book Chapter
Closed access
EGEduardo Guerra
Eduardo Guerra
MAMaurício Aniche
Maurício Aniche

20 May 2023
Verified
Book Chapter
Open access
PDF file
LVLuiz Viviani
Luiz Viviani
EGEduardo Guerra
Eduardo Guerra
JMJorge Melegati
Jorge Melegati
XWXiaofeng Wang
Xiaofeng Wang
Managing non-functional requirements (NFRs) has been a challenge in software development for many years. These requirements are typically used to make important architectural decisions early in the project, which can be problematic if they are uncertain or unstable. When this uncertainty is not considered when designing the software architecture, changes are often costly and sometimes even unfeasible. Some empirical studies on the subject have already been carried out, but few have focused on the perspective of professionals with extensive experience on the changes and uncertainties of NFRs. This work aims to expand the understanding about the management, clarity and validation of NFRs to fill this gap in the literature. To achieve this goal, a survey was carried out with professionals to find out how NFRs were managed and validated. For the research design, instead of generic questions, the questionnaire focused on some specific types of NFRs to induce participants to recall and report concrete situations. As a result, 40 valid responses were obtained, most from professionals with more than 10 years of experience. The results reveal that a significant number of NFRs were defined after the delivery of software increments (more than 30%) and that revision and change occurred in about a third of the NFRs. Hence, this study presents evidence that NFRs, as the functional ones, can also be uncertain and change frequently, requiring agile approaches and techniques to evolve the software architecture to consider this uncertainty.