Upgrade Tracking System for Application Data Dependencies

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software developers lack a systematic approach to manage dependencies between data upgrade files during application upgrades, leading to inefficient execution phases and increased downtime due to unawareness of inter-file dependencies, making it difficult to modify the execution order without breaking downstream dependencies.

Innovation Solution

Grouping data upgrade files into functional upgrade groups and creating a dependency hierarchy to manage and track dependencies, along with an upgrade tracking system that provides analytics and reporting to ensure consistent execution order and efficient upgrades.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If developers determine execution order ad-hoc on a file-by-file basis, then individual file placement is simple, but the total running time of the upgrade increases due to unnecessary serial execution phases

Engineering Contradiction:
Improveupgrade execution efficiencyVSAvoidsystem downtime
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments data upgrade files into functional upgrade groups based on their dependencies. Files that can execute in parallel are grouped together, while groups themselves are ordered according to dependency relationships. This segmentation enables parallel execution within groups while maintaining correct sequential ordering between groups, thereby reducing total upgrade time and system downtime.

Inventive Principle:
Principle #1Segmentation

2Reliability

If developers place files in random downstream phases to ensure execution order, then dependency satisfaction is achieved, but the number of execution phases increases unnecessarily

Engineering Contradiction:
Improvedependency satisfactionVSAvoidexecution phase structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges independent data upgrade files into the same execution phase by grouping them into functional upgrade groups. Files that have no dependency relationships between them are combined into parallel execution batches, reducing the total number of execution phases while ensuring all dependency constraints are satisfied through the hierarchical group structure.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If developers modify execution order of data upgrade files, then adaptation to upstream dependency changes is possible, but downstream dependencies may be broken due to lack of holistic view

Engineering Contradiction:
Improveexecution order flexibilityVSAvoiddownstream dependency integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the system automatically tracks and reports dependency relationships between all data upgrade files. When developers need to modify execution order, the system provides holistic visibility of all downstream dependencies, allowing developers to anticipate and avoid breaking dependencies. The system monitors execution phases and can alert developers to potential dependency violations before they occur.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8752040B2Upgrade tracking system
Publication Date: 2014.06.10 ORACLE INT CORP
  • US8752040B2 patent drawing
  • US8752040B2 patent drawing
  • US8752040B2 patent drawing

AI summary

An upgrade tracking system for tracking aspects of an application upgrade. In various embodiments, the update tracking system includes a statistics collection component configured to collect statistics related an execution of the application upgrade, where the application upgrade includes a plurality of data upgrade files, and where the plurality of data upgrade files are organized into a plurality of functional upgrade groups. The system further includes a timing component configured to report execution timings related to the execution of the application upgrade, and a status component configured to track statuses related to the execution of the application upgrade.