Integrated Data Viewer for Program Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional programming approaches often neglect data, failing to facilitate its loading, saving, or viewing, making it difficult to manage and display data associated with programs effectively.

Innovation Solution

A system and method that allows data associated with a program to be displayed and saved within a graphical user interface (GUI) during and after program execution, enabling users to record and display input and output data, along with information about the GUI element, and to retrieve and display saved data sets in a second instance of the GUI.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional programming approaches are used, then program code is the focus, but data management and display capabilities are insufficient

Engineering Contradiction:
Improvedata management capabilityVSAvoidsystem functionality
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent merges data management, display, and program execution functions into a single integrated environment. The data viewer is embedded within the program execution interface, allowing users to view, save, and manage data without switching to separate external programs. This integration directly addresses the contradiction by improving ease of operation through unified functionality while avoiding the complexity of coordinating multiple separate systems.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system provides multi-functional capabilities within a single interface: it can display program execution results, save data to files, retrieve saved data, and present information in various formats (tables, graphs, lists). This universality allows one system to perform multiple data management tasks that traditionally required separate tools, thereby improving ease of operation without proportionally increasing complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If separate programs are invoked for data viewing, then data can be displayed, but the workflow becomes more complex and time-consuming

Engineering Contradiction:
Improvedata viewing efficiencyVSAvoidtime to switch between programs
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent combines program execution and data viewing in a single integrated interface. Users can view data immediately within the same window where the program executes, eliminating the need to switch between separate applications. This directly reduces time loss and improves productivity by maintaining context continuity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system automatically captures and prepares data for viewing during program execution, so that when users need to review data, it is already formatted and ready in the integrated viewer. This preliminary preparation eliminates delays that would occur if data had to be manually extracted and formatted in separate programs.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If data is displayed continuously, then real-time monitoring is possible, but data persistence and retrieval become difficult

Engineering Contradiction:
Improvedata persistenceVSAvoiddata retrieval capability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system automatically saves data to persistent storage during or after program execution, creating a record that can be retrieved later. This preliminary saving action ensures data persistence while maintaining ease of retrieval, as users can access saved data through the integrated viewer without manual intervention.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides feedback mechanisms that allow users to save data, retrieve it, and view it in the integrated interface. The ability to save and subsequently retrieve data with a simple user action creates a feedback loop that confirms data persistence while maintaining operational simplicity.

Inventive Principle:
Principle #23Feedback

4Loss of information

If detailed data information is displayed, then data completeness is improved, but interface complexity increases

Engineering Contradiction:
Improvedata completenessVSAvoidGUI complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The data display interface is segmented into multiple organized sections: data tables, graphical representations, metadata information, and navigation controls. Each section handles specific aspects of data presentation, making the overall interface manageable despite the detail level. This segmentation allows comprehensive data display without overwhelming complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system presents data through multiple dimensions: tabular format, graphical visualizations, and hierarchical organization. Users can switch between different representation dimensions to view the same data in ways that reduce perceived complexity while maintaining completeness. This dimensional flexibility allows detailed information to be displayed without proportionally increasing interface complexity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS8799865B2Integrated data viewer
Publication Date: 2014.08.05 NATIONAL INSTRUMENTS CORP
  • US8799865B2 patent drawing
  • US8799865B2 patent drawing
  • US8799865B2 patent drawing

AI summary

System and method for recording and displaying data associated with a program executing a program. Data associated with the program is displayed in a first instance of a graphical user interface (GUI) element. The data are saved one or more times during or after execution of the program in response to input, including saving information regarding the GUI element. The saved data are then displayed in a second instance of the GUI element in response to user input invoking display of the saved data, based on the saved information regarding the GUI element.