Reconstructing requirements coverage views from design and test using traceability recovery via LSI
TEFSE '05 Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering
Semantic clustering: Identifying topics in source code
Information and Software Technology
IEEE Transactions on Software Engineering
Correlating Social Interactions to Release History during Software Evolution
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Towards Software Component Procurement Automation with Latent Semantic Analysis
Electronic Notes in Theoretical Computer Science (ENTCS)
ACM Transactions on Software Engineering and Methodology (TOSEM)
Extracting traceability information from C# projects
ICCOMP'05 Proceedings of the 9th WSEAS International Conference on Computers
An industrial case study in reconstructing requirements views
Empirical Software Engineering
Establishing and maintaining traceability between large aerospace process standards
TEFSE '09 Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering
Cross-artifact traceability using lightweight links
TEFSE '09 Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering
Traceability-Based Change Awareness
MODELS '09 Proceedings of the 12th International Conference on Model Driven Engineering Languages and Systems
A machine learning approach for tracing regulatory codes to product specific requirements
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Source code indexing for automated tracing
Proceedings of the 6th International Workshop on Traceability in Emerging Forms of Software Engineering
Improving trace accuracy through data-driven configuration and composition of tracing features
Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering
| Hi-index | 0.00 |
We present a traceability recovery method and tool based on Latent Semantic Indexing (LSI) in the context of an artefact management system. The tool highlights the candidate links not identified yet by the software engineer and the links identified but missed by the tool, probably due to inconsistencies in the usage of domain terms in the traced software artefacts. We also present a case study of using the traceability recovery tool on software artefacts belonging to different categories of documents, including requirement, design, and testing documents, as well as code components.