Intermediate Code Analysis Using Repository Difference Reproduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing code analysis methods struggle to perform analysis on software in an intermediate state before it is uploaded to the cloud environment, leading to delayed reporting of results due to limited computational resources and functions in local environments, and inefficiencies in selecting required test codes.

Innovation Solution

An information processing device and method that acquires difference information between local and remote repositories to reproduce and analyze intermediate state code, using a machine learning model to select test codes based on code modification history and test history, combined with rule-based selection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If code analysis is performed in a local environment, then analysis speed is fast and results are reported early, but computational resources are limited and functional capabilities are restricted

Engineering Contradiction:
Improveanalysis timeVSAvoidfunctional capabilities
Core Design Contradiction:
Loss of timeVSAdaptability or versatility

Solution Approach 1:

The code analysis process is segmented into two phases: a preliminary analysis phase that runs locally on the developer's machine for quick feedback, and a comprehensive analysis phase that runs in the cloud environment for deep inspection. This segmentation allows the system to provide both fast initial results and thorough analysis capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary code analysis actions locally before the developer commits code to the repository. By analyzing code changes in the local environment first, the system provides early feedback to developers while reserving cloud resources for more comprehensive analysis after commit.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If code analysis is performed in a cloud environment, then computational resources are abundant and processing speed increases, but code must be committed first which delays analysis

Engineering Contradiction:
Improveprocessing speedVSAvoidcommit waiting time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary code analysis actions locally before the developer commits code to the repository. By analyzing code changes in the local environment first, the system provides early feedback to developers while reserving cloud resources for more comprehensive analysis after commit.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The local environment acts as an intermediary between the developer's IDE and the cloud analysis service. It captures code changes locally, performs initial analysis, and then transmits relevant information to the cloud environment for comprehensive processing, eliminating the need to wait for commit before starting analysis.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If comprehensive code analysis is performed on all code changes, then analysis thoroughness is high, but resource consumption and analysis time increase

Engineering Contradiction:
Improveanalysis thoroughnessVSAvoidcomputational resource consumption
Core Design Contradiction:
Measurement precisionVSLoss of energy

Solution Approach 1:

The system applies different analysis depths to different parts of the codebase. Frequently changed modules receive comprehensive analysis, while stable modules receive lighter inspection. This local quality approach ensures thoroughness where needed while conserving computational resources in stable areas.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system performs partial code analysis by focusing only on the specific code changes introduced in the current commit rather than analyzing the entire codebase. This selective approach maintains high analysis thoroughness for changed code while significantly reducing overall resource consumption.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12619522B2Information processing device, information processing method, and information processing system
Publication Date: 2026.05.05 SONY GROUP CORP
  • US12619522B2 patent drawing
  • US12619522B2 patent drawing
  • US12619522B2 patent drawing

AI summary

Provided is an information processing device that performs processing regarding a code analysis of software that is in an intermediate state. The information processing device includes a difference information acquisition section and a code analysis section. The difference information acquisition section acquires difference information regarding the difference between a code stored in a first repository and a code stored in a second repository in correspondence with the code stored in the first repository. The code analysis section reproduces the code stored in the first repository from the code stored in the second repository, in reference to the difference information, and performs code analysis on the reproduced code. The information processing device reports the result of analysis by the code analysis section to the developer of the reproduced code.