Towards Optimal Non-functional Requirements Elicitation and Documentation in Agile Software Development: A Case Study

In agile software development, non-functional requirements are often underspecified and improperly handled due to the focus on rapidly delivering functionality. Neglecting NFRs in early phases of development may compromise software quality and customer satisfaction. In our previous paper, we introduced a guideline for handling non-functional requirements in Agile. This guideline was evaluated in a case study, revealing that improved identification of non-functional requirements led to enhanced development stability and client communication, without losing agility in the process. In this paper, we propose an extension of the guideline aimed at improving the documentation of each stage and incorporating a NFR testing phase.