Demo Data from EDBT 2026 / reviewers in the wild / expert
Dwight F. Hare
dblp:85/6841
· 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 |
Requirements engineering and software design · 44% Program verification · 44% Software maintenance and evolution · 13% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design
software architecture |
0.0 | 1 | 1986 | The PegaSys System: Pictures as Formal Documentation of Large Programs · ACM Trans. Program. Lang. Syst. 1986 |
Software maintenance and evolution
software documentation |
0.0 | 1 | 1986 | The PegaSys System: Pictures as Formal Documentation of Large Programs · ACM Trans. Program. Lang. Syst. 1986 |
Methods — techniques the papers use, named apart from their topics
logical reasoning · 0.0hierarchical refinement · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1986 | The PegaSys System: Pictures as Formal Documentation of Large ProgramsabstractPegsSys is an experimental system in which a user formally describes how a program is put together by means of a hierarchically structured collection of pictures, called formal dependency diagrams (FDDs). Icons in an FDD denote a wide range of data and control dependencies among the relatively coarse-grained entities contained in large programs. Dependencies considered atomic with respect to one level in a hierarchy can be decomposed into a number of dependencies at a lower level. Each dependency can be a predefined primitive of the FDD language or it can be defined by a PegaSys user in terms of the primitives. A PegsSys user is given the illusion that logical formulas do not exist, even though PegaSys reasons about them internally. This involves (1) checking whether an FDD is meaningful syntactically, (2) determining whether hierarchical refinements of an FDD are methodologically sound, and (3) deciding whether an FDD hierarchy is logically consistent with the program that it is intended to describe. The techniques used to provide these capabilities are discussed along with the logical properties that enable PegaSys to maintain the user illusion. Mark Moriconi, Dwight F. Hare |
ACM Trans. Program. Lang. Syst. | 2 |