Virtual Device for Legacy Transaction Simulation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional computing system verification processes are inefficient and costly due to the need for manual verification of multiple components, limited manpower, and the difficulty in simulating real-world scenarios, leading to inadequate testing of new systems.
Innovation Solution
A virtual device system that captures and stores transaction history between legacy and linked devices, allowing for the generation of test data to simulate interactions and verify the new computing system's responses, thereby reducing the need for extensive manual testing and minimizing costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual verification is performed by developers or testers for each test case, then verification thoroughness can be improved, but verification time and cost increase significantly
Solution Approach 1:
The patent creates virtual copies of real transaction data through virtual devices that simulate legacy systems. These virtual devices reproduce actual transaction scenarios without requiring manual intervention for each test case, enabling automated verification that maintains thoroughness while reducing time consumption
Solution Approach 2:
The verification system performs self-service by automatically executing test cases using virtual devices that generate and process test data without human intervention. The system autonomously verifies computing system responses across multiple scenarios, eliminating the need for manual verification while maintaining comprehensive coverage
2Reliability
If multiple separate components are verified manually by multiple users, then component verification completeness can be improved, but resource consumption and cost increase
Solution Approach 1:
The patent merges multiple verification tasks into a single integrated automated system. Virtual devices consolidate the functionality of multiple testers verifying different components, allowing comprehensive component verification to be performed by one system rather than requiring multiple manual operators
Solution Approach 2:
The virtual device system performs multiple verification functions simultaneously - it can verify different components, simulate various legacy systems, and execute diverse test cases through a single multi-functional platform, improving resource efficiency while maintaining verification completeness
3Measurement precision
If test environments are created for different legacy systems to verify outbound testing, then testing accuracy can be improved, but system complexity and setup cost increase
Solution Approach 1:
The patent introduces virtual devices as intermediary components that simulate legacy systems without requiring actual legacy system environments. These virtual intermediaries provide accurate transaction scenario reproduction while eliminating the need to set up and maintain complex test environments for each legacy system
Solution Approach 2:
Instead of creating physical test environments for different legacy systems, the patent creates virtual copies through software-based virtual devices. These copies reproduce the essential characteristics and transaction behaviors of legacy systems, maintaining testing accuracy while dramatically reducing environment setup complexity
4Measurement precision
If conversion programs are developed for each verification task, then task-specific verification accuracy can be improved, but development time and cost increase
Solution Approach 1:
The virtual device system provides a universal verification platform that handles multiple verification tasks through a single system. Rather than requiring separate conversion programs for each task, the virtual devices can adapt to different verification scenarios through configuration rather than custom program development, improving ease of implementation while maintaining task-specific accuracy
Data Source
AI summary
A virtual device acquires a transaction history between a legacy computing device and a linked device; obtains a first request provided from the legacy computing device based on the transaction history and a first response received from the linked device in response to the first request; receives a second request corresponding to the first request from a new computing device and determines a second response to the second request; and provides test information for the new computing device based on a comparison of the first response and the second response.


