Abstract
In the past few decades, a great number of hardware and software reliability models have been proposed to address hardware failures in hardware subsystems and software failures in software subsystems, respectively. The interactions between hardware and software subsystems are often neglected in order to simplify reliability modeling, and hence, most existing reliability models assumed hardware subsystems and software subsystem are independent of each other. However, this may not be true in reality. In this study, system failures are classified into three categories, which are hardware failures, software failures, and hardware-software interaction failures. The main contribution of our research is that we further classify hardware-software interaction failures into two groups: software-induced hardware failures and hardware-induced software failures. A Markov-based unified system reliability modeling incorporating all three categories of system failures is developed in this research, which provides a novel and practical perspective to define system failures and further improve reliability prediction accuracy. Comparison of system reliability estimation between the reliability models with and without considering hardware-software interactions is elucidated in the numerical example. The impacts on system reliability prediction as the changes of transition parameters are also illustrated by the numerical examples.
Highlights
To model system reliability, most studies have considered partial of the system, hardware subsystem or software subsystem [1,2,3,4,5,6,7,8,9,10,11,12]
Iyer and Velardi [13] discovered that nearly 35 percent of the observed software failures were related with to the hardware platform
Their software errors analysis procedures demonstrated a new methodology to evaluate the interactions between hardware subsystems and software subsystems, which are related with system reliability
Summary
Most studies have considered partial of the system, hardware subsystem or software subsystem [1,2,3,4,5,6,7,8,9,10,11,12]. Iyer and Velardi [13] discovered that nearly 35 percent of the observed software failures were related with to the hardware platform Their software errors analysis procedures demonstrated a new methodology to evaluate the interactions between hardware subsystems and software subsystems, which are related with system reliability. Proposed an analytical method to address reliability of non-repairable hardware-software co-design systems on affecting system health status such as degradation and failure by incorporating the interaction between these two subsystems. Both references [26,27] considered hardware-software interaction failures to be hardware-related software failure, as defined in Teng et al [22].
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
