Must_1_Reliability Modeling of Hardware and Software_Dec-2006

Must_1_Reliability Modeling of Hardware and Software_Dec-2006

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: IEEE TRANSACTIONS ON RELIABILITY, VOL. 55, NO. 4, DECEMBER 2006 571 Reliability Modeling of Hardware and Software Interactions, and Its Applications Xiaolin Teng, Hoang Pham , Fellow, IEEE , and Daniel R. Jeske Abstract— We classify system failures into three categories: hardware failures, software failures, and hardware-software interaction failures. We develop a unified reliability model that ac- counts for failures in all three categories. Hardware, and software failures are accounted for with well-known modeling approaches. In this paper, we propose a modeling methodology using Markov processes to capture hardware-software interaction failures. We illustrate the combined hardware & software modeling approach by applying it to a real telecommunication system. NOTATIONS hazard rate for hardware subsystem to go to the degradation state. hazard rate for degraded hardware sub- system to go to the total failure state. software hazard rate from undetected hardware degradation to HW/SW failure (fail unsafe). software hazard rate from detected hardware degradation to abortion (fail safe). repair rate after degradation is detected. probability that the hardware degradation is detected. probability that the hardware degradation is undetected, . probability that the degradation is recovered by software methods. probability that the degradation is not recovered by software, . fraction of reported HW failures that are HW/SW failures. ratio sum of squared errors Manuscript received April 18, 2000; revised April 1, 2001 and March 8, 2006. Associate Editor: J. Healy. X. Teng and H. Pham are with the Department of Industrial & Systems En- gineering, Rutgers University, Piscataway, NJ USA. D. R. Jeske is with the Department of Statistics, University of California at Riverside, Riverside, CA USA. Digital Object Identifier 10.1109/TR.2006.884589 I. INTRODUCTION A LARGE literature exists in the areas of hardware relia- bility, and software reliability. However, most of the re- search in these areas has been limited to consideration of either the hardware subsystem alone, or the software subsystem alone. A few researchers, such as [2], [4], and [8], tried to establish a combined reliability model for the whole system, including both hardware, and software. However, they generally assume that the hardware and software subsystems are independent of each other (i.e., there is no interaction between the two systems). It has been shown that there exist remarkable interactions be- tween hardware components and software components within many modern computing systems. For example, [5] analysed software errors on an MVS/SP operating system at Stanford University, and found that nearly 35 percent of all observed soft- ware failures were hardware-related. With hardware and soft- ware being heavily involved with each other, it has become more difficult to distinguish hardware failures from software failures....
View Full Document

This note was uploaded on 06/03/2011 for the course TCS 402 taught by Professor Nitin during the Spring '11 term at Century College.

Page1 / 7

Must_1_Reliability Modeling of Hardware and Software_Dec-2006

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online