Demo Data from VLDB 2026 / reviewers in the wild / expert
Tobias Kiecker
dblp:426/4328
· DBLP profile ↗
1ranked-venue papers
1as first author
1since 2021 · last 2025
—ORCID · unresolved
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-author · 1 since 2021
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 · 77% Software testing · 23% |
Topics — the 1 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution
artifact consistency |
0.9 | 1 | 2025 | Detecting and Mitigating Inconsistencies Between Code, Documentation and Tests · ASE 2025 |
Methods — techniques the papers use, named apart from their topics
regeneration-based triangulation · 0.9cross-validation · 0.9
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | Detecting and Mitigating Inconsistencies Between Code, Documentation and TestsabstractInconsistencies between different software artifacts, such as source code, documentation, and tests, are a common and long-standing problem in software engineering. These misalignments can degrade software quality, slow down development, and hinder maintenance. Each of these artifacts provides a distinct yet overlapping perspective of the same software behavior, forming a triangular relationship in which any one artifact can, in principle, be used to regenerate the others.In this PhD project, we aim to exploit these relationships through regeneration-based techniques to detect and ultimately mitigate inconsistencies across software artifacts. The approach focuses on building an SE-tool that leverages original and regenerated versions of artifacts to triangulate inconsistencies and improve reliability through cross-validation. A particular emphasis is placed on reducing false positives, ensuring that reported issues are trustworthy and actionable, especially when presented to developers in real-world projects. Tobias Kiecker |
ASE | 1 |