Demo Data from EDBT 2026 / reviewers in the wild / expert
Heinrich Jasper
dblp:j/HeinrichJasper
· DBLP profile ↗
2ranked-venue papers
1as first author
0since 2021 · last 1996
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 2 · 1 first-authorArtificial intelligence and machine learning · 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.
| Databases, data mining, and information retrieval
1 paper |
Database system architecture and tuning · 100% | |
| Software engineering, system software, and programming languages
1 paper |
Requirements engineering and software design · 100% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Database system architecture and tuning
active database |
0.0 | 1 | 1994 | Active Databases for Active Repositories · ICDE 1994 |
Requirements engineering and software design › software process
software process modeling |
0.0 | 1 | 1994 | Active Databases for Active Repositories · ICDE 1994 |
Methods — techniques the papers use, named apart from their topics
repository triggers · 0.0event-condition-action rules · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1996 | Case Studies on Active Database Applications
Hans-Jürgen Appelrath, Helge Behrends, Heinrich Jasper, Olaf Zukunft |
DEXA | 3 |
| 1994 | Active Databases for Active RepositoriesabstractThe various activities necessary for constructing a software product are described by software process models. Many of the actions mentioned there are supported by tools that use a repository in order to create, manipulate, generate, etc. the deliverables. The process is tailored for each project to necessary work and planned with respect to existing resources. This results in a schedule for each project that is manually compared with ongoing work. We introduce the idea of active repositories that partially automate scheduling and controlling of the activities described within a process model. The notion of active repositories is based on active database technology that allows for detecting events and triggering the corresponding actions. Events are state changes in the repository or raised by external components, e.g. a clock or CASE tool. Actions manipulate the repository, trigger CASE tools, signal external systems or notify the user.> Heinrich Jasper |
ICDE | 1 |