ICSE '94 Proceedings of the 16th international conference on Software engineering
Concern graphs: finding and describing concerns using structural program dependencies
Proceedings of the 24th International Conference on Software Engineering
Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
Recovering documentation-to-source-code traceability links using latent semantic indexing
Proceedings of the 25th International Conference on Software Engineering
Using a Concept Lattice of Decomposition Slices for Program Understanding and Impact Analysis
IEEE Transactions on Software Engineering
How Effective Developers Investigate Source Code: An Exploratory Study
IEEE Transactions on Software Engineering
Advancing Candidate Link Generation for Requirements Tracing: The Study of Methods
IEEE Transactions on Software Engineering
IBM Systems Journal - Model-driven software development
Software Feature Understanding in an Industrial Setting
ICSM '06 Proceedings of the 22nd IEEE International Conference on Software Maintenance
Identifying Crosscutting Concerns Using Fan-In Analysis
ACM Transactions on Software Engineering and Methodology (TOSEM)
ICPC '08 Proceedings of the 2008 The 16th IEEE International Conference on Program Comprehension
Automated traceability analysis for UML model refinements
Information and Software Technology
Combining textual and structural analysis of software artifacts for traceability link recovery
TEFSE '09 Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering
Case Study of Feature Location Using Dependence Graph, after 10 Years
ICPC '10 Proceedings of the 2010 IEEE 18th International Conference on Program Comprehension
Effort and Quality of Recovering Requirements-to-Code Traces: Two Exploratory Experiments
RE '10 Proceedings of the 2010 18th IEEE International Requirements Engineering Conference
How do we trace requirements: an initial study of analyst behavior in trace validation tasks
Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Proceedings of the 17th International Software Product Line Conference
Enhancing software artefact traceability recovery processes with link count information
Information and Software Technology
| Hi-index | 0.00 |
Traces between requirements and code reveal where requirements are implemented. Such traces are essential for code understanding and change management. Unfortunately, traces are known to be error prone. This paper introduces a novel approach for validating requirements-to-code traces through calling relationships within the code. As input, the approach requires an executable system, the corresponding requirements, and the requirements-to-code traces that need validating. As output, the approach identifies likely incorrect or missing traces by investigating patterns of traces with calling relationships. The empirical evaluation of four case study systems covering 150 KLOC and 59 requirements demonstrates that the approach detects most errors with 85-95% precision and 82-96% recall and is able to handle traces of varying levels of correctness and completeness. The approach is fully automated, tool supported, and scalable.