M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour. A Practitioner 's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993.  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... fresh inputs. It is not at all obvious that the software architecture meets its deadline requirements. In this section, we perform a formal analysis to check whether this is the case. We use results from real time scheduling theory, in particular, xed priority scheduling theory (e.g. see [8, 7, 5, 14, 1, 2, 15]) and the so called HKL model and analysis [3, 4] First, we cast the platoon application into the formal model. Then, we estimate the execution times and other latencies involved in the system, and compute the total CPU utilization. This is found to be about 74 , that is, less than 1, which is a ....

....are inversely proportional to task periods. In fact this is an optimal xed priority policy, in the sense that if the tasks are schedulable with any other xed priority policy then they are also schedulable with the rate monotonic policy [8] By performing the so called completion time test [7, 5, 6]. This is an exact test, that is, tasks are schedulable if and only if they pass the test. We brie y describe the completion time test for the simple model and then show how it is extended for the model of tasks with more than one sub tasks. We try to make our description self contained, although ....

[Article contains additional citation context not shown here]

M.G. Harbour, M.H. Klein, R. Obenza, B. Pollak, and T. Ralya. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate-Monotonic Analysis for Real-Time Systems. Kluwer, 1993.

....to ensure predictable execution, including upgrades of software components during system operation. A full description of RMS is beyond the scope of this paper. For a general introduction, see the article by Sha and Goodenough [Sha 90] A practitioner s guide is available in the book by Klein [Klein 93] RMS Theory was applied to the Coordinated Prototype to ensure that the pendulums continue to meet al..l real time constraints in their operation even in the presence of faults. Under RMS, higher frequency tasks are assigned higher priorities. Within the same frequency, ties can be broken ....

Klein, M. H.; Ralya, T.; Pollak, B.; Obenza, R.; & Harbour, M. G. A Practitioner's Handbook for Real-Time Analysis: Guide to RateMonotonic Analysis for Real-Time Systems. Kluser Academic Publishers, 1993. ISBN 0-7923-9361-9.

....are more general purpose than the synchronous languages mentioned above. Implementation of asynchronous languages typically relies on an operating system. The latter is responsible for scheduling, which is usually based on static priorities. Real time scheduling theory (e.g. 11] 12] [18], and [32] provides techniques, such as rate monotonic analysis [26] that guarantee satisfaction of simple time constraints, such as deadlines. Unfortunately, these results are often applicable only to simple models, and are difficult to generalize. Neither of the two paradigms faces the ....

M. G. Harbour, M. H. Klein, R. Obenza, B. Pollak, and T. Ralya, A Practitioner's Handbook for Real-Time Analysis: Guide to Rate-Monotonic Analysis for Real-Time Systems. Norwell, MA: Kluwer, 1993.

....code, or through commercial vendors who provide documentation and support. Real time system development requires selecting a realtime operating system that provides scheduling guarantees, and designing the software to ensure that deadlines are met. Techniques such as rate monotonic analysis (RMA) [6, 7, 8] are commonly used to derive task scheduling based on task worstcase execution time (WCET) However, worst case execution time is difficult to obtain analytically for tasks running on general purpose microprocessors like the Intel Pentium, due to unpredictable effects from external sources like ....

Klein, M.H., et al. A Practitioner's Handbook for RealTime Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Boston, MA: Kluwer Academic Publishers, 1993.

....all tasks can make their deadlines. Note that while designing and implementing a system that most changes made will affect the real time properties of the system. This makes real time scheduling a global cross cutting dependency. While many different schedulability analysis techniques exist [1, 2, 4, 9, 11, 16, 26], they differ in their assumptions on the task set and none of the existing analysis is applicable to all real time embedded systems. The compatibility between schedulability analyses and the characteristics of the designed system is a typical crosscutting dependency that is hidden from the ....

Klein, M., Ralya, T., Pollak, B., Obenza, R., Harbour, M. G. (1993) A Practitioner's Handbook for Real-Time Analysis -- Guide to Rate Monotonic Analysis for RealTime Systems, Kluwer Academic Publishers.

....requests a reservation from a speci c host with a f lowID. The kernel reserves the queue for that particular ow. Along with the reservation, the application can also request a certain amount of bu er space. The priority assignment currently follows the rate monotonic xed priority algorithm [17]. Hence the task with lower value T gets higher priority. Under this assumption, the response times for a set of n reservations 1 ; 2 ; n with priority( i ) i 1 , can be calculated using the response time test [17] The resource kernel will deny the newest incoming request if the ....

....currently follows the rate monotonic xed priority algorithm [17] Hence the task with lower value T gets higher priority. Under this assumption, the response times for a set of n reservations 1 ; 2 ; n with priority( i ) i 1 , can be calculated using the response time test [17]. The resource kernel will deny the newest incoming request if the response time test fails for at least one reservation. 2.4 Scheduling Mechanism Each reservation is assigned a unique ow identi cation number f lowID that maps to a dedicated priority queue, and is associated with the ....

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate-Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993. ISBN 0-7923-9361-9.

....it is necessary to distinguish design forces that are part of the fundamental problem context from those introduced by particular design decisions made in the process of reconciling the overall system of design forces. For example, rate monotonic analysis and assignment of task priorities [9, 10] is a mechanism commonly used to partition resource access requests into ordered groups, to ensure lower frequency requests do not interfere with servicing higher frequency requests. In certain cases, such as mutually exclusive use of resources shared among threads of different priorities, the ....

.... Level(s) F1 Temporally constrained request All F2 Request asynchrony All F3 Concurrency All F4 Performance constraints All F5 Space constraints All F6 Resource allocation semantics All F7 Constrained resource supply Kernel F8 Concurrent access to a resource Kernel F9 Request cost Kernel F10 Allocation granularity trade offs Kernel F11 Resource utilization trade offs Endsystem F12 Safety vs. interference Endsystem F13 Coordination and communication Endsystem F14 Encapsulation limitations Endsystem F15 Priority management Endsystem F16 Dynamic ordering Endsystem F17 Activities ....

[Article contains additional citation context not shown here]

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour, A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Norwell, Massachusetts: Kluwer Academic Publishers, 1993.

....addition, it provides specific facilities for analysing real time systems for schedulability or performance. 1. Introduction In September 2001, the Object Management Group (OMG) adopted a specification for a standard way of modelling real time systems using the Unified Modelling Language (UML) [1]. This specification is in the form of a UML profile a set of interpretation rules, markings, and constraints imposed on standard UML to more accurately capture the specific phenomena of a given application domain. The benefits of such standard are clear: interoperability of tools and the ....

....profile. This package contains three specific sub profiles: The SAProfile package, specializes the concepts of the concurrency modelling and time modelling sub profiles into a set of generalized concepts commonly used in different schedulability analyses, such as rate monotonic analysis [1] and others. The PAprofile package incorporates a set of general concepts used in performance analyses. The RSAprofile package further refines the concepts of the schedulability profile for the very specific case of the real time CORBA middleware standard. This is useful for analysing the ....

Klein, M., Ralya, T., Pollak, B., Obenza, R., and Gonzalez Harbour, M., A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems, Kluwer Academic Publishers, 1993.

....caches and branch prediction are more suitable than highly speculative complex microprocessors. Second, the operating system used should be a real time one. It should support at least one of the common real time scheduling policies like xed priority preemptive or earliest deadline rst (EDF) [1] [2] The process service described in section 2.1 adapts to di erent process models and scheduling policies. Real time memory management is a useful feature which can be used by OSA as will be seen later in this section. In case of no real time memory management is available the operating system ....

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, M. G. Harbour. A Practitioner's Handbook for Real-Time Analysis: Guide To Rate-Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1999.

....systems incorporate a real time operating system, which offers specialized scheduling services tuned to real time needs, in addition to standard operating system services such as I O. The schedules might be based on priorities, using for example the principles of rate monotonic scheduling [65][49], or on deadlines. There remains much work to be done to improve the match between the assumptions of the scheduling principle (such as periodicity, in the case of rate monotonic scheduling) and the realities of embedded systems. Because the match is not always good today, many real time embedded ....

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour, A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems, Kluwer Academic Publishers, Norwell, Massachusetts, 1993.

....systems incorporate a real time operating system, which in addition to standard operating system services such as I O, offers specialized scheduling services tuned to real time needs. The schedules might be based on priorities, using for example the principles of rate monotonic scheduling [63][48], or on deadlines. There remains much work to be done to improve the match between the assumptions of the scheduling principle (such as periodicity, in the case of rate monotonic scheduling) and the realities of embedded systems. Because the match is not always good today, many real time embedded ....

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour, A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems, Kluwer Academic Publishers, Norwell, Massachusetts, 1993.

....of designs we choose to divide them according to the type and scope of the analysis which provide or suggest. ffl Based on Scheduling Results. This group is constituted by formal and informal notations that use the scheduling results for a periodic task model to asses timing requirements [33, 56, 5]. These are usually deadline satisfaction requirements which come from sampling rate or response time requirements. No functionality is taken into account for analysis. The control structure of the task might be represented as the abstract response structure of the event to be attended ....

....for analysis. The control structure of the task might be represented as the abstract response structure of the event to be attended (sequential, parallel or select ordering of actions) Each action is described in terms of the way it consumes resources (amount, preemtiveness, priority, etc. see [56]. All tasks are considered periodic and interruptions are handled using some kind of sporadic attendance scheme [71] They also support certain degree of analysis in certain multiprocessing environment model [67, 15] Their major strength is that they are of polynomial complexity on the number of ....

[Article contains additional citation context not shown here]

M.H. Klein, T. Ralya, P. Pollak, R. Obenza, M. G. Harbour. Carnegie Mellow University Software Engineering Institute. A Practitioner's HandBook for Real-Time Analysis-Guide To Rate Monotonic analysis for Real Time Systems. Kluwer academic Publishers, 1993.

....produces a portfolio of its products and services. A guidebook such as the Software Engineering Process Group Guide [Fowler Rifkin 1990] is one example of how information pertaining to implementation is conveyed. Engineering handbooks, such as A Practitioner s Handbook for Real Time Analysis [Klein et al. 1993] are also important print based dissemination mechanisms attending to this area. The SEI Education Program uses video extensively: for software engineering courses delivered through the National Technological University and for a lecture series on special topics, where each tape is sold ....

.... (SPA) associates are licensed by the SEI to evaluate software organizations; the National Technological University (NTU) delivers SEI developed courses; Springer Verlag publishes SEI conference proceedings; and Kluwer Academic Publishers released A Practitioner s Handbook for Real Time Analysis [Klein et al. 1993] in the summer of 1993. Funding mechanisms such as direct government grants for FFRDCs allow for timely partnerships for co development early in SEI work and for subsequent prototyping of the technology and transition methods directly with customers. In addition, the SEI is experimenting with ....

Klein M. et al. (1993). A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Boston, Mass.: Kluwer Academic Publishers.

....C i T I is effectively the percent of each period that task I uses. The utilization bound U(N) is defined as U(N) N(2 1 N Gamma 1) RMA states that if the utilization bound is greater than or equal to the total task utilization, then the set of tasks can always be scheduled [26] 19] [16]. This algorithm is inappropriate for the needs of this project. Most importantly, RMA determines whether or not a set of processes is schedulable. This is important in many contexts, but the aim of utility based scheduling is to find the best schedule whether or not all tasks are schedulable. In ....

....ends up being 6 even though t 2 was never executed. In addition, RMA generally assumes a set of periodic tasks; for the case of the utility based scheduler the desired set of tasks might not be predominantly periodic. There has been some work to extend RMA to tasks that are not purely periodic [16]. Even with this work, RMA is not particularly well suited towards the analysis of the systems we are considering. Finally, not only does RMA not consider utility functions, it does not even consider any kind of priority. For these reasons a new form of analysis must be developed. 17 Chapter 3 ....

Ralya Thomas Pollak Bill Obenza Ray Klein, Mark H. and Michael Gonzalez Harbour. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Carnegie Mellon University /Software Engineering Institute, Kluwers Academic Publishing, 1993.

....start with the scheduling analysis to derive a threshold interval between errors that can be tolerated and then employ the fault model to assign a probability to this threshold value. To provide the flexibility needed to program fault tolerance, fixed priority preemptive scheduling will be used [13]. The faults of interest are those that are transient. Castillo at al [6] in their study of several systems indicate that the occurrences of transient faults are 10 to 50 times more frequent than permanent faults. In some applications this frequency can be quite large; one experiment on a ....

....between schedulability and T f , it is possible to apply sensitivity analysis to equation (6) to find the minimum value of T f that leads to the system being just schedulable. As indicated earlier, let this value be denoted as T F (it is the threshold fault interval) Sensitivity analysis [19, 14, 13, 17] is used with fixed priority systems to investigate the relationship between values of key task parameters and schedulability. For an unschedulable system it can easily generate (using simple branch and bound techniques) factors such as the percentage by which all Cs must be reduced for the system ....

M. H. Klein, T. A. Ralya, B. Pollak, R. Obenza, and M. G. Harbour. A Practitioner 's Handbook for Real-Time Analysis: A Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993. Burns, Punnekkat, Strigini, Wright

....results are and the less impact there is on differences in server capacity. The larger the average computation times, the more capacity exhaustions occur and therefore the graph of the average response time is less smooth. An additional conclusion is that queuing network models that were used in [15] and others to predict the performance of the servers are not applicable because they do not model accurately enough their behaviour. Queuing models are based on the server utilisation as the single parameter for determining the performance. We have shown that there is a huge variability on the ....

M. Klein, T. Ralya, B. Pollak, R. Obenza, and M. Harbour. A Practitioner's Handbook for Real-Time Analysis: A Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993.

....of tasks in the system. A necessary and sufficient feasibilitytestwas subsequently proposed by Lehoczky, Sha, and Ding [7] These results have since been generalized in various directions (see, e.g. 2] for a survey) and indeed form the basis of the popular rate monotonic analysis methodology [6] for the design of hard real time systems. The static priority scheduling of systems of MF tasks has also been studied. Mok and Chen [10]proved that the rate monotonic priority assignment is optimal for systems of MF tasks in which each task satisfies an additional property called the ....

Mark Klein, Thomas Ralya, Bill Pollak, Ray Obenza, and Michael Gonzalez Harbour. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, Boston, 1993.

....motivates the hybrid static dynamic MUF scheduling approach for CORBA operations used by TAO s real time scheduling service (described in [6] 2. 1 Limitations of Static Scheduling Many hard real time systems have traditionally been scheduled statically using rate monotonic 2 scheduling (RMS) [7]. Static scheduling provides schedulability assurance prior to run time and can be implemented with low run time overhead [6] However, static scheduling has the following disadvantages: Inefficient handling of non periodic processing: Static scheduling treats aperiodic processing as if it was ....

....static dynamic scheduling. These include purely dynamic strategies such as EDF and MLF, and hybrid approachs such as MUF and two level scheduling. 2.3. 1 Purely Dynamic Scheduling Strategies This section reviews two well known purely dynamic scheduling strategies, Earliest Deadline First (EDF) [12, 7], and Minimum Laxity First (MLF) 9] These strategies are illustrated in Figure 4 and discussed below. In addition, Figure 4 deMUF OPERATION A: HIGH CRITICALITY 40 USEC TO DEADLINE 25 USEC EXECUTION MLF EDF TIME AXIS OPERATION B: LOW CRITICALITY 35 USEC TO DEADLINE 25 USEC EXECUTION ....

[Article contains additional citation context not shown here]

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour, A Practitioner's Handbook for RealTime Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Norwell, Massachusetts: Kluwer Academic Publishers, 1993.

....in order to ensure that systems meet their real time constraints. In another system, complex performance models were constructed to analyze performance using a combination of analytic techniques and simulation. In some of the newer systems, analysis techniques such as rate monotonic analysis [20] are just being introduced. A tool that models this system behavior and supports tuning and analysis of system parameters would be very useful. In almost all of the cases analysis models used were manually derived from the software architecture, and must be redeveloped when the architecture ....

M.H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. Gonzalez Harbour. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993.

....introduced by multitasking. Before this situation can change, we have to rethink multitasking. First, component interface definitions need to declare temporal properties. Not just a priority, which is only sufficient under the rarely applicable assumptions of ratemonotonic scheduling [60][48], but they need to declare the dynamics (phases of execution, exception handling, modes of operation, and yes, also periodicity where appropriate) Then compositions of components need to have consistent and non conflicting temporal properties, much as today compositions of objects need to have ....

....systems incorporate a real time operating system, which in addition to standard operating system services such as I O, offers specialized scheduling services tuned to real time needs. The schedules might be based on priorities, using for example the principles of ratemonotonic scheduling [60][48], or on deadlines. There remains much work to be done to improve the match between the assumptions of the scheduling principle (such as periodicity, in the case of rate monotonic scheduling) and the realities of embedded systems. Because the match is not always good today, many real time embedded ....

[Article contains additional citation context not shown here]

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour, A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems, Kluwer Academic Publishers, Norwell, Massachusetts, 1993.

....nature and finite capacities of the underlying computing resources. Over the years, a number of very useful techniques have evolved in the real time domain for predicting these attributes. These techniques include, notably, schedulability analysis techniques such as rate monotonic analysis [5], which determine whether a given system will meet al..l of its deadlines, and performance modeling methods such as queuing theory [6] which compute delays and resource requirements as statistical quantities. For models to be predictive, it is necessary to model not only the structure and behavior ....

Klein, M. et al. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993.

....measures of context switch time are useful. Impact of context switching overhead on two way CORBA operations: OS context switching overhead significantly impacts the performance and predictability of real time ORB endsystems. In addition, context switching complicates realtime scheduling analysis [30]. Thus, high levels of OS context switching overhead are undesirable for applications with stringent performance requirements. To study the effect of context switching overhead on CORBA operations, we consider two way operations, i.e. round trip request response from client to server and back. ....

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour, A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Norwell, Massachusetts: Kluwer Academic Publishers, 1993.

....priority based concurrency architecture is optimized for statically configured, fixed priority real time applications. In addition, it is well suited for scheduling and analysis techniques that associate priority with rate, such as rate monotonic scheduling (RMS) and rate monotonic analysis (RMA) [19, 20]. For instance, avionic mission computing systems commonly execute their tasks in rates groups. A rate group assembles all periodic processing operations that occur at particular rates (e.g. 20 Hz, 10 Hz, 5 Hz, and 1 Hz) and assigns them to a pool of threads using fixed priority scheduling. ffl ....

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour, A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Norwell, Massachusetts: Kluwer Academic Publishers, 1993.

....schedule real time CORBA operations, as described in Section 3. 2. 1 Limitations of Static Scheduling Many hard real time systems, such as those for avionics mission computing and manufacturing process controllers, have traditionally been scheduled statically using rate monotonic scheduling (RMS) [16]. Static scheduling provides schedulability assurance prior to run time and can be implemented with low run time overhead [10] However, static scheduling has the following disadvantages: Inefficient handling of non periodic processing: Static scheduling treats aperiodic processing as if it was ....

....strategies include purely dynamic techniques, such as EDF, Minimum Laxity First (MLF) as well as the hybrid Maximum Urgency First (MUF) strategy. 2.3. 1 Purely Dynamic Scheduling Strategies This section reviews two well known purely dynamic scheduling strategies, Earliest Deadline First (EDF) [14, 16], and Minimum Laxity First (MLF) 15] These strategies are illustrated in Figure 5 and discussed below. In addition, Figure 5 MUF OPERATION A: HIGH CRITICALITY 40 USEC TO DEADLINE 25 USEC EXECUTION MLF EDF TIME AXIS OPERATION B: LOW CRITICALITY 35 USEC TO DEADLINE 25 USEC EXECUTION ....

[Article contains additional citation context not shown here]

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour, A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Norwell, Massachusetts: Kluwer Academic Publishers, 1993.

....the state of servants to be 6 locked only if they interact across different thread priorities. In addition, this multi threading architecture supports scheduling and analysis techniques that associate priority with rate, such as Rate Monotonic Scheduling (RMS) and Rate Monotonic Analysis (RMA) [13, 14]. The disadvantage with the Reactor per thread priority architecture is that it serializes all client requests for each Reactor within a single thread of control, which can reduce parallelism. To alleviate this problem, a variant of this architecture can associate a pool of threads with each ....

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour, A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Norwell, Massachusetts: Kluwer Academic Publishers, 1993. 7

....The kernel threads run at the same priority as the application threads, which prevents the real time scheduling hazards outlined above. To ensure predictable performance, the kernel threads belong to a real time I O scheduling class. This scheduling class uses rate monotonic scheduling (RMS) [36, 37] to support real time applications with periodic processing behavior. Once a real time I O thread is admitted by the OS kernel, TAO s RIO subsystem is responsible for (1) computing its priority relative to other threads in the class and (2) dispatching the thread periodically so that its deadlines ....

....priority based concurrency architecture is optimized for statically configured, fixed priority real time applications. In addition, it is well suited for scheduling and analysis techniques that associate priority with rate, such as rate monotonic scheduling (RMS) and rate monotonic analysis (RMA) [36, 37]. For instance, avionic mission computing systems commonly execute their tasks in rates groups. A rate group assembles all periodic processing operations that occur at particular rates (e.g. 20 Hz, 10 Hz, 5 Hz, and 1 Hz) and assigns them to a pool of threads using fixed priority scheduling. # ....

[Article contains additional citation context not shown here]

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour, A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Norwell, Massachusetts: Kluwer Academic Publishers, 1993.

No context found.

Klein, M.; Ralya, T.; Pollak, B.; Obenza, R.; & Gonzalez Harbour, M. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems Kluwer Academic Publishers, 1993. 74 CMU/SEI-99-TR-022

No context found.

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour. A Practitioner 's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993.

No context found.

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993.

No context found.

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993.

No context found.

Klein, M. H., Ralya, T., Pollak, B., Obenza, R. and Harbour, M. G. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate-Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993. ISBN 0-7923-9361-9.

No context found.

Mark Klein, Thomas Ralya, Bill Pollak, Ray Obenza, and Michael Gonzalez Harbour. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate-Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993.

No context found.

Klein. A practitioner's handbook for real-time analysis: guide to rate monotonic. Kluwer, 1993.

No context found.

M. H. Klein, T. Ralya, B. Pollak, and R. Obenza. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, Boston, 1993.

No context found.

M. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate-Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993.

No context found.

M. A. Klein. A Practitioner's Handbook for Real-Time Analysis: A Guide to Rate Monotonic Analysis for RealTime Systems. Kluwer, Boston, 1993.

No context found.

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993.

No context found.

M. H. Klein, T. A. Ralya, B. Pollak, R. Obenza, and M. G. Harbour. A Practitioner's Handbook for Real-Time Analysis: A Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993.

No context found.

M. Klein, et.al., "A Practitioner's Handbook for Real-time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems". Boston: Kluwer, 1993.

No context found.

Mark H. Klein, Thomas Ralya, Bill Pollak, and Ray Obenza. A Practitioner's Handbook for RealTime Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993.

No context found.

Klein, M. et al.. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Press, 1993.

No context found.

Klein, M., Ralya, T., Pollak, B., Obenza, R. ,Gonzalez Harbour, M., A practitioner's Handbook for RealTime Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems Kluwer (August 1993).

No context found.

M. H. Klein, T. Ralya, B. Pollak, and R. Obenza. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, 1993.

No context found.

M. Klein, T. Ralya, B. Pollak, R. Obenza, M. G. Harbour, A Practitioner's Handbook for Real-Time Analysis -- Guide to Rate Monotonic Analysis for Real-Time Systems, Kluwer Academic Publishers, August 1993.

No context found.

Mark Klein, Thomas Ralya, Bill Pollak, Ray Obenza, and Michael Gonzalez Harbour. A Practitioner's Handbook for Real--Time Analysis: Guide to Rate Monotonic Analysis for Real--Time Systems. Kluwer Academic Publishers, Dordrecht, The Netherlands, 1993. 4, 13

No context found.

M. H. Klein, T. A. Ralya, B. Pollak, R. Obenza and M. G. Harbour, A Practitioner's Handbook for Real-Time Analysis: A Guide to Rate Monotonic Analysis for Real-Time Systems, Kluwer Academic Publishers, 1993.

No context found.

Klein, M., Ralya, T., Pollak, B., et al, "A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems", Kluwer Academic Publishers, Boston, 1993.

No context found.

M. H. Klein, T. Ralya, B. Pollak, R. Obenza, M. Gonzalez Harbour, A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems, Kluwer 1993.

No context found.

M. Klein, T. Ralya, B. Pollak, R. Obenza, and M. G. Harbour. A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems. Kluwer Academic Publishers, Boston, 1993.

No context found.

M. H. Klein, T. A. Ralya, B. Pollak, R. Obenza and M. G. Harbour, A Practitioner's Handbook for Real-Time Analysis: A Guide to Rate Monotonic Analysis for Real-Time Systems, Kluwer Academic Publishers, 1993

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC