Terminal Application Run-Time Data Capture for Offline Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing terminal applications face challenges in design and testing due to the need for a live connection to a host server, making modernization from TUI to GUI front-ends time-consuming and error-prone, and restricting outsourcing of software development due to security and integration issues with mainframe systems.
Innovation Solution
A system that captures and stores terminal application run-time data in a persistent format like XML, allowing for the reconstruction of visual layouts and interactions without a live server connection, enabling testing and development of scenarios independently of the host server using a run-time data editor and playback component.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a live connection to host server is required for terminal application testing, then application functionality can be verified, but testing time and complexity increase significantly
Solution Approach 1:
The system captures and stores terminal application run-time data (screens, transactions, user interactions) during actual application execution. This preliminary data collection enables later replay and testing without requiring live server connections, thus reducing testing time while maintaining functionality verification capability
Solution Approach 2:
The system creates a copy of the terminal application's run-time data including screen images, transactions, and user interactions. This copy can be replayed locally without the host server, allowing testers to verify application functionality independently, thereby eliminating the time loss associated with establishing and maintaining live server connections
2Measurement precision
If host server connection is required for terminal application testing, then accurate testing can be performed, but modernization from TUI to GUI becomes time-consuming and error-prone
Solution Approach 1:
The system captures accurate representations of terminal application screens and transactions during execution. These captured data serve as precise reference copies that can be used to verify both TUI and GUI implementations, enabling accurate testing during modernization without the time consumption of live server connections
Solution Approach 2:
By capturing run-time data during actual application execution, the system creates a foundation for verifying modernized interfaces. This preliminary data collection enables testers to accurately compare TUI and GUI implementations without requiring continuous live server access, thus reducing modernization time while maintaining testing accuracy
3Reliability
If host server connection is required for terminal application testing, then functional verification is possible, but emulator establishment and maintenance costs increase
Solution Approach 1:
The system creates a copy of terminal application run-time data including screen images, transactions, and user interactions. This copy can be replayed locally without requiring complex emulator infrastructure or live server connections, thereby maintaining functional verification capability while eliminating emulator establishment and maintenance costs
Solution Approach 2:
The system extracts essential run-time data from the terminal application execution process. By taking out only the necessary data (screens, transactions, interactions) rather than requiring the entire host server environment, the system enables functional verification without the complexity and cost of maintaining emulator infrastructure
4Object-affected harmful factors
If security restrictions limit host server access, then system security is maintained, but outsourcing software development functions becomes difficult
Solution Approach 1:
The system creates a copy of terminal application run-time data that can be analyzed and tested locally without accessing the restricted host server. This enables outsourced developers to verify functionality and contribute to development while maintaining security restrictions on the host server, thus resolving the contradiction between security and outsourcing capability
Solution Approach 2:
The captured run-time data acts as an intermediary between the secure host server and outsourced developers. Instead of requiring direct access to the restricted server, developers can analyze replayed data copies locally, enabling secure outsourcing while maintaining system security
5Reliability
If tight integration between terminal applications and mainframe system is required, then system reliability is maintained, but platform-independent development is restricted
Solution Approach 1:
The system captures platform-independent run-time data representations of terminal application transactions and screens. These copies can be analyzed and used for development on different platforms without requiring tight integration with the mainframe system, thus enabling platform-independent development while maintaining the reliability of the integrated system through accurate data capture
Data Source
AI summary
Run-time data and visual layout definition data can be stored in a storage medium. The run-time data and the visual layout definition data can be associated with a terminal application, which is configured to communicate with a host server in blocks of data in accordance with a standardized synchronous terminal protocol. A visual screen for the terminal application can be generated by combining the layout data and the run-time data. The generating can occur when the terminal application is disconnected from the host server or host server emulator. The generated visual screen, which is a screen of a front-end of a terminal application interface, can be presented.