Demo Data from EDBT 2026 / reviewers in the wild / expert
Charles Reynolds
dblp:68/2743
· DBLP profile ↗
5ranked-venue papers
3as first author
0since 2021 · last 2020
—ORCID · unresolved
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 2 · 2 first-authorArtificial intelligence and machine learning · 1Security and privacy · 1Databases, data management, data science and information retrieval · 1Human-computer interaction and ubiquitous computing · 1 · 1 first-author
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
2 papers |
Program verification · 100% | |
| Theoretical computer science
2 papers |
Logic in computer science · 67% Automated reasoning and model checking · 33% |
Topics — the 3 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Program verification › invariant generation
inductive assertions |
0.0 | 1 | 1976 | Induction as the Basis for Program Verification · IEEE Trans. Software Eng. 1976 |
Logic in computer science
proof theory |
0.0 | 2 | 1976 | Induction as the Basis for Program Verification · IEEE Trans. Software Eng. 1976 Induction as the Basis for Program Verification (Abstract) · ICSE 1976 |
Automated reasoning and model checking
inductive proof |
0.0 | 1 | 1976 | Induction as the Basis for Program Verification · IEEE Trans. Software Eng. 1976 |
Methods — techniques the papers use, named apart from their topics
subgoal induction · 0.0structural induction · 0.0predicate transformers · 0.0inductive assertions · 0.0computation induction · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2020 | To Ensemble or Not Ensemble: When Does End-to-End Training Fail?
Andrew M. Webb 0002, Charles Reynolds, Henry W. J. Reeve, Dan-Andrei Iliescu, Mikel Luján, Gavin Brown 0001 |
ECML/PKDD (3) | 2 |
| 1999 | Information Security Education for the Next Millennium: Building the Next Generation of Practitioners (Forum)
Ron Ross, Cynthia E. Irvine, Charles Reynolds, Ravi S. Sandhu, Blaine Burnham, Rayford B. Vaughn |
ACSAC | 3 |
| 1996 | Requirements for a computer science curriculum emphasizing information technology: subject area curriculum issuesabstractThe landscape of computing has changed dramatically for computing users, We routinely hear about the information superhighway, world-wide web and the Internet, multimedia, virtual reality, electronic mail and bulletin boards, groupware, desktop publishing, expert systems and knowledge engineering.Dramatically, these are not topics discussed exclusively by computer scientists and other kinds of computing specialists.These topics are Charles Reynolds, Christopher J. Fox |
SIGCSE | 1 |
| 1976 | Induction as the Basis for Program Verification (Abstract)
Charles Reynolds, Raymond T. Yeh |
ICSE | 1 |
| 1976 | Induction as the Basis for Program VerificationabstractWe will consider the inductive mechanisms in five techniques for verifying iterative/recursive program structures: inductive assertion, predicate transformers, subgoal induction, computation induction, and structural induction. We will discover that all five techniques can be justified by a single theorem about inductive proof techniques. We will also show that all five techniques face the problem of finding properties that will carry an induction. Such properties are called inductive sets. We will see that the inductive sets of the five techniques are easily related to one another and that a program proof by any of the techniques can be easily converted to a proof by any of the other techniques. Our conclusion is that computer programs simply are inductive definitions of the functions they compute. Induction is the only method by which they can be proved. The problems of induction are therefore unavoidable. Charles Reynolds, Raymond T. Yeh |
IEEE Trans. Software Eng. | 1 |