Demo Data from EDBT 2026 / reviewers in the wild / expert
Gary E. Anderson
dblp:08/3514
· DBLP profile ↗
1ranked-venue papers
1as 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 · 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% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Distributed systems · 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 › software architecture
architectural style |
0.0 | 1 | 2000 | Dragonfly: linking conceptual and implementation architectures of multiuser interactive systems · ICSE 2000 |
Requirements engineering and software design
software architecture |
0.0 | 1 | 2000 | Dragonfly: linking conceptual and implementation architectures of multiuser interactive systems · ICSE 2000 |
Distributed systems
distributed implementation |
0.0 | 1 | 2000 | Dragonfly: linking conceptual and implementation architectures of multiuser interactive systems · ICSE 2000 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2000 | Dragonfly: linking conceptual and implementation architectures of multiuser interactive systemsabstractSoftware architecture styles for developing multiuser applications are usually defined at a conceptual level, abstracting such low-level issues of distributed implementation as code replication, caching strategies and concurrency control policies. Ultimately, such conceptual architectures must be cast into code. The iterative design inherent in interactive systems implies that significant evolution will take place at the conceptual level. Equally, however, evolution occurs at the implementation level in order to tune performance. This paper introduces Dragonfly, a software architecture style that maintains a tight, bidirectional link between conceptual and implementation software architectures, allowing evolution to be performed at either level. Dragonfly has been implemented in the Java-based TeleComputing Developer (TCD) toolkit. Gary E. Anderson, T. C. Nicholas Graham, Timothy N. Wright |
ICSE | 1 |