Proposed Framework to Manage Non-Functional Requirements in Agile
Résumé
Agile Software Development (ASD) is a type of iterated software development that strives to maximize productivity, effectiveness, and quick delivery through the minimization of documents and needless procedures within constrained timeframes. Agile software development has a number of advantages. There are still some difficulties. For instance, during the development lifecycle, non-functional requirements (NFRs) are disregarded and not given first-class artifacts. This results in several issues, including customer dissatisfaction and a great deal of rework, which impacts time and cost. In this paper, a proposed framework for handling non-functional requirements in Agile is explained. The framework supports the several primary activities of requirements engineering including requirements elicitation, analysis, documentation, and validation. In addition, the framework handles non-functional recommendations. Results of the suggested solution validation showed that it could address the problems with non-functional requirements in Agile.
Citer ce document
Exporter : BibTeX · RIS (Zotero, Mendeley, EndNote)
Accès au document
Texte intégral archivé sur SPHAERO, en accès ouvert : lisible gratuitement en ligne après connexion. Le document reste aussi disponible à sa source. Se connecter
Voir l'article sur le site de la revueLicence et provenance
Licence : CC BY
Notice moissonnée depuis OpenAlex le 10/09/2026. Le document reste hébergé par sa source.
Voir le document à la source →