Demo Data from VLDB 2026 / reviewers in the wild / expert
David G. Esp
dblp:83/884
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 1986
—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 |
Software testing · 56% Requirements engineering and software design · 44% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design › software process
software development methods |
0.0 | 1 | 1986 | PODS - A Project on Diverse Software · IEEE Trans. Software Eng. 1986 |
Software testing
software reliability |
0.0 | 1 | 1986 | PODS - A Project on Diverse Software · IEEE Trans. Software Eng. 1986 |
Software testing
fault detection |
0.0 | 1 | 1986 | PODS - A Project on Diverse Software · IEEE Trans. Software Eng. 1986 |
Methods — techniques the papers use, named apart from their topics
independent development · 0.0controlled experiment · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1986 | PODS - A Project on Diverse SoftwareabstractA review of the Project on Diverse Software (PODS), a collaborative software reliability research project, is presented. The purpose of the project was to determine the effect of a number of different software development techniques on software reliability. The main objectives were to evaluate the merits of using diverse software, evaluate the specification language X-SPEX, and compare the productivity and reliability associated with high-level and low-level languages. A secondary objective was to monitor the software development process, with particular reference to the creation and detection of software faults. To achieve these objectives, an experiment was performed which simulated a normal software development process to produce three diverse programs to the same requirement. The requirement was for a reactor over-power protection (trip) system. After careful independent development and testing, the three programs were tested against each other in a special test harness to locate residual faults. The conclusions drawn from this project are discussed. Peter Bishop 0001, David G. Esp, Mel Barnes, Peter Humphreys, Gustav Dahll, Jaakko Lahti |
IEEE Trans. Software Eng. | 2 |