Demo Data from VLDB 2026 / reviewers in the wild / expert
Christian Piwetz
dblp:09/5249
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 1998
—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 · 100% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Performance modeling and evaluation · 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 design |
0.0 | 1 | 1998 | On Detecting and Handling Inconsistencies in Integrating Software Architecture Design and Performance Evaluation · ASE 1998 |
Requirements engineering and software design
software architecture |
0.0 | 1 | 1998 | On Detecting and Handling Inconsistencies in Integrating Software Architecture Design and Performance Evaluation · ASE 1998 |
Performance modeling and evaluation › software performance engineering
software performance analysis |
0.0 | 1 | 1998 | On Detecting and Handling Inconsistencies in Integrating Software Architecture Design and Performance Evaluation · ASE 1998 |
Methods — techniques the papers use, named apart from their topics
graph-based approach · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1998 | On Detecting and Handling Inconsistencies in Integrating Software Architecture Design and Performance EvaluationabstractWe consider the problem of detecting and handling inconsistencies in software development processes using a graph based approach. It seems to be a natural way to express the various options and possibilities in attacking the problem. We apply the techniques developed in the area of software architecture design which uses in a structured way performance models in order to produce a design which incorporates also nonfunctional requirements in terms of quantitative performance. Michael Goedicke, Torsten Meyer, Christian Piwetz |
ASE | 3 |