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
Event-Based Traceability for Managing Evolutionary Change
IEEE Transactions on Software Engineering
Helping Analysts Trace Requirements: An Objective Look
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
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
Software Feature Understanding in an Industrial Setting
ICSM '06 Proceedings of the 22nd IEEE International Conference on Software Maintenance
ICPC '08 Proceedings of the 2008 The 16th IEEE International Conference on Program Comprehension
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
Code patterns for automatically validating requirements-to-code traces
Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering
| 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, the handling of traces is highly error prone, in part due to the informal nature of requirements. This paper discusses observations on the connectedness between requirements-to-code traces and calling relationships within the source code. These observations are based on the empirical evaluation of four case study systems covering 150 KLOC and 59 sample requirements. We found that certain patterns of connectedness have high or low likelihoods of occurring. These patterns can thus be used to confirm or reject existing traceability - hence they are useful for validating requirements-to-code traces.