Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
Event-Based Traceability for Managing Evolutionary Change
IEEE Transactions on Software Engineering
ACM Transactions on Software Engineering and Methodology (TOSEM)
Assessing IR-based traceability recovery tools through controlled experiments
Empirical Software Engineering
ASE '08 Proceedings of the 2008 23rd IEEE/ACM International Conference on Automated Software Engineering
A comprehensive characterization of NLP techniques for identifying equivalent requirements
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
A combination approach for enhancing automated traceability (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
Exploring a Bayesian and linear approach to requirements traceability
Information and Software Technology
Improving automated documentation to code traceability by combining retrieval techniques
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
| Hi-index | 0.01 |
When a system evolves, while the source code is changed documentation and traceability links are barely ever updated: maintaining traceability information between software artifacts is a costly and tedious activity frequently sacrificed during development and maintenance due to market pressure. This paper presents a new method to recovery traceability links between high level and low-level artifacts. The method is based on the partial knowledge of a subset of traceability links. It can be fully automated and the human intervention is only required to confirm or confute recovered traceability links. The method has been applied to software written in Java, to trace classes onto functional requirements, experimental result demonstrate the superiority of the novel method over the previously published results on the same system.