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