Front-End Data Validation Framework for Heterogeneous Database Portability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software systems face challenges in efficiently managing structured data collection, presentation, validation, and workflow management across heterogeneous distributed database systems, leading to difficulties in portability and customization.
Innovation Solution
The development of a set of software components that logically decouple front-end data collection, presentation, validation, and workflow management software from the back-end database system, using interpretable configuration files and frameworks to facilitate configuration, validation, and workflow management across different database models.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If front-end software is tightly coupled with back-end database systems, then data collection and validation can be performed, but portability across different database models is lost
Solution Approach 1:
The patent divides the software system into distinct front-end and back-end components, with the front-end containing data collection forms and validation logic, and the back-end containing database-specific implementation details. This segmentation allows the front-end to be portable across different database models while maintaining functional integrity.
Solution Approach 2:
The patent introduces an intermediary layer (application logic layer) between the front-end forms and back-end database systems. This intermediary handles database-specific operations and translates them into generic form definitions, enabling portability without requiring changes to the front-end software when switching database models.
2Productivity
If database-specific software is customized for each heterogeneous database model, then optimal data access is achieved, but software re-development is required when switching databases
Solution Approach 1:
The patent creates a universal front-end software architecture that can interface with multiple different database models through standardized form definitions. The same form definitions and validation logic can be used across relational databases, hierarchical databases, and other database models without re-development.
Solution Approach 2:
The patent uses configurable parameters and metadata to adapt the software behavior to different database models. By changing database connection parameters and model-specific configuration settings, the same software can efficiently access different types of databases without requiring code changes.
3Ease of operation
If forms-based interfaces are used for data collection, then user-friendly data entry is achieved, but complex validation across heterogeneous databases becomes difficult
Solution Approach 1:
The patent uses form definitions that serve as templates or copies of the underlying data models. These form definitions capture the structure, validation rules, and data types, allowing the same forms to be used across different database models while maintaining consistent validation logic.
Solution Approach 2:
The patent introduces an intermediary validation layer that handles complex validation logic independent of the specific database model. This intermediary validates data according to form definitions before passing it to the database-specific layer, simplifying the overall validation process while maintaining complexity where needed.
Data Source
AI summary
A method of managing decoupled front-end and back-end processes is disclosed. The method comprises receiving a first result of user interaction with a first front-end interface; determining that the first result represents a validation of a data item entered via the first front-end interface; mapping the data item in a validated form to a back-end object; causing storing the data item in a database system in association with the back-end object; receiving a second result of user interaction with a second front-end interface; determining that the second result represents a state transition corresponding to executing a query entered via the second front-end interface against the database system; mapping the state transition to a set of back-end commands; causing executing the set of back-end commands over the database system of back-end objects.