Cookies Policy
The website need some cookies and similar means to function. If you permit us, we will use those means to collect data on your visits for aggregated statistics to improve our service. Find out More
Accept Reject
  • Menu
Publications

Publications by Jorge Melegati

2022

A Framework Model to Support A/B Tests at the Class and Component Level

Authors
De Souza, WS; Oliveira Pereira, Fd; Albuquerque, VG; Melegati, J; Guerra, E;

Publication
COMPSAC

Abstract

2022

XPro: A Model to Explain the Limited Adoption and Implementation of Experimentation in Software Startups

Authors
Melegati, J; Edison, H; Wang, X;

Publication
IEEE Trans. Software Eng.

Abstract

2022

HyMap: Eliciting hypotheses in early-stage software startups using cognitive mapping

Authors
Melegati, J; Guerra, E; Wang, X;

Publication
Inf. Softw. Technol.

Abstract

2023

DAnTE: a taxonomy for the automation degree of software engineering tasks

Authors
Melegati, J; Guerra, E;

Publication
CoRR

Abstract

2023

An Empirical Study About the Instability and Uncertainty of Non-functional Requirements

Authors
Viviani, L; Guerra, E; Melegati, J; Wang, X;

Publication
XP

Abstract
AbstractManaging 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.

2023

An Exploratory Study About Non-functional Requirements Documentation Practices in Agile Teams

Authors
Nasir, S; Guerra, E; Zaina, LAM; Melegati, J;

Publication
SAC

Abstract

  • 6
  • 11