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
When and how to visualize traceability links?
TEFSE '05 Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering
IEEE Transactions on Software Engineering
Towards Software Component Procurement Automation with Latent Semantic Analysis
Electronic Notes in Theoretical Computer Science (ENTCS)
ACM Transactions on Software Engineering and Methodology (TOSEM)
Lagrein: tracking the software development process
Companion to the 22nd ACM SIGPLAN conference on Object-oriented programming systems and applications companion
Visualizing software evolution with lagrein
Companion to the 23rd ACM SIGPLAN conference on Object-oriented programming systems languages and applications
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
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
A survey of traceability in requirements engineering and model-driven development
Software and Systems Modeling (SoSyM)
Which traceability visualization is suitable in this context? a comparative study
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
MOOGLE: a metamodel-based model search engine
Software and Systems Modeling (SoSyM)
| Hi-index | 0.00 |
We present the traceability recovery tool developed in the ADAMS artefact management system. The tool is based on an Information Retrieval technique, namely Latent Semantic Indexing and aims at supporting the software engineer in the identification of the traceability links between artefacts of different types. We also present a case study involving seven student projects which represented an ideal workbench for the tool. The results emphasise the benefits provided by the tool in terms of new traceability links discovered, in addition to the links manually traced by the software engineer. Moreover, the tool was also helpful in identifying cases of lack of similarity between artefacts manually traced by the software engineer, thus revealing inconsistencies in the usage of domain terms in these artefacts. This information is valuable to assess the quality of the produced artefacts.