How Can I Use This Method?
The DOI matches its Crossref record; 2 of the 2 references it cites were found in a registry or an index.
Abstract
Code examples are small source code fragments whose purpose is to illustrate how a programming language construct, an API, or a specific function/method works. Since code examples are not always available in the software documentation, researchers have proposed techniques to automatically extract them from existing software or to mine them from developer discussions. In this paper we propose MUSE (Method USage Examples), an approach for mining and ranking actual code examples that show how to use a specific method. MUSE combines static slicing (to simplify examples) with clone detection (to group similar examples), and uses heuristics to select and rank the best examples in terms of reusability, understandability, and popularity. MUSE has been empirically evaluated using examples mined from six libraries, by performing three studies involving a total of 140 developers to: (i) evaluate the selection and ranking heuristics, (ii) provide their perception on the usefulness of the selected examples, and (iii) perform specific programming tasks using the MUSE examples. The results indicate that MUSE selects and ranks examples close to how humans do, most of the code examples (82%) are perceived as useful, and they actually help when performing programming tasks.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Learning a Metric for Code Readability
Buse, R. P. L., & Weimer, W. R. (2010) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2009.70 · Cited by 396 · cited 5×
“More recently, Buse and Weimer [6] proposed to generate documented abstract API usages by extracting and synthesizing code examples of a particular API data type.”
MethodInfluentialMining StackOverflow to turn the IDE into a self-confident programming prompter
Ponzanelli, L., Bavota, G., Di Penta, M., Oliveto, R., & Lanza, M. (2014) · Proceedings of the 11th Working Conference on Mining Software Repositories · doi:10.1145/2597073.2597077 · Cited by 240 · cited 5×
“Prompter [5] matches the generated query with Stack Overflow entries, to automatically push discussions relevant to the developers’ task at hand.”
BackgroundMethodInfluentialSelf-citation
Research works printed but not linked: 19
- moreno, 0, How can I use this method? The MUSE approach Replication package
- 10.1016/j.jss.2011.05.016 · DOI · Paper page
- harris, 0, Simian - Similarity Analyser
- 10.1016/j.scico.2009.02.007 · DOI · Paper page
- 10.1109/TSE.2002.1019480 · DOI · Paper page
- oppenheim, 1992, Questionnaire Design Interviewing and Attitude Measurement
- conover, 1998, Practical Nonparametric Statistics
- grissom, 2005, Effect Sizes for Research A Broad Practical Approach
- baker, 1995, Modern permutation test software, Randomization tests
- 10.1109/ICSE.2005.1553554 · DOI · Paper page
- chatterjee, 2009, SNIFF: A search engine for java using free-form queries, Fundamental Approaches to Software Engineering 12th International Conference FASE 2009 Held as Part of the Joint European Conferences on Theory and Practice of Software ETAPS 2009 York UK March 22–29 2009 Proceedings ser Lecture Notes in Computer Science, 385
- 10.1109/ICSE.2012.6227140 · DOI
- 10.1109/MSR.2013.6624045 · DOI · Paper page
- 10.1145/1137983.1137997 · DOI · Paper page
- 10.1145/1882291.1882316 · DOI
- 10.1145/2568225.2568292 · DOI · Paper page
- zhong, 2009, MAPO: mining and recommending API usage patterns, Proceedings of the 23rd European Conference on ECOOP 2009 ser Genoa, 318
- 10.1145/1287624.1287630 · DOI · Paper page
- 10.1145/2635868.2635877 · DOI
Cited by
Software Documentation Issues Unveiled
Aghajani, E., Nagy, C., Vega-Marquez, O. L., Linares-Vasquez, M., Moreno, L., Bavota, G., & Lanza, M. (2019) · 2019 IEEE/ACM 41st International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2019.00122 · Cited by 195
Self-citationAPI method recommendation without worrying about the task-API knowledge gap
Huang, Q., Xia, X., Xing, Z., Lo, D., & Wang, X. (2018) · Proceedings of the 33rd ACM/IEEE International Conference on Automated Software Engineering · doi:10.1145/3238147.3238191 · Cited by 192
“[28] proposed MUSE for mining and ranking actual code examples that show how to use a specific method.”
In-IDE Code Generation from Natural Language: Promise and Challenges
Xu, F. F., Vasilescu, B., & Neubig, G. (2021) · arXiv · doi:10.48550/arxiv.2101.11149 · Cited by 153
In-IDE Code Generation from Natural Language: Promise and Challenges
Xu, F. F., Vasilescu, B., & Neubig, G. (2022) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3487569 · Cited by 154
“[78], which retrieves usage examples that show how to use a specific method.”
BackgroundA comparison of code similarity analysers
Ragkhitwetsagul, C., Krinke, J., & Clark, D. (2018) · Empirical Software Engineering · doi:10.1007/s10664-017-9564-7 · Cited by 122
“Examples include finding similar bug fixes (Hartmann et al. 2010), identifying cross-cutting concerns (Bruntink et al. 2005), program comprehension (Maletic and Marcus 2001), code recommendation (Holmes and Murphy 2005), and example extraction (Moreno et al. 2015).”
BackgroundIronies of Generative AI: Understanding and Mitigating Productivity Loss in Human-AI Interaction
Simkute, A., Tankelevitch, L., Kewenig, V., Scott, A. E., Sellen, A., & Rintel, S. (2024) · International Journal of Human–Computer Interaction · doi:10.1080/10447318.2024.2405782 · Cited by 89
“It could also include more context and documentation with the output, e.g., links to Stack Overflow or official documentation pages (Xu et al., 2022), real-time information about libraries (Feuerriegel et al., 2024) or provide relevant usage examples (Moreno et al., 2015).”
A Study of Visual Studio Usage in Practice
Amann, S., Proksch, S., Nadi, S., & Mezini, M. (2016) · 2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER) · doi:10.1109/saner.2016.39 · Cited by 77
Supporting Software Developers with a Holistic Recommender System
Ponzanelli, L., Scalabrino, S., Bavota, G., Mocci, A., Oliveto, R., Di Penta, M., & Lanza, M. (2017) · 2017 IEEE/ACM 39th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2017.17 · Cited by 41
Self-citationUnveiling ChatGPT’s usage in open source projects: A mining-based study
Tufano, R., Mastropaolo, A., Pepe, F., Dabic, O., Di Penta, M., & Bavota, G. (2024) · Proceedings of the 21st International Conference on Mining Software Repositories · doi:10.1145/3643991.3644918 · Cited by 38
“…context” Over the years, researchers have developed various forms of recommenders, aimed at suggesting relevant code elements for a given task [44, 86, 111], helping to fix bugs [48, 81, 106, 114] and vulnerabilities [54, 68, 70], and even to automatically document software systems [43, 83, 100].”
BackgroundSelf-citationEvaluating the evaluations of code recommender systems: a reality check
Proksch, S., Amann, S., Nadi, S., & Mezini, M. (2016) · Proceedings of the 31st IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/2970276.2970330 · Cited by 26
“, [3,9,15,20]).”
BackgroundIronies of Generative AI: Understanding and mitigating productivity loss in human-AI interactions
Simkute, A., Tankelevitch, L., Kewenig, V., Scott, A. E., Sellen, A., & Rintel, S. (2024) · arXiv · doi:10.48550/arxiv.2402.11364 · Cited by 7
Metadata
- Authors
- Moreno, L., Bavota, G., Di Penta, M., Oliveto, R., & Marcus, A.
- Venue
- 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering
- Publisher
- IEEE
- Published
- 2015-05
- ISSN
- 0270-5257 (ISSN-L)
- OpenAlex
- W4241089335
- Cited by
- 125
- References
- 2
- FWCI
- 13.45
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.