Hierarchical Object Schema for Unified Data and Algorithm Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computer programming environments, such as Microsoft's Visual Studio, enforce strict rules on object instantiation and lack support for displaying visual representations of programming code semantics, leading to complex and difficult-to-maintain software development processes, with limitations in displaying data and algorithm views and interactions with databases.
Innovation Solution
An integrated development environment that uses a hierarchical object schema with three basic classes of data objects: Container Objects, Master Objects, and Label-Value Pairs, allowing for a graphical interface to display and modify data, metadata, and algorithm code simultaneously, enabling normalization and reduction of redundancy in database implementation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If developers declare classes within source code for each object type, then object instantiation follows strict rules, but code complexity increases and becomes difficult to maintain
Solution Approach 1:
The patent introduces a universal object model where all objects inherit from a base Object class, providing common properties and methods. This allows different object types (Person, Phone, etc.) to be instantiated uniformly without requiring separate class declaration rules for each type, reducing code complexity while maintaining instantiation reliability
Solution Approach 2:
The patent segments object properties into distinct categories (common properties inherited from base Object class, and type-specific properties). This segmentation allows the system to handle generic object operations uniformly while managing type-specific characteristics separately, reducing overall code complexity
2Adaptability or versatility
If each object type requires different internal complex management infrastructure, then specific object requirements are met, but development and maintenance difficulty increases
Solution Approach 1:
The base Object class provides universal management infrastructure that handles common operations (display, data management, etc.) for all object types. This eliminates the need for each object type to implement its own complex management infrastructure, making development easier while still allowing type-specific behavior through inheritance and method overriding
3Difficulty of detecting and measuring
If visual editors display code as flowcharts, then visual representation is provided, but semantic and syntactical information is not unified
Solution Approach 1:
The patent merges the visual flowchart representation with the underlying semantic and syntactical information in a unified object model. The Object class structure maintains full semantic meaning while the visual interface provides graphical representation, combining both advantages without losing information
4Difficulty of detecting and measuring
If data and algorithms are displayed separately, then clarity is maintained, but interaction and navigation become cumbersome
Solution Approach 1:
The patent combines data and algorithm representations within the unified Object class structure, allowing them to be displayed together in the visual interface. The object model inherently links data (properties) with algorithms (methods), enabling simultaneous display and easy navigation without sacrificing clarity
5Reliability
If database queries use middleware, then data access is structured, but functionality is restricted and programming is required
Solution Approach 1:
The Object class acts as an intermediary between the visual interface and the underlying data storage, providing direct access to data and algorithms without requiring traditional database middleware. This eliminates the need for ETL programming while maintaining structured access through the object's properties and methods
Data Source
AI summary
A data schema stores both data and metadata as data in a hierarchical, extensible schema made of three classes of objects. The data schema includes algorithms that generate the data schema and provide the functionality. Container object hold master objects, which represent items in a collection. Master objects hold label-value pairs, having a label portion that provides metadata, and having a value portion that holds the data. The label portion references a second label-value pair, in which the value portion holds the metadata as data, which is retrieved at runtime. Label-value pairs may reference a child container object in master objects to create a hierarchy. The schema can retrieve data and data structures from other databases; multiple databases of different formats can be joined. Software can be stored as data and shown as active flowcharts. A graphical interface can be generated in multiple display modes, including in websites.