Requirement traceability model for agile development: results from empirical studies

Currently, it is crucial to develop software within the time frame given. Agile software development methodologies offer methods to develop a system in term of time and cost saving but has been criticized for not offering software quality management (a.k.a Non-Functional Requirement, NFR) properly....

Full description

Saved in:
Bibliographic Details
Main Authors: Arbain, A. F., Jawawi, D. N. A., Wan Kadir, W. M. N., Ghani, I.
Format: Article
Published: Blue Eyes Intelligence Engineering and Sciences Publication 2019
Subjects:
Online Access:http://eprints.utm.my/id/eprint/91552/
https://www.ijitee.org/wp-content/uploads/papers/v8i8s/H10690688S19.pdf.
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Currently, it is crucial to develop software within the time frame given. Agile software development methodologies offer methods to develop a system in term of time and cost saving but has been criticized for not offering software quality management (a.k.a Non-Functional Requirement, NFR) properly. An empirical case study has been conducted used to find out the need of a traceability approach for NFR change impact in most of Agile software methodology (TANC). TANC is improved and further evaluated by using expert survey analysis method. Based on the results of the expert survey analysis TANC has been proven to fulfil the characteristics of the criteria that needed to be a traceability approach in Agile Software Development for tracing NFR change impact. Thus, this proves that TANC offered better way to trace change impact during the agile development process.