Agile non functional requiremnents (NFR) traceability metamodel

Abstract

Agile methodologies are well known for early and frequently releases. Besides that, it also handles functional requirement changes well during the software development without causing delays. However, the functional requirement changes may affect the non-functional requirements (NFRs). It is also possible that the agile team is not even aware of these effects causing dysfunctional system in terms of security and performance. This issue could be addressed by offering traceability mechanism that helps to trace the effect of functional requirement changes on the non-functional requirements. Unfortunately, there are a few researchers that provide study regarding this issue. Thus, this study attempts to present a Traceability Process Model (TPM) to tackle the issue of tracing NFR especially in security and performance. The TPM is compatible in Agile development processes such as Scrum and FDD.