Main Article Content
This systematic literature review studies and summarizes findings of requirements documentation of non-functional requirements practiced by agile software development teams. It identifies current practices and existing gaps when agile software teams discuss and implement non-functional requirements, and the current methods used to document non-functional requirements. Our aim is to identify available evidence on current practices and gaps in documenting non-functional requirements. The review was conducted by searching major databases for publications between 2018 and 2022. The inclusion and exclusion criteria as well as quality assessment scoring criteria were subsequently established. Results show that common themes in the practices and gaps in requirements documentation by agile teams do intersect although they are scarce. This review has the benefit for practitioners to have a better approach to document the requirements that may result in a more quality software product.
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.
All articles published in JIWE are licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0) License. Readers are allowed to• Share — copy and redistribute the material in any medium or format under the following conditions:
- Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use;
- NonCommercial — You may not use the material for commercial purposes;
- NoDerivatives — If you remix, transform, or build upon the material, you may not distribute the modified material.