Artifact Package Branch Retention to Reduce Storage Requirements

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Managing artifact information packages for different development branches of an app consumes large data storage resources, and existing systems lack efficient methods to reduce storage requirements while preserving meaningful historical and branch structures.

Innovation Solution

A method and system that includes providing a sequence of artifact information packages, applying cut-off information to separate packages into pre-cut-off and post-cut-off groups, determining retained side branches, storing parts of the earliest package and relevant post-cut-off packages, and discarding irrelevant post-cut-off packages to reduce storage size while maintaining historical and branch structures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If all artifact information packages for different development branches are stored in the data repository, then complete historical and branch structure information is preserved, but storage resources are consumed excessively

Engineering Contradiction:

Improvehistorical and branch structure informationVSAvoidstorage resources

Core Design Contradiction:

Loss of informationVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential historical information (earliest package) and relevant branch structure information (retained side branches) from the complete package history, separating necessary information from redundant data that can be discarded

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent discards post-cut-off packages from non-retained side branches while recovering and preserving the essential historical structure through the earliest package and retained side branches, achieving storage reduction without losing meaningful information

Inventive Principle:

Principle #34Discarding and recovering

2Reliability

If post-cut-off packages from all side branches are retained, then complete branch development history is maintained, but storage requirements increase significantly

Engineering Contradiction:

Improvebranch structure integrityVSAvoidstorage size

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies different retention policies to different side branches based on their importance and relationship to the main branch, retaining some side branches (those with post-cut-off packages) and discarding others, creating a differentiated storage strategy that maintains essential branch structures while reducing overall storage requirements

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS20250244999A1Storage resources saving management of artifact information packages, such as packages relating to different development branches of an app, method, and system

Publication Date: 2025.07.31 SIEMENS INDUSTRY SOFTWARE NETHERLANDS BV

AI summary

A method includes providing a sequence of artifact information packages including an earliest package and a latest package in a data repository. Each package except the earliest package is an amended version of the respective preceding package. The sequence includes at least three branches of packages, including a main branch including the latest package. The branches include at least two side branches of which a respective earliest branch package is a respective amended version of a preceding package of the main branch. Cut-off information separating the packages in pre-cut-off packages and post-cut-off packages is provided. At least one of the side branches including at least one post-cut-off package to be a respective retained side branch is determined, a part of the earliest package is stored in a data store, and the respective post-cut-off package of the respective side branch other than the respective retained side branch is discarded.