Demo Data from EDBT 2026 / reviewers in the wild / expert
Andy Pryor
dblp:89/4121
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2000
—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 |
Requirements engineering and software design · 38% Software testing · 38% Program verification · 23% |
Topics — the 3 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design
formal specification |
0.0 | 1 | 2000 | Is Proof More Cost-Effective Than Testing? · IEEE Trans. Software Eng. 2000 |
Program verification
theorem proving |
0.0 | 1 | 2000 | Is Proof More Cost-Effective Than Testing? · IEEE Trans. Software Eng. 2000 |
Program verification › deductive verification
verification condition generation |
0.0 | 1 | 2000 | Is Proof More Cost-Effective Than Testing? · IEEE Trans. Software Eng. 2000 |
Methods — techniques the papers use, named apart from their topics
z notation · 0.0verification condition generation · 0.0formal proof · 0.0SPARK Ada · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2000 | Is Proof More Cost-Effective Than Testing?abstractThe paper describes the use of formal development methods on an industrial safety-critical application. The Z notation was used for documenting the system specification and part of the design, and the SPARK subset of Ada was used for coding. However, perhaps the most distinctive nature of the project lies in the amount of proof that was carried out: proofs were carried out both at the Z level (approximately 150 proofs in 500 pages) and at the SPARK code level (approximately 9000 verification conditions generated and discharged). The project was carried out under UK Interim Defence Standards 00-55 and 00-56, which require the use of formal methods on safety-critical applications. It is believed to be the first to be completed against the rigorous demands of the 1991 version of these standards. The paper includes comparisons of proof with the various types of testing employed, in terms of their efficiency at finding faults. The most striking result is that the Z proof appears to be substantially more efficient at finding faults than the most efficient testing phase. Given the importance of early fault detection, we believe this helps to show the significant benefit and practicality of large-scale proof on projects of this kind. Steve King 0001, Jonathan Hammond, Roderick Chapman, Andy Pryor |
IEEE Trans. Software Eng. | 4 |