Demo Data from SIGIR 2026 / reviewers in the wild / expert
Frank Dixon Whitworth
dblp:337/0949
· DBLP profile ↗
1ranked-venue papers
1as first author
1since 2021 · last 2022
0000-0002-6674-2803ORCID · reported
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 testing · 56% Program analysis · 44% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Program analysis
dynamic analysis |
0.6 | 1 | 2022 | Execution Path Detection through Dynamic Analysis in Black-Box Testing Environments · ASE 2022 |
Software testing › test coverage
path coverage |
0.6 | 1 | 2022 | Execution Path Detection through Dynamic Analysis in Black-Box Testing Environments · ASE 2022 |
Software testing
test coverage |
0.2 | 1 | 2022 | Execution Path Detection through Dynamic Analysis in Black-Box Testing Environments · ASE 2022 |
Methods — techniques the papers use, named apart from their topics
binary analysis · 0.6
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2022 | Execution Path Detection through Dynamic Analysis in Black-Box Testing EnvironmentsabstractPath coverage is the process of measuring the fraction of execution paths that are taken during run-time in a software by a given set of inputs. It is commonly used to assess the stability, security, and functionality of an application; therefore, this is closely associated with software testing. Path coverage requires knowledge of the software’s source code (white-box testing), specifically the software’s potential execution paths; however, the problem becomes more challenging when the source code is not available and path coverage must be done using only the software’s binary code. This can occur if the software is a product, the software is a legacy system, or the source code is not available (e.g. contracted software or permission-less). Frank Dixon Whitworth |
ASE | 1 |