2013 7th International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE) 2013
DOI: 10.1109/tefse.2013.6620159
|View full text |Cite
|
Sign up to set email alerts
|

A tracelab-based solution for identifying traceability links using LSI

Abstract: Abstract-An information retrieval technique, latent semantic indexing (LSI), is used to automatically identify traceability links from system documentation to program source code. The experiment is performed in the TraceLab framework. The solution provides templates and components for building and querying LSI space and datasets (corpora) that can be used as inputs for these components. The proposed solution is evaluated on traceability links already discovered by mining adaptive commits of the open source sys… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2014
2014
2019
2019

Publication Types

Select...
5
2

Relationship

1
6

Authors

Journals

citations
Cited by 10 publications
(4 citation statements)
references
References 15 publications
0
4
0
Order By: Relevance
“…The gold sets were constructed using the mappings between the source code and the features, which were made available by Eaddy et al [58]. These mappings 3 were produced by considering the sections of the ECMAScript specification as features, and associating them with software artifacts using the following prune dependency rule, created by Eaddy et al [58]: "A program element is relevant to a concern if it should be removed, or otherwise altered, when the concern is pruned. "…”
Section: Systemsmentioning
confidence: 99%
See 1 more Smart Citation
“…The gold sets were constructed using the mappings between the source code and the features, which were made available by Eaddy et al [58]. These mappings 3 were produced by considering the sections of the ECMAScript specification as features, and associating them with software artifacts using the following prune dependency rule, created by Eaddy et al [58]: "A program element is relevant to a concern if it should be removed, or otherwise altered, when the concern is pruned. "…”
Section: Systemsmentioning
confidence: 99%
“…That being said, we tried to implement as many of the techniques that we could in order to show the efficacy and usefulness of TraceLab as a research tool in the domain of software evolution and maintenance. We are continuously working on driving new research projects with TraceLab [3,29,44,50,78,101,155,183] and encourage others to do so as well.…”
Section: Limitationsmentioning
confidence: 99%
“…This is also done by extracting all the natural language information associated with a given source code; all the words used in include user documents (e.g., HTML,XML/docbook, LaTeX and Doxygen), build management documents (automake, cmake, and makefile), HowTo guides (e.g., FAQs), release and distribution documents (e.g.,ChangeLogs, whatsNew, README, and INSTALL guides), progress monitoring documents (TODO and STATUS), and extensible mechanisms (e.g., Python, Ruby, and Pearl bindings for an API) [2,8,9].…”
Section: Stepmentioning
confidence: 99%
“…Both of the source code and the external documentation need to be broken up into the proper granularity to define the corpuses documents, which will be represented as vectors [2,9,[12][13][14]. Therefore, we split up the source code into documents with function granularity level.…”
Section: Total Of External Documents 11594mentioning
confidence: 99%