Proposed Framework to Manage Non-Functional Requirements in Agile

13Citations
Citations of this article
93Readers
Mendeley users who have this article in their library.

This article is free to access.

Abstract

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.

Cite

CITATION STYLE

APA

Sherif, E., Helmy, W., & Galal-Edeen, G. H. (2023). Proposed Framework to Manage Non-Functional Requirements in Agile. IEEE Access, 11, 53995–54005. https://doi.org/10.1109/ACCESS.2023.3281195

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free