Discrete Software Package Deployment via Metadata Grouping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software updates often include unnecessary components, leading to resource-intensive downloads and installations, which can disrupt client devices and cause system instability due to interdependent software applications and tools.
Innovation Solution
A method and system for automatically identifying and packaging discrete software packages by detecting triggering events, using metadata identifiers to group related source code deliverables, and applying packaging rules to generate deployment data for efficient transmission and installation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a large software update including all dependent applications is distributed, then completeness of software update is improved, but bandwidth consumption and processing time increase
Solution Approach 1:
The software update is divided into discrete packages, each containing a specific application or component. The system identifies and groups related software components into separate deployable units, allowing selective transmission and installation of only the necessary packages rather than distributing a monolithic update containing all dependencies.
2Reliability
If a large software update including all dependent applications is distributed, then completeness of software update is improved, but processing time increases
Solution Approach 1:
The software update is divided into discrete packages, each containing a specific application or component. The system identifies and groups related software components into separate deployable units, allowing selective transmission and installation of only the necessary packages rather than distributing a monolithic update containing all dependencies.
3Reliability
If a large software update is distributed, then completeness of software update is improved, but client device resources are overwhelmed
Solution Approach 1:
The software update is divided into discrete packages, each containing a specific application or component. The system identifies and groups related software components into separate deployable units, allowing selective transmission and installation of only the necessary packages rather than distributing a monolithic update containing all dependencies.
Solution Approach 2:
The system extracts and identifies only the specific software components that are actually needed by the client device, removing unnecessary components from the update package. This is achieved through metadata analysis that determines which applications and dependencies are relevant to the client's installed software.
4Reliability
If unnecessary software components are included in update, then completeness of software update is improved, but system stability deteriorates
Solution Approach 1:
The system extracts and identifies only the specific software components that are actually needed by the client device, removing unnecessary components from the update package. This is achieved through metadata analysis that determines which applications and dependencies are relevant to the client's installed software.
Data Source
AI summary
Methods and systems are disclosed for defining deployment data that identify a manner in which to divide a software package of source code deliverables into smaller discrete software package. A triggering event occurring in response to a modification of one or more source code deliverables causes a set of source code deliverables to be identified. One or more particular metadata identifiers associated with the modified one or more source code deliverables may be used to define a group of source code deliverables. The group of source code deliverables includes a subset of the set of source code deliverables that may also be associated with the one or more particular metadata identifiers. One or more packaging rules may facilitate defining deployment data identifying package transmissions for the group of source code deliverables. The deployment data may then be output to one or more devices.