Code Management System for Reducing Redundant Storage

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing technologies for reusing application code are inefficient due to poorly annotated and optimized code, leading to multiple redundant copies and a lack of tools to identify the most effective code for a specific purpose, resulting in suboptimal resource usage and limited user experience.

Innovation Solution

A code management and tracking system that provides a graphical user interface for selecting and deploying reusable code, tracks changes, and rewards developers for high-quality code contributions, ensuring efficient storage, deployment, and continuous improvement of application code.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If developers manually store and reuse code without a management system, then code can be preserved, but multiple redundant copies are created and resource efficiency decreases

Engineering Contradiction:

Improvecode storage efficiencyVSAvoidcomputing resource efficiency

Core Design Contradiction:

Quantity of substanceVSLoss of energy

Solution Approach 1:

The patent merges multiple scattered code copies into a centralized code repository, where all code entries are stored in one location. This consolidation eliminates redundant storage across multiple devices and enables efficient resource utilization through shared access to the same code base.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The code repository serves multiple functions: storing code entries, tracking usage metrics, identifying reusable code, and enabling deployment. This multi-functional system replaces multiple separate processes (manual code sharing, version control, usage tracking) with a single unified platform.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Ease of manufacture

If code is stored without annotations and optimization tracking, then storage is simple, but code reusability and effectiveness identification become difficult

Engineering Contradiction:

Improvecode storage simplicityVSAvoidcode effectiveness identification

Core Design Contradiction:

Ease of manufactureVSDifficulty of detecting and measuring

Solution Approach 1:

The system implements feedback loops where code usage is tracked and metrics are collected. This usage data feeds back into the repository to identify which code entries are most effective and frequently reused, enabling data-driven decisions about code optimization and reuse strategies.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system performs preliminary analysis and annotation of code entries when they are first deposited into the repository. Usage tracking and effectiveness metrics are established from the outset, rather than requiring manual annotations later, making the identification of reusable code automatic and efficient.

Inventive Principle:

Principle #10Preliminary action

3Ease of operation

If developers work independently without a sharing platform, then code creation is straightforward, but code reuse and collaboration are limited

Engineering Contradiction:

Improvecode creation simplicityVSAvoidcode reusability

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The code repository acts as an intermediary platform between developers. Instead of developers directly sharing code with each other (which would require multiple pairwise connections), all code flows through the centralized repository, enabling any developer to access and reuse any code entry through the unified interface.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Productivity

If code is deployed without tracking, then deployment is fast, but continuous improvement and quality enhancement cannot be achieved

Engineering Contradiction:

Improvedeployment speedVSAvoidcode quality improvement

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system maintains continuous tracking of code usage and performance metrics even after deployment. This ongoing monitoring enables continuous identification of improvement opportunities, allowing the code base to evolve and improve over time while maintaining rapid deployment capabilities through automated processes.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS12112150B2Reusable code management for improved deployment of application code

Publication Date: 2024.10.08 BANK OF AMERICA CORP

AI summary

A code repository stores application code. A code management determines, based at least in part on requested features selected in a graphical user interface, code requirements that include attributes of application code needed to achieve the requested features. The code management system determines, based at least in part on the determined code requirements and the metadata for each entry of application code stored in the code repository, one or more candidate application code entries from the code repository. The code management system presents the candidate application code entries for user selection in the graphical user interface. After receipt of a user selection of a selected application code, the selected application code is provided to a computing device associated with the user.