Demo Data from EDBT 2026 / reviewers in the wild / expert
L. Beth Protsko
dblp:97/2851
· DBLP profile ↗
1ranked-venue papers
1as first author
0since 2021 · last 1991
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-author
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 · 100% |
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
computer-aided software engineering |
0.0 | 1 | 1991 | Towards the Automatic Generation of Software Diagrams · IEEE Trans. Software Eng. 1991 |
Requirements engineering and software design
model-driven engineering |
0.0 | 1 | 1991 | Towards the Automatic Generation of Software Diagrams · IEEE Trans. Software Eng. 1991 |
Requirements engineering and software design
software architecture |
0.0 | 1 | 1991 | Towards the Automatic Generation of Software Diagrams · IEEE Trans. Software Eng. 1991 |
Methods — techniques the papers use, named apart from their topics
placement and routing algorithms · 0.0graph layout · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1991 | Towards the Automatic Generation of Software DiagramsabstractThe authors formulate the criteria for drawing dataflow diagrams and describe the placement and routing algorithms used in a system called MONDRIAN. A generalized approach to the question of software diagrams is proposed based on the authors' experience with MONDRIAN and a metasystem approach to the creation of CASE (computer-aided software engineering) environments. A formal approach to the definition of software objects and their graphical representation is given. The use of location constraints as a basis for generalized layout algorithms is discussed.> L. Beth Protsko, Paul G. Sorenson, J. Paul Tremblay, Douglas A. Schaefer |
IEEE Trans. Software Eng. | 1 |