Demo Data from EDBT 2026 / reviewers in the wild / expert
Jens Wiemann
dblp:222/5894
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2018
—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 |
Empirical software engineering · 77% Software maintenance and evolution · 23% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering
developer studies |
0.3 | 1 | 2018 | Do you remember this source code? · ICSE 2018 |
Software maintenance and evolution
program comprehension |
0.1 | 1 | 2018 | Do you remember this source code? · ICSE 2018 |
Methods — techniques the papers use, named apart from their topics
version control system data extraction · 0.3survey · 0.3
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2018 | Do you remember this source code?abstractBeing familiar with the source code of a program comprises knowledge about its purpose, structure, and details. Consequently, familiarity is an important factor in many contexts of software development, especially for maintenance and program comprehension. As a result, familiarity is considered to some extent in many different approaches, for example, to model costs or to identify experts. Still, all approaches we are aware of require a manual assessment of familiarity and empirical analyses of forgetting in software development are missing. In this paper, we address this issue with an empirical study that we conducted with 60 open-source developers. We used a survey to receive information on the developers' familiarity and analyze the responses based on data we extract from their used version control systems. The results show that forgetting is an important factor when considering familiarity and program comprehension of developers. We find that a forgetting curve is partly applicable for software development, investigate three factors - the number of edits, ratio of owned code, and tracking behavior - that can impact familiarity with code, and derive a general memory strength for our participants. Our findings can be used to scope approaches that have to consider familiarity and they provide insights into forgetting in the context of software development. Jacob Krüger, Jens Wiemann, Wolfram Fenske, Gunter Saake, Thomas Leich |
ICSE | 2 |