Virtual Hardware Unit Emulation for System-Wide Software Defect Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for testing software on physical computer systems with defective hardware units are limited, as they can only test individual modules and require significant development effort, cannot simulate the entire system, and cannot account for sudden or temporary defects, especially in safety-critical software where hardware defects can lead to system failures.
Innovation Solution
A method that simulates the functionality of physical hardware units as virtual units, allowing for the creation of a virtual computer system to analyze the execution behavior of a program flow, compare it with varied functionality, and compensate for defects, enabling comprehensive testing without modifying the physical system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software-based test code with stubs is used to simulate hardware defects, then individual modules can be tested for defective hardware behavior, but only individual modules can be tested and the entire system cannot be tested in its entirety including the operating system
Solution Approach 1:
The patent creates a virtual copy of the physical computer system including virtual hardware units and a virtual operating system. This virtual replica allows comprehensive system-wide testing without modifying the physical system, enabling test of the entire system including OS while avoiding the limitation of stub-based module testing.
Solution Approach 2:
The patent introduces a virtualization layer as an intermediary between the physical hardware and the software under test. This virtual operating system acts as a mediator that can simulate hardware defects while maintaining system-wide testing capability, bridging the gap between physical hardware testing and software validation.
2Reliability
If real defective hardware units are used to simulate hardware defects, then hardware defects can be tested, but for each physical hardware unit a modified hardware unit must be provided and all combinations of potentially defective hardware units must be simulated
Solution Approach 1:
The patent creates virtual copies of physical hardware units that can simulate defects without requiring physical modification. A single physical hardware unit can be emulated multiple times with different defect scenarios, eliminating the need to procure and maintain multiple modified hardware units for comprehensive testing.
Solution Approach 2:
The patent enables simulation of hardware defects by changing parameters in the virtual hardware unit models rather than physically modifying hardware. Defects are introduced through software-based parameter modifications in the virtualization layer, allowing flexible simulation of various defect types without additional physical hardware.
3Reliability
If modified hardware units are used to simulate defects, then predefined defects can be tested, but validation for suddenly occurring defects or temporary defects is not possible
Solution Approach 1:
The patent implements dynamic defect simulation in the virtual hardware units, allowing defects to be introduced, modified, or removed during program execution. The virtualization layer can dynamically change hardware behavior without physical reconfiguration, enabling testing of sudden and temporary defects that cannot be simulated with static modified hardware.
Solution Approach 2:
The patent allows preparation of virtual defect scenarios in advance while maintaining the ability to activate them dynamically during execution. Test configurations can be pre-defined in the virtualization layer and activated on-demand, combining the benefits of planned testing with the flexibility to simulate unexpected defects.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
The functionality of simulated, virtual hardware units (305a, 305b, 305c, 305d, 305e) is varied during the execution of a program flow (300) on the virtual hardware units (305a, 305b, 305c, 305d, 305e), for example via an interface device (310) of a simulation device (306), in such a manner that the execution behavior changes of a program flow (300) can be identified by using at least one faulty, physical hardware unit (309a, 309b, 309c, 309d, 309e). According to the invention, a method and a device are used for analyzing an execution of a predetermined program flow (300) on a physical computer system (308). The method and the device are used to determine execution behavior changes of software products which changes are due to faulty hardware components. The invention allows execution behavior changes to be identified systematically, using an operating system (303) and eliminates the need for expensive, physical hardware components (309a, 309b, 309c, 309d, 309e) and for modifications to a physical computer system (308).