Declarative Application Data Model Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computer applications face challenges in accommodating diverse application functionality across different domains due to rigid data models, limited adaptability, and complex implementation requirements, making it difficult to add new functionality or process data without substantial effort and expertise.

Innovation Solution

A declarative application system that uses a general data model to derive concrete models for processing, persisting, accessing, and transferring data, enabling purpose-oriented processing and customization through structure and behavior specifications, allowing for dynamic adaptation to different purposes and technologies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If applications are implemented using high-level programming languages with specific data models, then application functionality can be achieved, but the implementation demands substantial skill and effort and cannot accommodate changes to the data model without further development

Engineering Contradiction:
Improveease of implementationVSAvoidadaptability to data model changes
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements a dynamic data model system where the data model can be modified at runtime without requiring application restart or recompilation. The system allows schema evolution, addition of new data types, and modification of existing data structures while the application continues to operate, thereby achieving adaptability to data model changes without substantial reimplementation effort

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent creates a universal data model framework that can accommodate multiple data models and application types through a common architecture. The system provides generic data binding mechanisms, unified query interfaces, and standardized data transformation capabilities that work across diverse data models, reducing implementation complexity while maintaining adaptability

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

2Productivity

If application functionality is implemented as reusable modules, then code reuse is achieved, but reuse is only possible when module user and module implementation use same or syntactically similar data models

Engineering Contradiction:
Improvecode reuse efficiencyVSAvoidcompatibility across different data models
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a data model translation layer that acts as an intermediary between modules with different data models. This translation layer automatically transforms data between different schema formats, enabling modules to communicate and reuse functionality even when they operate on different data models, thereby breaking the coupling requirement while maintaining code reuse efficiency

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements parameterized data model interfaces where data model specifications can be dynamically configured and changed. Modules accept data model parameters as inputs and can adapt their behavior based on the specific data model being used, allowing the same module code to work across different data models without modification through parameter customization

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If declarative programming paradigm is used to abstract task specification, then what needs to be done is specified instead of how, but the declarative specification becomes too vague for the evaluation engine to offer effective processing that meets reasonable processing and performance requirements

Engineering Contradiction:
Improveease of task specificationVSAvoidprocessing effectiveness and performance
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent segments the declarative specification into multiple hierarchical levels: high-level intent specifications, mid-level data model definitions, and low-level implementation details. This segmentation allows the system to maintain vague high-level specifications for ease of use while automatically generating or selecting specific implementation strategies that meet performance requirements, resolving the contradiction between abstraction and effectiveness

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9904519B2Systems and methods for declarative applications
Publication Date: 2018.02.27 BHARATIA VEERAL
  • US9904519B2 patent drawing
  • US9904519B2 patent drawing
  • US9904519B2 patent drawing

AI summary

Embodiments of the disclosure are directed to systems and methods to process a declaratively-specified computer application by interpreting a structure and a behavior specification. Application data items are interpreted using a processing concrete model based on the structure specification. Application functionality is provided by processing the application data items in accordance to the behavior specification. The application information may further be used in an embodiment of the disclosure to perform additional processing and provide an added functionality. Various embodiments of the disclosure allow additional functions for declarative application such as performing domain activities, accessing data items, transferring application data, storing data and milestones and rendering data items.