Automating Traceability Link Recovery Using Information Retrieval

D. Mounika*, K. Delhi Babu**
* M.Tech Scholar, Department of Computer Science and Engineering, Sree Vidyanikethan Engineering College, Tirupati, India.
** Vice Principal, Department of Computer Science and Engineering, Sree Vidyanikethan Engineering College, Tirupati, India.
Periodicity:July - September'2016
DOI : https://doi.org/10.26634/jse.11.1.8191

Abstract

Software documentation is one of the important factors in the software maintenance. Documentation illustrates the written form of data which can be easily understandable by the software engineers. Traceability links are the links which are used to decrease the distance between the software developers and the software documentation. Previously there was a technique called AdDoc that automatically detects the changes in the documentation. In this paper we propose a method called Information Retrieval (IR). Information retrieval is well known method for the automating traceability recovery based on the similarity among the software artifacts. IR combines both textual and structural information for the traceability recovery in the software documentation. Synonymy problem can be decreased by the information retrieval method and can retrieve the correct link between the source code and the documentation. In this work, the performance of the information retrieval method is comparatively high than the previous technique.

Keywords

Software Documentation, Traceability Links, Information Retrieval, Latent Semantic Indexing

How to Cite this Article?

Mounika, D., and Babu, K. D. (2016). Automating Traceability Link Recovery Using Information Retrieval. i-manager’s Journal on Software Engineering, 11(1), 13-20. https://doi.org/10.26634/jse.11.1.8191

References

[1]. Antoniol, G and Canfora, (1999). “Recovering Code th to Documentation Links in OO Systems”. In Proceedings 6 IEEE Working Conference on Reverse Engineering (WCRE'99), pp. 136-144.
[2]. Deerwester and S., Dumais, (1990). “Indexing by Latent Semantic Analysis”. Journal of the American Society for Information Science, pp. 391-407.
[3]. M. P. Robillard and G. C. Murphy, (2007). “Representing concerns in source code”. ACM Trans. Softw. Eng. Methodol., Vol. 16, No. 1, pp. 1–38.
[4]. P. C. Rigby and M. P. Robillard, (2013). “Discovering essential code elements in informal documentation”. In th Proc. 35 ACM/IEEE Int. Conf. Softw. Eng, pp. 832–841.
[5]. B. Dagenais and M. P. Robillard, (2012). “Recovering traceability links between an API and its learning resources”. In Proceedings of the 34 ACM/IEEE International Conference on Software Engineering, pp. 47–57.
[6]. C. Somai and R. Mihalcea, (2008). “Linguistically motivated features for enhanced back-of-the-book th indexing”. In Proc. 46 Annu. Meet. Assoc. Comput. Linguistics, pp. 932–940.
[7]. B. Dagenais and F. W. Warr, (2007). “Inferring structural patterns for concern traceability in evolving software”. In Proc. IEEE/ACM Int. Conf. Autom. Softw. Eng., pp. 254–263.
[8]. A. De Lucia and F. Fasano, (2004). “Enhancing an artefact management system with traceability recovery th features”. In Proceedings of 20 IEEE International Conference on Software Maintenance, pp. 306–315.
[9]. B. Dagenais and M. P. Robillard, (2010). “Creating and evolving developer documentation: Understanding the decisions of open source contributors”. In Proc. ACM SIGSOFT Int. Symp. Found. Softw. Eng., pp. 127–136.
[10]. B. Dit and L. Guerrouj, (2011). “Can better identifier splitting techniques help feature location?” In th Proceedings of the 19 IEEE International Conference on Program Comprehension, pp. 11–20.
[11]. G. Antoniol and E. Merlo, (2002). “Recovering traceability links between code and documentation”. IEEE Transactions on Software Engineering, Vol. 28, No. 10, pp. 970–983.
[12]. J. H. Hayes and J. Osborne, (2003). “Improving requirements tracing via information retrieval”. In th Proceedings of the 11 IEEE International Requirements Engineering Conference, pp. 138–147.
[13]. M. Magyar, (2000). “Automating software documentation: A case study”. In Proc. ACM SIGDOC Int. Conf. Comput. Documentation, pp. 549–558.
[14]. Maletic, J. I. and Valluri, (1999). “Automatic Software Clustering via Latent Semantic Analysis”. In Proceedings th 14 IEEE International Conference on Automated Software Engineering (ASE'99), pp. 251-254.
[15]. Hayes and Osborne, (2003). “Improving Requirements Traceability via Information Retrieval”. in Proc. of IEEE Int. Requirements Engineering Conf, pp. 138-147.
[16]. M. Lormans and A. Van Deursen, (2006). “Can LSI help reconstructing requirements traceability in design th and test?” In Proceedings of 10 IEEE European Conference on Software Maintenance and Re Engineering, pp. 45–54.
If you have access to this article please login to view the article or kindly login to purchase the article

Purchase Instant Access

Single Article

North Americas,UK,
Middle East,Europe
India Rest of world
USD EUR INR USD-ROW
Pdf 35 35 200 20
Online 35 35 200 15
Pdf & Online 35 35 400 25

Options for accessing this content:
  • If you would like institutional access to this content, please recommend the title to your librarian.
    Library Recommendation Form
  • If you already have i-manager's user account: Login above and proceed to purchase the article.
  • New Users: Please register, then proceed to purchase the article.