Demo Data from EDBT 2026 / reviewers in the wild / expert
Peter R. Harvey
dblp:86/464
· DBLP profile ↗
2ranked-venue papers
0as first author
0since 2021 · last 1983
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 2
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 |
Compilers and program optimization · 100% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Embedded and real-time systems · 100% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Compilers and program optimization › intermediate representation
static single assignment form |
0.0 | 1 | 1983 | Analyzing Software Safety · IEEE Trans. Software Eng. 1983 |
Embedded and real-time systems › real-time embedded systems
safety-critical real-time systems |
0.0 | 1 | 1983 | Analyzing Software Safety · IEEE Trans. Software Eng. 1983 |
Methods — techniques the papers use, named apart from their topics
fault tree analysis · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1983 | Software fault tree analysis
Nancy G. Leveson, Peter R. Harvey |
J. Syst. Softw. | 2 |
| 1983 | Analyzing Software SafetyabstractWith the increased use of software controls in critical realtime applications, a new dimension has been introduced into software reliability–the "cost" of errors. The problems of safety have become critical as these applcations have increasingly included areas where the consequences of failure are serious and may involve grave dangers to human life and property. This paper defines software safety and describes a technique called software fault tree analysis which can be used to analyze a design as to its safety. The technique has been applied to a program which controls the flight and telemetry for a University of California spacecraft. A critical failure scenario was detected by the technique which had not been revealed during substantial testing of the program. Parts of this analysis are presented as an example of the use of the technique and the results are discussed. Nancy G. Leveson, Peter R. Harvey |
IEEE Trans. Software Eng. | 2 |