Application Model Migration via Combined History File Tracking

Solution Overview

Problem

Current software development methods face challenges in migrating complex data models from one software version to another, as prior art tools can only partially migrate changes across extended data model relationships, leading to compatibility issues.

Innovation Solution

A tracking application creates a combined history file to identify and record changes across application model definition files, constructing a transformation file that ensures proper migration of data model instances by unified versioning and dependency tracking.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If separate history files are used for each data model definition file, then changes to individual models can be tracked independently, but changes to extended properties are not properly propagated to dependent models

Engineering Contradiction:

Improvechange propagationVSAvoidhistory file structure

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The patent merges multiple separate history files into a single combined history file that tracks changes across all data model definition files. This combined history file records changes to base models and their extensions together, ensuring that when a property changes in a base model, the change is properly propagated to all dependent extended models. The merging eliminates information loss while managing complexity through unified change tracking.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces a model extension relationship tracker as an intermediary component that identifies and records dependency relationships between base data models and their extensions. This intermediary enables the system to understand which models depend on which properties, allowing proper propagation of changes through the inheritance hierarchy without requiring complex manual tracking in each separate history file.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If data model instances are migrated using separate history files, then migration of individual models can be performed independently, but compatibility issues arise when models extend other models

Engineering Contradiction:

Improvemigration compatibilityVSAvoidmigration process

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent performs preliminary actions by creating a combined history file that pre-establishes the relationships between base models and their extensions before migration begins. The system identifies all model extension relationships and records them in advance, so that during migration, changes can be automatically propagated to dependent models without requiring complex runtime analysis. This preliminary setup ensures compatibility while streamlining the migration process.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent segments the migration process into distinct phases: first identifying model extension relationships, then recording changes in a combined history file, and finally applying migrations while maintaining dependency relationships. This segmentation allows independent processing of individual models while ensuring overall compatibility through the structured approach to handling extensions.

Inventive Principle:

Principle #1Segmentation

3Loss of information

If changes are recorded in separate history files without considering model relationships, then each model's change history is maintained independently, but dependent models do not reflect changes from extended models

Engineering Contradiction:

Improvechange propagationVSAvoidhistory file structure

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The patent merges multiple separate history files into a single combined history file that tracks changes across all data model definition files. This combined history file records changes to base models and their extensions together, ensuring that when a property changes in a base model, the change is properly propagated to all dependent extended models. The merging eliminates information loss while managing complexity through unified change tracking.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces a model extension relationship tracker as an intermediary component that identifies and records dependency relationships between base data models and their extensions. This intermediary enables the system to understand which models depend on which properties, allowing proper propagation of changes through the inheritance hierarchy without requiring complex manual tracking in each separate history file.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS9304765B1Method and system for tracking changes to application model definitions for application model migration

Publication Date: 2016.04.05 DELL EMC

AI summary

Tracking changes to application model definitions for application model migration is described. A combined history file is created based on changes associated with application model definition files. A first property for a first model definition file of the application model definition files is identified that depends on a second property for a second model definition file of the application model definition files. A change for the second property is identified based on the combined history file. A transformation file is constructed that includes a change for the first property based on the change for the second property.