This site requires Cookies enabled in your browser for login.
Updating ...
WaterNet Home
WaterNet
for
pour le
Canada
Menu
WaterNet
Home
GWFO
Home
Catalogue
Master Index
Data
Centre
X
Find Data By Variable Find Data By Site, Facility, or Deployable Show Near-realtime Telemetry (7 day)
Collections
X
Defaults
Select All
Websites
X
Global Water Futures Observatories (GWFO) Global Water Futures (GWF) Global Institute for Water Security (GIWS) International Network of Alpine Research Catchment Hydrology
Legacy Research Programs
X
Changing Cold Regions Network (CCRN) Drought Research Initiative (DRI) International Network of Alpine Research Catchment Hydrology (Legacy Site) Improving Processes & Parameterization for Prediction in Cold Regions Hydrology (IP3) The Mackenzie Global Energy and Water Cycle Experiment (GEWEX) Study (MAGS)
Legacy sites
Map
Utilities
X
Account Settings Create a New Record Record List Alias List Editor
Edit Data Centre
Data Types
. . .
X
Clear
Select All
Advanced Search
Go to Top⇡
Related items loading ...
Fetching Chart ...
Publication Additional Information Download
Publication Type
Journal Article
Authorship
Saifullah, C. K., Asaduzzaman, M., & Roy, C. K.
Title
Learning from examples to find fully qualified names of api elements in code snippets
Year
2019
Publication Outlet
In 2019 34th IEEE/ACM International Conference on Automated Software Engineering (ASE) (pp. 243-254). IEEE
DOI
https://doi.org/10.1109/ASE.2019.00032
Citation
Saifullah, C. K., Asaduzzaman, M., & Roy, C. K. (2019). Learning from examples to find fully qualified names of api elements in code snippets. In 2019 34th IEEE/ACM International Conference on Automated Software Engineering (ASE) (pp. 243-254). IEEE. https://doi.org/10.1109/ASE.2019.00032
Abstract
Developers often reuse code snippets from online forums, such as Stack Overflow, to learn API usages of software frameworks or libraries. These code snippets often contain ambiguous undeclared external references. Such external references make it difficult to learn and use those APIs correctly. In particular, reusing code snippets containing such ambiguous undeclared external references requires significant manual efforts and expertise to resolve them. Manually resolving fully qualified names (FQN) of API elements is a non-trivial task. In this paper, we propose a novel context-sensitive technique, called COSTER, to resolve FQNs of API elements in such code snippets. The proposed technique collects locally specific source code elements as well as globally related tokens as the context of FQNs, calculates likelihood scores, and builds an occurrence likelihood dictionary (OLD). Given an API element as a query, COSTER captures the context of the query API element, matches that with the FQNs of API elements stored in the OLD, and rank those matched FQNs leveraging three different scores: likelihood, context similarity, and name similarity scores. Evaluation with more than 600K code examples collected from GitHub and two different Stack Overflow datasets shows that our proposed technique improves precision by 4-6% and recall by 3-22% compared to state-of-the-art techniques. The proposed technique significantly reduces the training time compared to the StatType, a state-of-the-art technique, without sacrificing accuracy. Extensive analyses on results demonstrate the robustness of the proposed technique.
Program Affiliations
GWF: Global Water Futures
Publication Stage
Published
Download Links
https://doi.org/10.1109/ASE.2019.00032
© 2026 - WaterNet Version 2026-08-06
Global Water Futures Observatories
Powered by
G W F Net
T-2022-12-05-31Rb33SGkzz0qN9jH8yfG86A Publication 1.0