Object Mapping via Intrinsic Persistence Metadata and Pattern Rules

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional approaches to object models require specialized technicians for maintenance and transformation, leading to increased costs and delays, as users need to understand complex data structures and transforms to achieve desired results.

Innovation Solution

The system employs intrinsic persistence metadata and pattern-based rules to transform business-level object models into data-level mappings, enabling dynamic code generation for data integration, reducing the need for specialized expertise and simplifying the development process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional object model approaches are used, then data transformation can be achieved, but specialized technicians are required and development time increases

Engineering Contradiction:
Improvedevelopment timeVSAvoidease of object model maintenance
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent introduces an automatic code generation system that acts as an intermediary between business users and complex data transformation operations. The system generates executable code from high-level business rules, eliminating the need for users to directly understand or manually implement complex data structures and transforms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables self-service by allowing business users to define their own object models and transformation rules without requiring specialized technical knowledge. The automatic code generation feature empowers users to independently maintain and modify object models, generating the necessary implementation code automatically.

Inventive Principle:
Principle #25Self-service

2Reliability

If users directly manipulate data structures and transforms, then desired results can be achieved, but specialized training is required and costs increase

Engineering Contradiction:
Improveaccuracy of data transformationVSAvoidcomplexity of object model maintenance
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the complexity of code generation and data structure manipulation from the user's direct control. The system separates high-level business rule definition from low-level implementation details, automatically generating the complex code and data structure transformations needed to achieve accurate results.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system replaces manual mechanical processes of writing and maintaining complex transformation code with an automated code generation mechanism. This substitution maintains transformation accuracy while eliminating the need for users to manually handle complex implementation details.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Ease of manufacture

If manual code generation is used, then object model transformations can be implemented, but development time and delays increase

Engineering Contradiction:
Improveease of code generationVSAvoiddevelopment time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The system performs preliminary action by automatically generating implementation code before users would need to manually write it. The code generation occurs on-demand based on user-defined business rules, preparing the necessary transformation logic in advance and eliminating time-consuming manual coding processes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates copies of transformation logic by generating code from template patterns and business rules. Instead of manually writing each transformation from scratch, the system automatically replicates and adapts proven transformation patterns to specific user requirements, dramatically reducing development time.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10503482B2Object mapping using intrinsic persistence metadata and pattern-based rules for mapping transformation
Publication Date: 2019.12.10 ORACLE INT CORP
  • US10503482B2 patent drawing
  • US10503482B2 patent drawing
  • US10503482B2 patent drawing

AI summary

The present disclosure relates generally to a data integration system that may provide techniques for capturing definitions from business entities and how the business entities are implemented in a set of tables. This enables the data integration system to transform a data flow defined using business entities into code that may be used to transform the underlying tables and columns. Additionally to generate tables, classes and APIs to provide persistence of and manipulation for the definitions of these business entities. Additionally to dynamically generate a GUI editor for an object model of arbitrary complexity while maintaining GUI usability. This reduces development time and supports editing of an arbitrary object model. A dynamically generated GUI may be generated from an object model definition that is received from a user and/or is derived from the user's code.