Software Module Correlation for Redundant Library Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large-scale software applications face challenges due to information barriers and redundancy between development groups, leading to redundant modules and increased hardware requirements, which can be addressed by automatically comparing the correlation of third-party libraries referenced by modules and adjusting them to reduce redundancy.

Innovation Solution

A method and system that determines the degree of correlation between sets of third-party libraries referenced by different modules and adjusts modules based on this correlation, such as merging or replacing similar modules, thereby reducing redundant libraries and application volume.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If modules are decomposed into multiple groups for parallel development, then development efficiency is improved, but information barriers and redundancy between groups increase

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidinformation barriers between groups
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system implements automated feedback mechanisms by continuously analyzing third-party library usage across modules and providing correlation information back to development groups. This enables each group to understand what libraries other groups are using, reducing information barriers while maintaining parallel development efficiency.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary system that acts as a mediator between development groups. This system analyzes library correlations and provides recommendations, serving as a communication bridge that reduces information barriers without requiring direct interaction between development groups.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If each module independently references third-party libraries, then module autonomy is improved, but redundancy and application volume increase

Engineering Contradiction:
Improvemodule autonomyVSAvoidredundant libraries
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system promotes universal third-party library usage across multiple modules by identifying and recommending common libraries. This allows different modules to share the same library instances, reducing redundancy while maintaining each module's functional autonomy and independence.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent merges duplicate third-party library references across modules by identifying correlated libraries and consolidating them. This reduces the total quantity of redundant libraries in the application while preserving each module's independent functionality through shared library dependencies.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If modules use different third-party libraries, then specialized functionality is improved, but system complexity and maintenance difficulty increase

Engineering Contradiction:
Improvespecialized functionalityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system applies local quality by allowing modules to use specialized third-party libraries when necessary for specific functionality, while simultaneously identifying opportunities to use common libraries where appropriate. This balanced approach maintains specialized capabilities where needed while reducing overall system complexity through strategic standardization.

Inventive Principle:
Principle #3Local quality

4Adaptability or versatility

If redundant modules are retained for functionality, then feature completeness is improved, but hardware requirements and performance decrease

Engineering Contradiction:
Improvefeature completenessVSAvoidhardware requirements
Core Design Contradiction:
Adaptability or versatilityVSWeight of moving object

Solution Approach 1:

The system merges functionally similar modules by analyzing third-party library correlations and identifying redundant implementations. This consolidation reduces the overall application size and hardware requirements while preserving complete functionality through unified module designs that combine capabilities of previously separate modules.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20260030003A1Method, device, and product for processing software modules
Publication Date: 2026.01.29 DELL PROD LP
  • US20260030003A1 patent drawing
  • US20260030003A1 patent drawing
  • US20260030003A1 patent drawing

AI summary

A method includes acquiring and determining a first set of third-party libraries referenced by a first module in a target application and a second set of third-party libraries referenced by a second module in the target application. The method further includes determining a degree of correlation between the first set of third-party libraries and the second set of third-party libraries. The method further includes adjusting at least one of the first module and the second module in response to the degree of correlation being greater than a predetermined threshold. By automatically comparing the correlation between the sets of third-party libraries referenced by the modules, this method can adjust similar modules, such as replacing or merging similar modules, thereby reducing the number of third-party libraries in the target application, reducing redundant modules, and reducing the volume of the target application.