School of Engineering, University of Electronic Science and Technology of China, Chengdu 611731, China;Technology Department, Hunan Broadcasting System, Changsha 410007, China 在期刊界中查找 在百度中查找 在本站中查找
Information retrieval (IR) is widely used in automatically discovering requirement traceability. However IR will miss some correct artifacts which have low text similarity with the requirement. There are accuracy issues in requirement traceability based on IR. To solve the problem, we propose an approach of using the developer collaborative relationship to improve the accuracy of the traceability links recovery between requirement and source code. Meanwhile, we develop a requirement-to-code traceability system. When the system is tracing, it retrieves the source code artifacts of the highest text similarity with the requirement and extracts the developer collaborative relationship from code commit logs. Then the system recommends some relevant code artifacts by developer collaboration relationship. Users can choose the correct code artifacts from the recommend result. The experiment shows that the requirement traceability system could improve the accuracy and the efficiency and reduce errors.
1 Gotel OCZ, Finkelstein ACW. An analysis of the requirements traceability problem. Proc. of the First International Conference on Requirements Engineering, 1994. 94-101.
2 Baeza-Yates R, Ribeiro-Neto B. Modern information retrieval. New York: ACM press, 1999.
3 De Lucia A, Marcus A, Oliveto R, et al. Information retrieval methods for automated traceability recovery. Software and Systems Traceability, London, Springer. 2012. 71-98.
4 De Lucia A, Marcus A, Oliveto R, et al. Information retrieval methods for automated traceability recovery. Software and Systems Traceability, London, Springer. 2012. 71-98.
5 Abadi A, Nisenson M, Simionovici Y. A traceability technique for specifications. The 16th IEEE International Conference on Program Comprehension, ICPC 2008. 2008, 8: 103-112.
6 McMillan C, Poshyvanyk D, Revelle M. Combining textual and structural analysis of software artifacts for traceability link recovery. Traceability in Emerging Forms of Software Engineering, 2009: 41-48.
7 Asuncion HU, Asuncion AU, Taylor RN. Software traceability with topic modeling. Proc. of the 32nd ACM/IEEE Int. Conf. on Software Engineering. 2010. 95-104.
8 Gethers M, Oliveto R, Poshyvanyk D, et al. On integrating orthogonal information retrieval methods to improve traceability recovery. 27th IEEE International Conference on Software Maintenance (ICSM). 2011. 133-142.
9 Panichella A, McMillan C, Moritz E, et al. When and how using structural information to improve ir-based traceability recovery. 17th European Conference on Software Maintenance and Reengineering. 2013. 199-208.
10 Kong WK, Huffman Hayes J, Dekhtyar A, et al. How do we trace requirements: an initial study of analyst behavior in trace validation tasks. Proc. of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering. 2011. 32-39.
11 李引.需求变更影响分析模型及相关技术研究[学位论文].北京:中国科学院软件研究所,2010.
12 Cleland-Huang J, Czauderna A, Gibiec M, et al. A machine learning approach for tracing regulatory codes to product specific requirements. Proc. of the 32nd ACM/IEEE Int. Conf. on Software Engineering. 2010. 155-164.
13 Capobianco G, Lucia AD, Oliveto R, et al. Improving IR-based traceability recovery via noun-based indexing of software artifacts. Journal of Software: Evolution and Process, 2013, 25(7): 743-762.
14 Kagdi H, Maletic JI, Sharif B. Mining software repositories for traceability links. 15th IEEE International Conference on Program Comprehension, 2007: 145-154.
15 Meneely A, Williams L, Snipes W, et al. Predicting failures with developer networks and social network analysis. Proc. of the 16th ACM SIGSOFT International Symposium on Foundations of Software Engineering, 2008: 13-23.
16 Wolf T, Schroter A, Damian D, et al. Predicting build failures using social network analysis on developer communication. Proc. of the 31st International Conference on Software Engineering. 2009. 1-11.
17 Anvik J, Murphy GC. Reducing the effort of bug report triage: Recommenders for development-oriented decisions. ACM Trans. on Software Engineering and Methodology, 2011, 20(3): 10.
18 Duc Anh N, Cruzes D S, Conradi R, et al. Empirical validation of human factors in predicting issue lead time in open source projects. Proc. of the 7th Int. Conf. on Predictive Models in Software Engineering. 2011. 13.
19 Diaz D, Bavota G, Marcus A, et al. Using code ownership to improve IR-based Traceability Link Recovery. 21st Int. Conf. on Program Comprehension, 2013.