Shared Object Query Model for Visualization Data Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software applications face challenges in managing dynamic data needs by frequently updating queries for visualizations, leading to inefficiencies in code and storage usage due to separate objects for similar data across different visualizations.
Innovation Solution
Implementing a system that uses shared objects for multiple visualizations, allowing a single source of truth for data, where query models reference these shared objects to generate visualizations, and transforming these models into runtime versions for data retrieval from a computing system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate objects are used for data in different visualizations, then each visualization can be independently managed, but code and storage requirements increase and maintenance becomes more difficult
Solution Approach 1:
The patent merges data objects that are shared across multiple visualizations into a single shared object. When a data object is referenced by multiple query models, the system consolidates these references to point to one shared object instance, reducing code duplication and storage requirements while maintaining the ability to independently manage each visualization through its query model
Solution Approach 2:
The shared object is designed to serve multiple functions across different visualizations simultaneously. A single shared object can be referenced by multiple query models, enabling one object to support multiple visualizations with different query requirements, thereby reducing overall system complexity while maintaining versatility
2Adaptability or versatility
If separate objects are used for data in different visualizations, then each visualization has its own data source, but maintenance effort increases when data requirements change
Solution Approach 1:
By merging references to the same data object across multiple query models, the system enables centralized maintenance. When data requirements change, the modification is made to a single shared object that is automatically reflected in all visualizations that reference it, reducing maintenance effort while preserving data source independence through explicit reference management
3Reliability
If query models are frequently updated to reflect changing data needs, then visualizations remain accurate, but system performance decreases due to repeated transformations
Solution Approach 1:
The system performs preliminary actions by pre-compiling and caching the results of query model transformations. When query models reference shared objects, the transformation to runtime representations is performed once and cached, so that subsequent visualizations can reuse the pre-transformed results without repeating the transformation process, maintaining data accuracy while improving performance
Data Source
AI summary
Some embodiments provide a program that generates a first query for a first visualization based on a first query model associated with the first visualization. The first query model includes a first reference to a shared object. The program further sends the first query to a computing system. The program also receives from the computing system a first set of data. The program further generates the first visualization based on the first set of data. The program also generates a second query for a second visualization based on a second query model associated with the second visualization. The second query model includes a second reference to the shared object. The program further sends the second query to the computing system. The program also receives from the computing system a second set of data. The program further generates the second visualization based on the second set of data.