Software Reinstallation Prioritization by Usage Frequency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software reinstallation methods do not prioritize applications based on frequency of utilization, leading to inefficiencies and user frustration, especially when reinstalling on a new computer system.

Innovation Solution

A system and method that tracks the frequency of utilization for each software application and library, allowing users to prioritize reinstallation based on usage statistics, with the option to reinstall the operating system first and deferring less frequently used applications and libraries for background installation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If all applications are reinstalled in alphabetical order or random order, then the reinstallation process is simple to implement, but the most frequently used applications are not prioritized causing user frustration and extended downtime

Engineering Contradiction:
Improvereinstallation efficiencyVSAvoiddowntime during system recovery
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by tracking and recording the usage frequency of each application before the reinstallation event occurs. This usage data is stored and later used to determine the installation sequence, ensuring that frequently used applications are prioritized without requiring real-time analysis during the reinstallation process

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The reinstallation system dynamically adapts its installation sequence based on usage frequency data. Instead of a fixed alphabetical or random order, the system reconfigures the installation queue dynamically, placing high-frequency applications at the beginning of the sequence and low-frequency applications at the end, optimizing recovery time based on actual user needs

Inventive Principle:
Principle #15Dynamics

2Reliability

If foreign language fonts and rarely used applications are reinstalled first, then complete system restoration is achieved, but urgent tasks cannot be performed due to system clutter and extended setup time

Engineering Contradiction:
Improvesystem restoration completenessVSAvoidsystem usability during reinstallation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The reinstallation process is segmented into priority tiers based on application usage frequency. Critical high-frequency applications are installed in the first phase, enabling immediate system usability. Lower-priority applications and components are installed in subsequent phases, ensuring complete restoration without blocking urgent tasks during the initial recovery period

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs partial reinstallation in phases rather than attempting to install all applications simultaneously. The first phase installs only the most essential high-frequency applications needed for immediate productivity, while lower-priority applications are deferred to background installation or later phases, providing sufficient functionality without complete system restoration upfront

Inventive Principle:
Principle #16Partial or excessive action

3Productivity

If usage tracking is implemented to prioritize reinstallation, then frequently used applications are reinstalled first improving productivity, but the system complexity increases with additional tracking software and configuration

Engineering Contradiction:
Improveapplication reinstallation priorityVSAvoidtracking system configuration
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system employs self-service mechanisms by automatically tracking application usage frequency through integrated monitoring of system logs and user activity patterns. This eliminates the need for manual tracking configuration or additional specialized software, as the system autonomously collects and analyzes usage data to determine installation priorities

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback loops by continuously monitoring application usage patterns and using this information to dynamically adjust the reinstallation priority sequence. Usage data serves as feedback that informs the optimization algorithm, creating a closed-loop system that automatically adapts to changing user needs without requiring manual intervention or complex configuration

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9146722B2Reinstalling a computer based on frequency of application utilization
Publication Date: 2015.09.29 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9146722B2 patent drawing
  • US9146722B2 patent drawing
  • US9146722B2 patent drawing

AI summary

A system and method for efficiently reinstalling computer software, which tracks frequency of utilization for each software application loaded onto the computer and reinstalls applications based on frequency of utilization, with the option to reinstall a computer operating system first or to reinstall computer applications along with libraries, so that computer users can resume working as soon as possible instead of waiting many hours for the entire reinstallation image to complete before a computer system reboot allows for continuation of computer usage.