Abstract: A system and method for discovering fault conditions such as conflicts between applications and an operating system, driver, hardware, or a combination thereof, installed in mobile computing devices uses a mobile device running a diagnostic application. A list of applications that were launched or installed during a time period prior to an operational disruption is retrieved. A data table of combinations of incompatible programs and drivers is used to analyze the list of the applications that were launched or installed to create a list of potential fault-causing interactions due to software incompatibilities of software installed in the mobile computing device. A knowledge database is updated with data identifying at least one of the potential fault-causing interactions.

Abstract: System and method for analyzing operation of a device under test (DUT). In one embodiment, a reference component associated with a reference device may be received. The reference device may be in communication with the DUT and a component associated with the DUT can be exchanged with the reference component. A test may be performed on the DUT, wherein a result of the test may correspond to a source of a fault associated with the DUT. An indication of the source of the fault may be provided based on the test result.

Abstract: Software components “self-scrub” to improve software reliability, serviceability and availability (RAS). Each component designates a routine to perform a component level consistency check on major data structures and to verify the state of component. This is performed as an on-going task during the life of the component. The component registers an entry point with the system to receive notification of scrubbing parameter changes. The entry point is also called with the request to perform component-scrubbing operations. The entry point functions are responsible for executing within limitations on central processing unit (CPU) usage and memory footprint when performing scrubbing operations.

Abstract: A method for assessing and analyzing software reliability comprises the steps of: collecting failure data from a software system during a testing period; providing a reliability model having a testing compression factor, wherein the reliability model is used to fit the failure data; providing an estimation function derived from the reliability model; obtaining the value of the testing compression factor in accordance with the estimation function; and using the testing compression factor to determine the efficiency of test cases.