Demo Data from EDBT 2026 / reviewers in the wild / expert
Mathieu Sicard
dblp:167/0211
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2015
—ORCID · unresolved
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 · 100% | |
| Databases, data mining, and information retrieval
1 paper |
Information retrieval · 100% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution
software documentation |
0.2 | 1 | 2015 | TaskNav: Task-Based Navigation of Software Documentation · ICSE (2) 2015 |
Information retrieval
search interfaces |
0.1 | 1 | 2015 | TaskNav: Task-Based Navigation of Software Documentation · ICSE (2) 2015 |
Methods — techniques the papers use, named apart from their topics
task description extraction · 0.4auto-complete search · 0.4
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2015 | TaskNav: Task-Based Navigation of Software DocumentationabstractTo help developers navigate documentation, we introduce Task Nav, a tool that automatically discovers and indexes task descriptions in software documentation. With Task Nav, we conceptualize tasks as specific programming actions that have been described in the documentation. Task Nav presents these extracted task descriptions along with concepts, code elements, and section headers in an auto-complete search interface. Our preliminary evaluation indicates that search results identified through extracted task descriptions are more helpful to developers than those found through other means, and that they help bridge the gap between documentation structure and the information needs of software developers. Video: https://www.youtube.com/watch?v=opnGYmMGnqY. Christoph Treude, Mathieu Sicard, Marc Klocke, Martin P. Robillard |
ICSE (2) | 2 |