Demo Data from EDBT 2026 / reviewers in the wild / expert
Hao-Nan Zhu
dblp:278/4470
· DBLP profile ↗
3ranked-venue papers
1as first author
2since 2021 · last 2023
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 2 · 1 first-author · 2 since 2021Security and privacy · 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 · 100% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering › mining software repositories
defect datasets |
0.7 | 1 | 2023 | On the Reproducibility of Software Defect Datasets · ICSE 2023 |
Empirical software engineering
mining software repositories |
0.7 | 1 | 2023 | On the Reproducibility of Software Defect Datasets · ICSE 2023 |
Empirical software engineering
reproducibility |
0.7 | 1 | 2023 | On the Reproducibility of Software Defect Datasets · ICSE 2023 |
Methods — techniques the papers use, named apart from their topics
dependency caching · 0.7artifact isolation · 0.7
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2023 | On the Reproducibility of Software Defect DatasetsabstractSoftware defect datasets are crucial to facilitating the evaluation and comparison of techniques in fields such as fault localization, test generation, and automated program repair. However, the reproducibility of software defect artifacts is not immune to breakage. In this paper, we conduct a study on the reproducibility of software defect artifacts. First, we study five state-of-the-art Java defect datasets. Despite the multiple strategies applied by dataset maintainers to ensure reproducibility, all datasets are prone to breakages. Second, we conduct a case study in which we systematically test the reproducibility of 1,795 software artifacts during a 13-month period. We find that 62.6% of the artifacts break at least once, and 15.3% artifacts break multiple times. We manually investigate the root causes of breakages and handcraft 10 patches, which are automatically applied to 1,055 distinct artifacts in 2,948 fixes. Based on the nature of the root causes, we propose automated dependency caching and artifact isolation to prevent further breakage. In particular, we show that isolating artifacts to eliminate external dependencies increases reproducibility to 95% or higher, which is on par with the level of reproducibility exhibited by the most reliable manually curated dataset. Hao-Nan Zhu, Cindy Rubio-González |
ICSE | 1 |
| 2023 | An empirical study on real bug fixes from solidity smart contract projects
Yilin Wang 0026, Xiangping Chen, Yuan Huang 0002, Hao-Nan Zhu, Jing Bian, Zibin Zheng |
J. Syst. Softw. | 4 |
| 2020 | Deciphering Cryptocurrencies by Reverse Analyzing on Smart Contracts
Xiangping Chen, Queping Kong, Hao-Nan Zhu, Yuan Huang 0002, Zigui Jiang |
BlockSys | 3 |