Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Werner Schütz

dblp:90/95 · DBLP profile ↗
← Back
4ranked-venue papers
2as first author
0since 2021 · last 1994
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 1 · 1 first-authorSecurity and privacy · 1 · 1 first-authorApplied, interdisciplinary, general and emerging computing · 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.

Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 39% Embedded and real-time systems · 30% Electronic design automation · 30%

Topics — the 4 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Electronic design automation
design methodology
0.011992
The programmer's view of MARS · RTSS 1992
Distributed systems › fault tolerance
fault-tolerant real-time systems
0.011992
The programmer's view of MARS · RTSS 1992
Embedded and real-time systems
real-time system design
0.011992
The programmer's view of MARS · RTSS 1992
Distributed systems
fault tolerance
0.011992
The programmer's view of MARS · RTSS 1992
YearPublicationVenuePosition
1994 Fundamental Issues in Testing Distributed Real-Time Systems
Werner Schütz
Real Time Syst.1
1993 Real-time system development: The programming model of MARS
abstract
The 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
ISADS9
1992 The programmer's view of MARS
abstract
The 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
RTSS9
1991 On the Testability of Distributed Real-Time Systems
abstract
Event-triggered and time-triggered systems are compared with respect to their testability. To facilitate the comparison, three aspects of testability are introduced: test coverage, observability, and controllability. After a brief review of the problems of testing concurrent programs, the author compares the two system architectures with respect to each of these three aspects. The results of the comparisons favor time-triggered systems in all three aspects, most notably with respect to controllability and test coverage. Thus, time-triggered systems are inherently more testable than event-triggered systems. A series of experiments is summarized that shows that it is easy to achieve reproducible testing of time-triggered systems.>
Werner Schütz
SRDS1