Introduction to Modern Information Retrieval
Introduction to Modern Information Retrieval
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
Goal-centric traceability for managing non-functional requirements
Proceedings of the 27th international conference on Software engineering
Overcoming the Traceability Benefit Problem
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Advancing Candidate Link Generation for Requirements Tracing: The Study of Methods
IEEE Transactions on Software Engineering
Defining a strategy to introduce a software product line using existing embedded systems
EMSOFT '06 Proceedings of the 6th ACM & IEEE International conference on Embedded software
Adams re-trace: traceability link recovery via latent semantic indexing
Proceedings of the 30th international conference on Software engineering
Incremental Latent Semantic Indexing for Automatic Traceability Link Evolution Management
ASE '08 Proceedings of the 2008 23rd IEEE/ACM International Conference on Automated Software Engineering
Extraction and visualization of traceability relationships between documents and source code
Proceedings of the IEEE/ACM international conference on Automated software engineering
Recovering traceability links between an API and its learning resources
Proceedings of the 34th International Conference on Software Engineering
Code patterns for automatically validating requirements-to-code traces
Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering
Supporting commonality and variability analysis of requirements and structural models
Proceedings of the 16th International Software Product Line Conference - Volume 2
Hi-index | 0.00 |
If traceability links between requirements and source code are not clarified when conducting maintenance and enhancements for the same series of software products, engineers cannot immediately find the correction location in the source code for requirement changes. However, manually recovering links in a large group of products requires significant costs and some links may be overlooked. Here, we propose a semi-automatic method to recover traceability links between requirements and source code in the same series of large software products. In order to support differences in representation between requirements and source code, we recover links by using the configuration management log as an intermediary. We refine the links by classifying requirements and code elements in terms of whether they are common or specific to the products. As a result of applying our method to real products that have 60KLOC, we have recovered valid traceability links within a reasonable amount of time. Automatic parts have taken 13 minutes 36 seconds, and non-automatic parts have taken about 3 hours, with a recall of 76.2% and a precision of 94.1%. Moreover, we recovered some links that were unknown to engineers. By recovering traceability links, software reusability will be improved, and software product line introduction will be facilitated.