Optimum combined test plans for systems and components

Abstract

Since mathematical models based on component reliabilities are frequently used for prediction of system reliability, it stands to reason that cost-eective inferences on the reliability of a system could be made on the basis of tests of its constituent components. Prior research in the area of system-based component testing has for the most part addressed the development of plans that test only the components. From a practitioner's point of view, this is an issue of concern since system failures are often caused by imperfect interfaces and other causes that are not directly attributable to component failures. The exclusion of system tests may thus be an erroneous approach. This paper addresses the development of test plans that explicitly consider the possibility of interface failures. The paper analyzes a series system to determine when testing should be performed on the system alone, on the components only, and on both, depending on test costs and interface reliabilities. Optimum test plans are derived by solving a twostage mathematical program.

From Buyer to Integrator: The Transformation of the Supply‐chain Manager in the Vertically Disintegrating Firm

“…Or, as one manager stated, "'HPizing' [that is, building in reliability and user-friendliness] happens at HP" (Parker and Anderson 1999). In recent years, the bulk of quality problems have shifted from component-level issues to systems-level issues that cut across vendors (Rajgopal, Mazumdar, and Mejety 1999). For example, HP held it vitally important that they were first-to-market with a Windows 2000 -compatible notebook that worked.…”

Modular operational test plans for inferences on software reliability based on a Markov model

“…For the sake of simplicity, we also do not model the possibility of failures in the interfaces among the modules or module interactions. However, in earlier work on "hardware" systems we have explicitly modeled interface failures [14], and we believe that this extension can be achieved by modifying the software reliability model to include a combination of modular and system testing.…”

Failure Modes and Effects Analysis: An Evaluation of Group versus Individual Performance

“…Sosa et al (2004) study these two dimensions of product design and show that the lack of interaction among design subgroups can result in inadequate interfaces and, thus, unreliable interactions among the components which, in turn, result in product failures. Rajgopal et al (1999) also recognize the occurrence of such interface failures in their work, which determines effective testing policies for designs at the component and system levels. There is evidence that modular designs can lead to the lessening of interaction among design groups which, of course, is subsequently required to design reliable interfaces (Sosa et al 2003).…”

“…Rajgopal et al. (1999) also recognize the occurrence of such interface failures in their work, which determines effective testing policies for designs at the component and system levels. There is evidence that modular designs can lead to the lessening of interaction among design groups which, of course, is subsequently required to design reliable interfaces (Sosa et al.…”