Proposed Framework to Manage Non-Functional Requirements in Agile
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. The...
Gespeichert in:
Veröffentlicht in: | IEEE access 2023, Vol.11, p.53995-54005 |
---|---|
Hauptverfasser: | , , |
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Zusammenfassung: | 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. |
---|---|
ISSN: | 2169-3536 2169-3536 |
DOI: | 10.1109/ACCESS.2023.3281195 |