{"id":537,"date":"2022-08-17T17:53:54","date_gmt":"2022-08-17T09:53:54","guid":{"rendered":"https:\/\/yunpeng.site\/?p=537"},"modified":"2024-01-14T19:15:37","modified_gmt":"2024-01-14T11:15:37","slug":"tse-2022","status":"publish","type":"post","link":"https:\/\/yunpeng.site\/index.php\/2022\/08\/17\/tse-2022\/","title":{"rendered":"TSE 2022"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\n\t\t\n\t\t
\n\t\t\t\n\t\t\t
\n\t\t\t \n\t\t\t
\n\n\t\t\t \n\t\t\t
\n\t\t\t \n\t\t\t
\n\t\t\t \n\t\t\t
\n\t\t\t \t\t\t \n\t\t\t

\n\t\t\t \n\t\t\t \tRevisiting, Benchmarking and Exploring API Recommendation: How Far Are We?\t\t\t <\/span>\n\t\t\t <\/h1>\n\t\t\t \t \t\t\t \t \t\t\t \n\t\t\t
\n\t\t\t \t\n\t\t\t\t \tTSE 2022\t\t\t\t <\/span>\n\t\t\t <\/div>\n\t\t\t \t\t\t \t\t\t <\/div>\n\t\t\t \n\t\t\t <\/div>\n\t\t\t \n\t\t\t <\/div>\n\t\t\t \n\n\t\t\t <\/div>\n\t\t\t \n\t\t\t<\/div>\n\t\t\t\n\t\t<\/div>\n\t\t\n\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\n\t\t\n\t\t
\n\n\t\t\n\t\t
\n\n\t\t \t\t \n\t\t
\n\n\t\t \n\t\t
\n\t\t \n\t\t
\n\t\t \n\t\t

\n\t\t \t\n\t\t \tPaper Information\t\t <\/span>\n\t\t \t<\/h4>\n\t\t <\/div>\n\t\t \n\t\t <\/div>\n\t\t \n\n\t\t <\/div>\n\t\t \n\t\t \n\t\t \t\t \n\t\t
\n\t\t
\n\t\t \t\t
\n\t\t \t
\n\t\t \t

Paper Name:<\/strong> Revisiting, Benchmarking and Exploring API Recommendation: How Far Are We?<\/p>

Journal:<\/strong> IEEE Transactions on Software Engineering<\/a><\/p>

Authors: <\/strong>Yun Peng<\/span><\/em>, Shuqing Li, Wenwei Gu, Yichen Li, Wenxuan Wang, Cuiyun Gao, and Michael Lyu<\/p>\t\t <\/div>\n\t\t <\/div>\n\t\t\t \t\t\t \t\t <\/div>\n\t\t <\/div>\n\t\t \n\t\t \n\t\t \t\t<\/div>\n\t\t\n\n\t\t<\/div>\n\t\t\n\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\n\t\t\n\t\t
\n\n\t\t\n\t\t
\n\n\t\t \t\t \n\t\t
\n\n\t\t \n\t\t
\n\t\t \n\t\t
\n\t\t \n\t\t

\n\t\t \t\n\t\t \tAbstract\t\t <\/span>\n\t\t \t<\/h4>\n\t\t <\/div>\n\t\t \n\t\t <\/div>\n\t\t \n\n\t\t <\/div>\n\t\t \n\t\t \n\t\t \t\t \n\t\t
\n\t\t
\n\t\t \t\t
\n\t\t \t
\n\t\t \t

Application Programming Interfaces (APIs), which encapsulate the implementation of specific functions as interfaces, greatly improve the efficiency of modern software development. As the number of APIs grows up fast nowadays, developers can hardly be familiar with all the APIs and usually need to search for appropriate APIs for usage. So lots of efforts have been devoted to improving the API recommendation task. However, it has been increasingly difficult to gauge the performance of new models due to the lack of a uniform definition of the task and a standardized benchmark. For example, some studies regard the task as a code completion problem, while others recommend relative APIs given natural language queries. To reduce the challenges and better facilitate future research, in this paper, we revisit the API recommendation task and aim at benchmarking the approaches. Specifically, the paper groups the approaches into two categories according to the task definition, i.e., query-based API recommendation and code-based API recommendation. We study 11 recently-proposed approaches along with 4 widely-used IDEs. One benchmark named APIBench is then built for the two respective categories of approaches. Based on APIBench, we distill some actionable insights and challenges for API recommendation. We also achieve some implications and directions for improving the performance of recommending APIs, including appropriate query reformulation, data source selection, low resource setting, user-defined APIs, and query-based API recommendation with usage patterns.<\/p>\t\t <\/div>\n\t\t <\/div>\n\t\t\t \t\t\t \t\t <\/div>\n\t\t <\/div>\n\t\t \n\t\t \n\t\t \t\t<\/div>\n\t\t\n\n\t\t<\/div>\n\t\t\n\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\n\t\t\n\t\t
\n\n\t\t\n\t\t
\n\n\t\t \t\t \n\t\t
\n\n\t\t \n\t\t
\n\t\t \n\t\t
\n\t\t \n\t\t

\n\t\t \t\n\t\t \tWorkflow of API recommendation\t\t <\/span>\n\t\t \t<\/h4>\n\t\t <\/div>\n\t\t \n\t\t <\/div>\n\t\t \n\n\t\t <\/div>\n\t\t \n\t\t \n\t\t \n\t\t \t\t<\/div>\n\t\t\n\n\t\t<\/div>\n\t\t\n\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\n\t\t\n\t\t
\n\n\t\t\n\t\t
\n\n\t\t \n\t\t
\n\n\t\t \n\t\t
\n\t\t \t\t \n\t\t \n\t\t \n\t\t \"Workflow\n\t\t \n\t\t <\/i><\/span>\n\t\t <\/a>\n\t\t \n\t\t \t \t\t <\/div>\n\t\t \n\n\t\t <\/div>\n\t\t \n\n\t\t<\/div>\n\t\t\n\n\t\t<\/div>\n\t\t\n\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\n\t\t\n\t\t
\n\n\t\t\n\t\t
\n\n\t\t \t\t \n\t\t
\n\n\t\t \n\t\t
\n\t\t \n\t\t
\n\t\t \n\t\t

\n\t\t \t\n\t\t \tFindings\t\t <\/span>\n\t\t \t<\/h4>\n\t\t <\/div>\n\t\t \n\t\t <\/div>\n\t\t \n\n\t\t <\/div>\n\t\t \n\t\t \n\t\t \t\t \n\t\t
\n\t\t
\n\t\t \t\t
\n\t\t \t
\n\t\t \t
  1. Existing approaches fail to predict 57.8% method-level APIs that could be successfully predicted at the class level. The performance achieved by the approaches is far from the requirement of practical usage. Accurately recommending the method-level APIs still remains a great challenge.<\/strong><\/li>
  2. Learning-based methods do not necessarily outperform retrieval-based methods in recommending more correct APIs. The insufficient query-API pairs for training limit the performance of learning-based methods.<\/strong><\/li>
  3. Current approaches cannot rank the correct APIs well<\/strong>, considering the huge gap between the scores of Success Rate and the other ranking metrics.<\/li>
  4. Query reformulation techniques are quite effective<\/strong> in helping query-based API recommendation approaches give the correct API by adding an average boost of 27.7% and 49.2% on class-level and method-level recommendations, respectively.<\/li>
  5. Query expansion is more stable and effective<\/strong> to help current query-based API recommendation approaches give correct APIs than query modification.<\/li>
  6. In query expansion, adding predicted API class names or relevant words<\/strong> to queries are more useful than adding other tokens.<\/li>
  7. BERT-based data augmentation shows superior performance<\/strong> in query modification compared with other query modification techniques.<\/li>
  8. Expanding queries or modifying queries with appropriate data augmentation methods can improve the ranking performance<\/strong> of the query-based API recommendation techniques.<\/li>
  9. Original queries raised by users usually contain noisy words which can bias the recommendation results, and query reformulation techniques should consider involving noisy-word deletion<\/strong> for a more accurate recommendation.<\/li>
  10. Apart from official documentation, using other data sources<\/strong> such as Stack Overflow can significantly improve the performance of query-based API recommendation approaches.<\/li>
  11. DL models such as TravTrans show superior performance<\/strong> on code-based API recommendation by achieving a Success Rate@10 of 0.62, while widely-used IDEs also obtain satisfying performance by achieving a Success Rate@10 of 0.5 ~ 0.6.<\/li>
  12. Although current approaches achieve good performance on recommending standard and popular third-party libraries, they face the challenges of correctly predicting the user-defined APIs.<\/strong><\/li>
  13. Context length can impact the performance of current approaches in API recommendation. The approaches perform poorly for the functions with extremely short or long lengths, and accurate recommendation for the extremely short functions is more challenging<\/strong>.<\/li>
  14. The location of recommendation points can affect the performance of current approaches. Current approaches perform worst at front recommendation points<\/strong> due to limited contexts. Some of them also suffer from overwhelming contexts<\/strong> at back recommendation point.<\/li>
  15. Current approaches using fine-grained context representation are sensitive to the domain of the training data<\/strong> and suffer from performance drops when recommending cross-domain APIs.<\/li>
  16. Training on multiple domains<\/strong> helps the current approaches to recommend APIs in different single domains, and the performance is generally
    better than only training on a single domain.<\/li><\/ol>\t\t <\/div>\n\t\t <\/div>\n\t\t\t \t\t\t \t\t <\/div>\n\t\t <\/div>\n\t\t \n\t\t \n\t\t \t\t<\/div>\n\t\t\n\n\t\t<\/div>\n\t\t\n\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\n\t\t\n\t\t
    \n\n\t\t\n\t\t
    \n\n\t\t \t\t \n\t\t
    \n\n\t\t \n\t\t
    \n\t\t \n\t\t
    \n\t\t \n\t\t

    \n\t\t \t\n\t\t \tBenchmark\t\t <\/span>\n\t\t \t<\/h4>\n\t\t <\/div>\n\t\t \n\t\t <\/div>\n\t\t \n\n\t\t <\/div>\n\t\t \n\t\t \n\t\t \t\t \n\t\t
    \n\t\t
    \n\t\t \t\t
    \n\t\t \t
    \n\t\t \t

    APIBench contains two benchmarks: APIBench-Q for query-based API recommendation approaches and APIBench-C for code-based API recommendation approaches.\u00a0<\/p>

    APIBench has instances in Python and Java.<\/p>

    APIBench-Q:<\/strong><\/p>

    It contains more than 10,000 original queries from StackOverflow and tutorial websites. It also contains more than 100,000 reformulated queries generated by different data augmentation approaches according to original queries.<\/p>

    APIBench-C:<\/strong><\/p>

    It contains more than 2,000 GitHub projects in Python and Java. All projects are divided into five domains.<\/p>\t\t <\/div>\n\t\t <\/div>\n\t\t\t \t\t\t \t\t \n\t\t

    \n\t\t \t\n\t\t \t\t\n\t\t\t \tGet benchmark\t\t\t <\/span>\n\t\t \t<\/a>\n\t\t <\/div>\n\t\t \t \t\t <\/div>\n\t\t <\/div>\n\t\t \n\t\t \n\t\t \t\t<\/div>\n\t\t\n\n\t\t<\/div>\n\t\t\n\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\n\t\t\n\t\t
    \n\n\t\t\n\t\t
    \n\n\t\t \t\t \n\t\t
    \n\n\t\t \n\t\t
    \n\t\t \n\t\t
    \n\t\t \n\t\t

    \n\t\t \t\n\t\t \tGitHub\t\t <\/span>\n\t\t \t<\/h4>\n\t\t <\/div>\n\t\t \n\t\t <\/div>\n\t\t \n\n\t\t <\/div>\n\t\t \n\t\t \n\t\t \t\t \n\t\t
    \n\t\t
    \n\t\t \t\t
    \n\t\t \t
    \n\t\t \t

    https:\/\/github.com\/JohnnyPeng18\/APIBench<\/a><\/p>\t\t <\/div>\n\t\t <\/div>\n\t\t\t \t\t\t \t\t \n\t\t

    \n\t\t \t\n\t\t \t\t\n\t\t\t \tGo to github\t\t\t <\/span>\n\t\t \t<\/a>\n\t\t <\/div>\n\t\t \t \t\t <\/div>\n\t\t <\/div>\n\t\t \n\t\t \n\t\t \t\t<\/div>\n\t\t\n\n\t\t<\/div>\n\t\t\n\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\n\t\t\n\t\t
    \n\n\t\t\n\t\t
    \n\n\t\t \t\t \n\t\t
    \n\n\t\t \n\t\t
    \n\t\t \n\t\t
    \n\t\t \n\t\t

    \n\t\t \t\n\t\t \tResources\t\t <\/span>\n\t\t \t<\/h4>\n\t\t <\/div>\n\t\t \n\t\t <\/div>\n\t\t \n\n\t\t <\/div>\n\t\t \n\t\t \n\t\t \n\t\t \t\t<\/div>\n\t\t\n\n\t\t<\/div>\n\t\t\n\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t
    \n\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t<\/i>\t\t\t<\/span>\n\t\t\t\t\t\tDownload PDF<\/span>\n\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\n\t\t\n\t\t
    \n\n\t\t\n\t\t
    \n\n\t\t \t\t \n\t\t
    \n\n\t\t \n\t\t
    \n\t\t \n\t\t
    \n\t\t \n\t\t

    \n\t\t \t\n\t\t \tContact\t\t <\/span>\n\t\t \t<\/h4>\n\t\t <\/div>\n\t\t \n\t\t <\/div>\n\t\t \n\n\t\t <\/div>\n\t\t \n\t\t \n\t\t \t\t \n\t\t
    \n\n\t\t \n\t\t
    \n\t\t\t
    \n

    <\/p>

      <\/ul><\/div>\n
      \n
      \n\n\n\n\n\n\n<\/div>\n