Demo Data from EDBT 2026 / reviewers in the wild / expert
Alireza Mollaalizadehbahnemiri
dblp:245/7543
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2019
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Software maintenance and evolution · 56% Empirical software engineering · 44% | |
| Artificial intelligence
1 paper |
Information extraction and text analysis · 100% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Natural language and speech › Information extraction and text analysis
text classification |
0.4 | 1 | 2019 | On using machine learning to identify knowledge in API reference documentation · ESEC/SIGSOFT FSE 2019 |
Software maintenance and evolution › software documentation
API documentation analysis |
0.4 | 1 | 2019 | On using machine learning to identify knowledge in API reference documentation · ESEC/SIGSOFT FSE 2019 |
Empirical software engineering
mining software repositories |
0.4 | 1 | 2019 | On using machine learning to identify knowledge in API reference documentation · ESEC/SIGSOFT FSE 2019 |
Software maintenance and evolution › software documentation
API documentation |
0.1 | 1 | 2019 | On using machine learning to identify knowledge in API reference documentation · ESEC/SIGSOFT FSE 2019 |
Methods — techniques the papers use, named apart from their topics
text classification · 0.8deep learning · 0.8SVM · 0.8k-NN · 0.4KNN · 0.4
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2019 | On using machine learning to identify knowledge in API reference documentationabstractUsing API reference documentation like JavaDoc is an integral part of software development. Previous research introduced a grounded taxonomy that organizes API documentation knowledge in 12 types, including knowledge about the Functionality, Structure, and Quality of an API. We study how well modern text classification approaches can automatically identify documentation containing specific knowledge types. We compared conventional machine learning (k-NN and SVM) with deep learning approaches trained on manually-annotated Java and .NET API documentation (n = 5,574). When classifying the knowledge types individually (i.e., multiple binary classifiers) the best AUPRC was up to 87 Davide Fucci, Alireza Mollaalizadehbahnemiri, Walid Maalej |
ESEC/SIGSOFT FSE | 2 |