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.

Full Text:



M. Martínez Pérez, C. Dafonte, and Á. Gómez, “Traceability in Patient Healthcare through the Integration of RFID Technology in an ICU in a Hospital.,” Sensors Basel Sensors, vol. 18, no. 5, May 2018.

S. Kim, H. Kim, J. A. Kim, and Y. Cho, “A study on traceability between documents of a software R&D project,” in Advanced multimedia and ubiquitous engineering, vol. 354, J. J. Park, H.-C. Chao, H. Arabnia, and N. Y. Yen, Eds. Berlin, Heidelberg: Springer Berlin Heidelberg, 2016, pp. 203–210.

Q. Lu and X. Xu, “Adaptable Blockchain-Based Systems: A Case Study for Product Traceability,” IEEE Softw., vol. 34, no. 6, pp. 21–27, Nov. 2017.

F. Furtado and A. Zisman, “Trace++: A traceability approach to support transitioning to agile software engineering,” in 2016 IEEE 24th International Requirements Engineering Conference (RE), 2016, pp. 66–75.

T. Vale, E. S. de Almeida, V. Alves, U. Kulesza, N. Niu, and R. de Lima, “Software product lines traceability: A systematic mapping study,” Inf. Softw. Technol., vol. 84, pp. 1–18, Apr. 2017.

R. Elamin and R. Osman, “Towards requirements reuse by implementing traceability in agile development,” in 2017 IEEE 41st Annual Computer Software and Applications Conference (COMPSAC), 2017, pp. 431–436.

R. Vallon, B. J. da Silva Estácio, R. Prikladnicki, and T. Grechenig, “Systematic literature review on agile practices in global software development,” Inf. Softw. Technol., vol. 96, pp. 161–180, Apr. 2018.

B. Fitzgerald, K. Stol, R.O. Sullivan, and D.O Brien, Scaling Agile Methods to Regulated Environments : An Industry Case Study, In: 35th International Conference on Software Engineering (ICSE), pp. 863-872.2013.

L. Passos, C. Krzysztof, A. Sven, W. Andrzej, K. Christian, and G. Jianmei, Feature-oriented software evolution, In: Proceedings of the Seventh International Workshop on Variability Modelling of Software-intensive Systems.2013,

J. Zhang. "The software development process methodology of resource-based access control." In Computer and Automation Engineering (ICCAE), 2010 The 2nd International Conference on, vol. 4, pp. 111-117. IEEE, 2010.

L. K. Roses, A. Windmöller, and E. A. do Carmo. "Favorability conditions in the adoption of agile method practices for Software development in a public banking." JISTEM-Journal of Information Systems and Technology Management 13, no. 3, pp. 439-458, 2016.

N. Spasibenko, and A. Besiana. "Project Suitability for Agile methodologies." 2009.

J. Holvitie, S.A. Licorish, R.O. Spínola, S. Hyrynsalmi, S.G. MacDonell, T.S. Mendes, J. Buchan, and V. Leppänen. “Technical debt and agile software development practices and processes: An industry practitioner survey”. Information and Software Technology, 96, pp.141-160, 2018.

Al-Zewairi, Malek, Mariam Biltawi, Wael Etaiwi, and Adnan Shaout. "Agile software development methodologies: survey of surveys." Journal of Computer and Communications 5, no. 05 pp. 74-97.2017.

Rigby, Darrell K., Jeff Sutherland, and Hirotaka Takeuchi. "Embracing agile." Harvard Business Review 94, no. 5, pp. 40-50.2016.

Anwer, Faiza, Shabib Aftab, Usman Waheed, and Syed Shah Muhammad. "Agile Software Development Models TDD, FDD, DSDM, and Crystal Methods: A Survey." International journal of multidisciplinary sciences and engineering 8, no. 2 pp. 1-10. 2017.

S. Gayer, A. Herrmann, T. Keuler, M. Riebisch, and P. O. Antonino, “Lightweight traceability for the agile architect,” Computer, vol. 49, no. 5, pp. 64–71, May 2016.

P. Gregory, L. Barroca, H. Sharp, A. Deshpande, and K. Taylor, “The challenges that challenge: Engaging with agile practitioners’ concerns,” Inf. Softw. Technol., vol. 77, pp. 92–104, Sep. 2016. M. Senapathi and A. Srinivasan, “An empirical investigation of the factors affecting agile usage,” in Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering - EASE ’14, New York, New York, USA, 2014, pp. 1–10.

M. A. Brito and F. de Sá-Soares, “Assessment frequency in introductory computer programming disciplines,” Comput. Human Behav., vol. 30, pp. 623–628, Jan. 2014.



  • There are currently no refbacks.

Published by INSIGHT - Indonesian Society for Knowledge and Human Development