1993
DOI: 10.1109/2.231276
|View full text |Cite
|
Sign up to set email alerts
|

A systematic approach to designing distributed real-time systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
14
0

Year Published

1994
1994
2014
2014

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 54 publications
(14 citation statements)
references
References 10 publications
0
14
0
Order By: Relevance
“…In particular, GRM is claimed to be applicable to distributed systems. As (unvoluntarily) demonstrated in [22], such claims are unfounded. The unsolvable problem faced with GRM is that there cannot exist a method that could be used off-line to transform the deadlines into fixed priorities, while demonstrating that the transformed problem is equivalent to [HRTDM] or without violating [cc2].…”
Section: ]mentioning
confidence: 99%
See 1 more Smart Citation
“…In particular, GRM is claimed to be applicable to distributed systems. As (unvoluntarily) demonstrated in [22], such claims are unfounded. The unsolvable problem faced with GRM is that there cannot exist a method that could be used off-line to transform the deadlines into fixed priorities, while demonstrating that the transformed problem is equivalent to [HRTDM] or without violating [cc2].…”
Section: ]mentioning
confidence: 99%
“…The unsolvable problem faced with GRM is that there cannot exist a method that could be used off-line to transform the deadlines into fixed priorities, while demonstrating that the transformed problem is equivalent to [HRTDM] or without violating [cc2]. It is in fact easy to demonstrate that GRM cannot solve general distributed scheduling problems, contrary to the claims made in [22]. GRM is a typicM example of an approach based on an artificially restrictive view of reality (see section 4.1).…”
Section: ]mentioning
confidence: 99%
“…The execution times of all the jobs are known except for J 3 . Its execution time can be any value in the range [2,8]. Parts (b), (c) and (d) of this figure show the maximal, minimal and actual schedules, respectively.…”
Section: Arbitrary Release Time Casementioning
confidence: 99%
“…Consequently, it is impractical and unreliable to validate that all jobs meet their deadlines using exhaustive testing and simulation when their execution times and release times may vary. Recently, several efficient and analytical methods for validating timing constraints of static multiprocessor and distributed systems have been developed, e.g., [2,3,4] (In a static system, jobs are assigned and bound to processors.). These methods are based on worst-case bounds and schedulability conditions for uniprocessor systems [5,6,7,8].…”
Section: Introductionmentioning
confidence: 99%
“…A number of methods for modeling the real-time behavior of dataflow applications have been developed for multiprocessor and distributed systems [4,12,15,23]. Typically, such applications are modeled as directed acyclic graphs (DAGs), with nodes denoting tasks and edges denoting producer/consumer relationships.…”
Section: Introductionmentioning
confidence: 99%