Demo Data from EDBT 2026 / reviewers in the wild / expert
Fred M. Tonge
dblp:63/4288
· DBLP profile ↗
3ranked-venue papers
0as first author
0since 2021 · last 1988
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1Software engineering, systems software and programming languages · 1Databases, data management, data science and information retrieval · 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.
| Computer architecture, parallel and distributed computing, and storage systems
2 papers |
Electronic design automation · 54% Storage systems · 36% Distributed systems · 11% | |
| Software engineering, system software, and programming languages
1 paper |
Compilers and program optimization · 100% |
Topics — the 2 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Electronic design automation › design data management
design database |
0.0 | 1 | 1988 | A Context Mechanism to Control Sharing in a Design Database · DAC 1988 |
Compilers and program optimization › memory optimization
data representation selection |
0.0 | 1 | 1978 | Automating the Selection of Implementation Structures · IEEE Trans. Software Eng. 1978 |
Methods — techniques the papers use, named apart from their topics
pattern recognition · 0.0library retrieval · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1988 | A Context Mechanism to Control Sharing in a Design Database
Denise J. Ecklund, Fred M. Tonge |
DAC | 2 |
| 1987 | DVSS: A Distributed Version Storage Server for CAD Applications
Denise J. Ecklund, Earl F. Ecklund Jr., Robert O. Eifrig, Fred M. Tonge |
VLDB | 4 |
| 1978 | Automating the Selection of Implementation StructuresabstractAn approach to automating the selection of implementations for the data representations used in a program is presented. Formalisms are developed for specifying data representations and implementation structures. Using these formalisms, algorithms are presented which will recognize the use in a program of known data representations (e. g., stacks, queues, lists, arrays, etc.) so that alternative implementations can be retrieved from a library and which will, for those representations not recognized, generate alternative implementations with a wide range of space-time tradeoffs. Experience with using these algorithms indicates they are reasonably successful, although there are several problems that must be solved before automatic implementation selection systems will be practical. Lawrence A. Rowe, Fred M. Tonge |
IEEE Trans. Software Eng. | 2 |