Information retrieval: data structures and algorithms
Information retrieval: data structures and algorithms
Use Case to Source Code Traceability: The Developer Navigation View Point
RE '09 Proceedings of the 2009 17th IEEE International Requirements Engineering Conference, RE
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Assessing the effect of requirements traceability for software maintenance
ICSM '12 Proceedings of the 2012 IEEE International Conference on Software Maintenance (ICSM)
| Hi-index | 0.00 |
[Context and motivation] Traceability links between requirements and code are often created after development, which can, for example, lead to higher development effort. To address this weakness, we developed in previous work an approach that captures traceability links between requirements and code as the development progresses by using artifacts from project management called work items. [Question/problem] It is important to investigate empirically what is the best way to capture such links and how these links are used during development. [Principal ideas/results] In order to link requirements, work items and code during development, we extended our approach from previous work by defining three traceability link creation processes. We are applying these processes in practice in a software development project conducted with undergraduate students. The results indicate that our approach creates correct traceability links between requirements and code with high precision/recall during development, while developers mainly used the third process to link work items after implementation. Furthermore, the students used a subset of the created traceability links for navigating between requirements and code during the early phase of the development project. [Contribution] In this paper, we report on preliminary empirical results from applying our approach in practice.