Demo Data from EDBT 2026 / reviewers in the wild / expert
Axel Rauschmayer
dblp:85/4687
· DBLP profile ↗
3ranked-venue papers
1as first author
0since 2021 · last 2004
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 3 · 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
3 papers |
Requirements engineering and software design · 69% Software maintenance and evolution · 14% Empirical software engineering · 14% |
Topics — the 8 heaviest of 8, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design › design process
stepwise refinement |
0.1 | 2 | 2004 | Scaling Step-Wise Refinement · IEEE Trans. Software Eng. 2004 Scaling Step-Wise Refinement · ICSE 2003 |
Requirements engineering and software design › inconsistency management
consistency checking |
0.0 | 1 | 2004 | Consistency Checking in an Infrastructure for Large-Scale Generative · ASE 2004 |
Requirements engineering and software design › software product lines
feature-oriented software development |
0.0 | 1 | 2004 | Scaling Step-Wise Refinement · IEEE Trans. Software Eng. 2004 |
Empirical software engineering
mining software repositories |
0.0 | 1 | 2004 | Consistency Checking in an Infrastructure for Large-Scale Generative · ASE 2004 |
Software maintenance and evolution
software ecosystems |
0.0 | 1 | 2004 | Consistency Checking in an Infrastructure for Large-Scale Generative · ASE 2004 |
Requirements engineering and software design
software product lines |
0.0 | 1 | 2003 | Scaling Step-Wise Refinement · ICSE 2003 |
Requirements engineering and software design
software architecture |
0.0 | 1 | 2004 | Scaling Step-Wise Refinement · IEEE Trans. Software Eng. 2004 |
Programming languages and type systems › specification language
algebraic specification |
0.0 | 1 | 2003 | Scaling Step-Wise Refinement · ICSE 2003 |
Methods — techniques the papers use, named apart from their topics
consistency checking · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2004 | Consistency Checking in an Infrastructure for Large-Scale Generative
Axel Rauschmayer, Alexander Knapp, Martin Wirsing |
ASE | 1 |
| 2004 | Scaling Step-Wise RefinementabstractStep-wise refinement is a powerful paradigm for developing a complex program from a simple program by adding features incrementally. We present the AHEAD (algebraic hierarchical equations for application design) model that shows how step-wise refinement scales to synthesize multiple programs and multiple noncode representations. AHEAD shows that software can have an elegant, hierarchical mathematical structure that is expressible as nested sets of equations. We review a tool set that supports AHEAD. As a demonstration of its viability, we have bootstrapped AHEAD tools from equational specifications, refining Java and nonJava artifacts automatically; a task that was accomplished only by ad hoc means previously. Don S. Batory, Jacob Neal Sarvela, Axel Rauschmayer |
IEEE Trans. Software Eng. | 3 |
| 2003 | Scaling Step-Wise RefinementabstractStep-wise refinement is a powerful paradigm for developing a complex program from a simple program by adding features incrementally. We present the AHEAD (Algebraic Hierarchical Equations for Application Design) model that shows how step-wise refinement scales to synthesize multiple programs and multiple non-code representations. AHEAD shows that software can have an elegant, hierarchical mathematical structure that is expressible as nested sets of equations. We review a tool set that supports AHEAD. As a demonstration of its viability, we have bootstrapped AHEAD tools solely from equational specifications, generating Java and non-Java artifacts automatically, a task that was accomplished only by ad hoc means previously. Don S. Batory, Jacob Neal Sarvela, Axel Rauschmayer |
ICSE | 3 |