EDBT 2026 Demo / reviewers in the wild / expert
Johannes Reisinger
dblp:57/3018
· DBLP profile ↗
3ranked-venue papers
0as first author
0since 2021 · last 1993
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Applied, interdisciplinary, general and emerging computing · 2
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.
| Computer architecture, parallel and distributed computing, and storage systems
2 papers |
Embedded and real-time systems · 66% Distributed systems · 19% Electronic design automation · 15% | |
| Software engineering, system software, and programming languages
1 paper |
Concurrent programming · 100% |
Topics — the 8 heaviest of 8, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Embedded and real-time systems
real-time scheduling |
0.0 | 1 | 1993 | The Non-Blocking Write Protocol NBW: A Solution to a Real-Time Synchronisation Problem · RTSS 1993 |
Embedded and real-time systems
real-time synchronization |
0.0 | 1 | 1993 | The Non-Blocking Write Protocol NBW: A Solution to a Real-Time Synchronisation Problem · RTSS 1993 |
Embedded and real-time systems › real-time scheduling
schedulability analysis |
0.0 | 1 | 1993 | The Non-Blocking Write Protocol NBW: A Solution to a Real-Time Synchronisation Problem · RTSS 1993 |
Electronic design automation
design methodology |
0.0 | 1 | 1992 | The programmer's view of MARS · RTSS 1992 |
Distributed systems › fault tolerance
fault-tolerant real-time systems |
0.0 | 1 | 1992 | The programmer's view of MARS · RTSS 1992 |
Embedded and real-time systems
real-time system design |
0.0 | 1 | 1992 | The programmer's view of MARS · RTSS 1992 |
Concurrent programming
synchronization |
0.0 | 1 | 1993 | The Non-Blocking Write Protocol NBW: A Solution to a Real-Time Synchronisation Problem · RTSS 1993 |
Distributed systems
fault tolerance |
0.0 | 1 | 1992 | The programmer's view of MARS · RTSS 1992 |
Methods — techniques the papers use, named apart from their topics
schedulability analysis · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1993 | Real-time system development: The programming model of MARSabstractThe systematic development of fault-tolerant real-time systems with guaranteed timeliness requires an appropriate system architecture and a rigorous design methodology. Those services of the architecture that help to simplify the work of the real-time programmer are described, taking the MARS architecture as an example. Programming in the large activities, i.e., the systematic derivation of task timing parameters from the requirements specification, are then addressed. Programming to meet a time budget is discussed, and the programming interface, the programming environment, and the testing and support tools are presented. The architecture and most of the tools have been implemented and can be demonstrated on a fault-tolerant prototype application.> Hermann Kopetz, Gerhard Fohler, Günter Grünsteidl, Heinz Kantz, Gustav Pospischil, Peter P. Puschner, Johannes Reisinger, Ralf Schlatterbeck, Werner Schütz, Alexander Vrchoticky, Ralph Zainlinger |
ISADS | 7 |
| 1993 | The Non-Blocking Write Protocol NBW: A Solution to a Real-Time Synchronisation ProblemabstractThe synchronization problem between a communication controller writing a data structure into a common memory and a set of concurrently executing real-time tasks reading this data structure is investigated. Two versions of an adaptable new non-blocking protocol are presented and a schedulability analysis for a task set using these protocols is given.> Hermann Kopetz, Johannes Reisinger |
RTSS | 2 |
| 1992 | The programmer's view of MARSabstractThe authors propose a system architecture, MARS, which supports a strict separation of the issues of synchronization and timeliness, data transformation, and the dependability aspects (e.g., error detection, error handling, and redundancy management. The systematic development of fault-tolerant real-time systems with guaranteed timeliness requires an appropriate system architecture and a rigorous design methodology. The authors propose a system with strict separation of the issues of synchronization, dependability aspects, and data transformation. Dependability aspects are handled by the architecture. Synchronization and programming in the large are handled at the design level. The programmer only has to be concerned with a sequential program for which he has to meet a so-called time budget. The architecture and many tools have been implemented and can be demonstrated on a fault-tolerant prototype application.> Hermann Kopetz, Gerhard Fohler, Günter Grünsteidl, Heinz Kantz, Gustav Pospischil, Peter P. Puschner, Johannes Reisinger, Ralf Schlatterbeck, Werner Schütz, Alexander Vrchoticky, Ralph Zainlinger |
RTSS | 7 |