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.
Managing non-functional requirements (NFRs) is complex and has been challenging over the years. These requirements are typically used to make important architectural decisions early in the project, which can be a problem if they are uncertain or volatile. Identifying and demonstrating the existence of anti-patterns associated with the negligence and volatility of NFRs is a topic that deserves attention. This study identified five anti-patterns associated with managing NFRs and the volatility of these requirements. Based on a survey applied to 40 professionals with more than 10 years of experience, data were obtained from 144 NFRs of real projects, and important dysfunctions were identified. The mapped anti-patterns describe dysfunctions associated with: incorrect perception of needs (FALSE CERTAINTY); delayed elicitation of NFRs (LATE IDENTIFICATION); immutable NFRs (FROZEN NFR); projects that include all NFRs without validation of feasibility and impacts (FULL PACKAGE); and equal management for all NFRs (INVARIANT MANAGEMENT).