A debugger for concurrent programs
Software—Practice & Experience
A Hybrid Monitor for Behavior and Performance Analysis of Distributed Systems
IEEE Transactions on Software Engineering
Software testing techniques (2nd ed.)
Software testing techniques (2nd ed.)
Black-box testing: techniques for functional testing of software and systems
Black-box testing: techniques for functional testing of software and systems
Consistent global states of distributed systems: fundamental concepts and mechanisms
Distributed systems (2nd Ed.)
Real time and dependability concepts
Distributed systems (2nd Ed.)
Time, clocks, and the ordering of events in a distributed system
Communications of the ACM
DeeDS towards a distributed and active real-time database system
ACM SIGMOD Record
The Testability of Distributed Real-Time Systems
The Testability of Distributed Real-Time Systems
Petri Net Theory and the Modeling of Systems
Petri Net Theory and the Modeling of Systems
Active and Real-Time Database Systems (ARTDB-95): Proceedings of the First International Workshop on Active and Real-Time Database Systems: Skovde, Sweden, 9-11 June 1995
Replication Techniques in Distributed Systems
Replication Techniques in Distributed Systems
Main Memory Database Systems: An Overview
IEEE Transactions on Knowledge and Data Engineering
Building an Integrated Active OODBMS: Requirements, Architecture, and Design Decisions
ICDE '95 Proceedings of the Eleventh International Conference on Data Engineering
A taxonomy of correctness criteria in database applications
The VLDB Journal — The International Journal on Very Large Data Bases
| Hi-index | 0.00 |
Event-triggered distributed real-time systems are prohibitively difficult to test due the required test effort. The test effort includes instrumenting the test object, and generating, executing, and analyzing the test results. The test effort can be significantly reduced by the use of an distributed active real-time database, thanks to the transaction concept and the built-in event monitor. The two major problems identified w.r.t. testing are the following. Firstly, whether the test effort is manageable. Secondly, whether the introduced run-time overhead is acceptable, i.e., no critical deadlines are missed due to testing.