International Journal on Advanced Science, Engineering and Information Technology, Vol. 10 (2020) No. 1, pages: 34-40, DOI:10.18517/ijaseit.10.1.10176

Case Study on Non-Functional Requirement Change Impact Traceability for Agile Software Development

Adila Firdaus Arbain, Dayang Norhayati Abang Jawawi, Wan Mohd Nasir bin Wan Kadir, Imran Ghani


Currently, it is crucial to develop a complex software on time. Agile software development methodologies provide methods to develop a system in term of time and cost-saving but it has been criticized for software quality management. In this paper, a case study is used to find out the need of NFR change impact traceability approach in most of Agile software methodology. This case study was conducted in an undergraduate course that trained the students on how to develop software using Agile process model.This case study has been conducted for 4 months in an undergraduate-level course, Application Development. The samples of this case study are among Year 3 undergraduate students. The case study shows the lack of traceability techniques in the existing Agile process model (SFDD- Secured Feature Driven Development) that result to non-awareness of NFR change impact during development. Based on the case study mentioned the main objective of the case study conducted in survey is to empirically test the theoretical constructs and the hypothesized relationships of the research issues that concern on the lack of change impact management towards NFR in Agile Software Methodology.  TANC (Traceability for Agile Non-Functional Requirement Change Impact) model offered techniques in tracing change impact during the agile development process. Therefore, the result of the case study, a traceability process model needs to design in order to tackle the NFR change impact issues in Agile software development.


agile methodologies; scrum; feature driven development; traceability; non-functional requirement.

Viewed: 1063 times (since abstract online)

cite this paper     download