使用段落向量来改进我们现有的代码审查辅助工具-CRUSO
Using Paragraph Vectors to improve our existing code review assisting tool-CRUSO
摘要:
代码评审是评估源代码缺陷的有效方法之一。然而,现有的方法依赖于专家或效率低下。在本文中,我们提高了我们现有的代码审查辅助工具-CRUSO的性能(在速度和内存使用方面)。该方法的中心思想是通过使用不同StackOverflow(SO)帖子中存在的类似代码片段的缺陷分数来估计输入源代码的缺陷。我们的论文的重要贡献是i)SOpostsDB:包含PVA向量和SO帖子信息的数据集,ii)CRUSO-P:基于在\emph{SOpostsDB}上训练的PVA模型的代码审查辅助系统。对于给定的输入源代码,CRUSO-P将其标记为{可能有缺陷,不太可能有缺陷,不可预测}。为了开发CRUSO-P,我们处理了超过300万个SO帖子和188200多个GitHub源文件。CRUSO-P设计用于处理以流行程序设计语言{C、C#、Java、JavaScript和Python}编写的源代码。CRUSO-P的性能优于CRUSO,响应时间提高了97.82%,存储减少了99.15%。当用C程序设计语言测试时,CRUSO-P达到了99.6%的最高平均准确度分数,从而比现有方法提高了5.6%。
英文摘要:
Code reviews are one of the effective methods to estimate defectiveness in source code. However, the existing methods are dependent on experts or inefficient. In this paper, we improve the performance (in terms of speed and memory usage) of our existing code review assisting tool--CRUSO. The central idea of the approach is to estimate the defectiveness for an input source code by using the defectiveness score of similar code fragments present in various StackOverflow (SO) posts. The significant contributions of our paper are i) SOpostsDB: a dataset containing the PVA vectors and the SO posts information, ii) CRUSO-P: a code review assisting system based on PVA models trained on \emph{SOpostsDB}. For a given input source code, CRUSO-P labels it as {Likely to be defective, Unlikely to be defective, Unpredictable}. To develop CRUSO-P, we processed >3 million SO posts and 188200+ GitHub source files. CRUSO-P is designed to work with source code written in the popular programming languages {C, C#, Java, JavaScript, and Python}. CRUSO-P outperforms CRUSO with an improvement of 97.82% in response time and a storage reduction of 99.15%. CRUSO-P achieves the highest mean accuracy score of 99.6% when tested with the C programming language, thus achieving an improvement of 5.6% over the existing method.
机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。