Maintaining Requirements and Test Cases Traceability in an Agile Environment
Abstract
The increasing adoption of agile methodologies in software development has highlighted challenges related to the dynamic management of requirements and the continuous updating of test cases. In an environment where changes are frequent and requirements evolve rapidly, ensuring the quality and consistency of testing is essential for project success. This problem is common among various companies that adopt agile methodologies, facing difficulties in maintaining software quality while managing frequent changes in requirements. In this context, this research proposes a semi-automated approach to managing requirements and test cases by automatically identifying the impacts of requirement changes on test cases. For this purpose, the natural language process is applied with the support of the BERT language model. The methodology proposed in this study aims to enable the addition, editing, and removal of requirements and test cases in an integrated manner, ensuring that all changes are reflected efficiently and accurately. The suggested solution is based on tokenization and embeddings provided by the BERT model, combined with cosine similarity analysis, to identify the requirements and test cases that may be affected by changes in the requirement set. It is expected that the approach brings significant improvements in the efficiency of the requirement and test case management process and, consequently, in the quality of the software developed. By automatically identifying and updating test cases, it should contribute to reducing failures and rework, resulting in a more agile development process aligned with stakeholder expectations.
References
Antonino, P. O., Keuler, T., Germann, N., and Cronauer, B. (2014). A non-invasive approach to trace architecture design, requirements specification and agile artifacts. Proceedings of the Australian Software Engineering Conference, ASWEC, pages 220–229.
Devlin, J., Chang, M.-W., Lee, K., and Toutanova, K. (2019). Bert: Pre-training of deep bidirectional transformers for language understanding.
Gazzawe, F., Lock, R., and Dawson, C. (2020). Traceability framework for requirement artefacts. Advances in Intelligent Systems and Computing, 1228 AISC:97–109.
Gröpler, R., Sudhi, V., García, E. J. C., and Bergmann, A. (2021). Nlp-based requirements formalization for automatic test case generation. CEUR Workshop Proceedings, 2951:18–30.
Reider, M., Magnus, S., and Krause, J. (2018). Feature-based testing by using model synthesis, test generation and parameterizable test prioritization. Proceedings - 2018 IEEE 11th International Conference on Software Testing, Verification and Validation Workshops, ICSTW 2018, pages 130–137.
Schwaber, K. and Sutherland, J. (2020). The scrum guide: The definitive guide to scrum: The rules of the game. Available online at: [link]. Accessed: 18 April 2025.
Silva, A., Andrade, W. L., and Alves, E. L. (2018). A study on the impact of model evolution in mbt suites. ACM International Conference Proceeding Series, pages 49–56.
Souza, F., Nogueira, R., and Lotufo, R. (2020). BERTimbau: Pretrained BERT Models for Brazilian Portuguese, pages 403–417.
Sultania, A. K. (2015). Developing software product and test automation software using agile methodology. Proceedings of the 2015 3rd International Conference on Computer, Communication, Control and Information Technology, C3IT 2015.
Tiwari, S. and Gupta, A. (2015). An approach of generating test requirements for agile software development. ACM International Conference Proceeding Series, 18-20-February-2015:186–195.
Tsilionis, K., Maene, J., Heng, S., Wautelet, Y., and Poelmans, S. (2021). Conceptual modeling versus user story mapping: Which is the best approach to agile requirements engineering? Lecture Notes in Business Information Processing, 415 LNBIP:356–373.
Yang, A. Z., Costa, D. A. D., and Zou, Y. (2019). Predicting co-changes between functionality specifications and source code in behavior driven development. IEEE International Working Conference on Mining Software Repositories, 2019-May:534–544.
