Concurrent Program Code Comparison for Resource Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software developers face challenges in efficiently comparing and updating multiple versions of program code across different stages of the software development lifecycle, leading to errors and increased processor resource usage.

Innovation Solution

A system that concurrently compares multiple portions of code sets to identify differences, generating comparison information that highlights additions, deletions, and modifications, thereby reducing errors and conserving processor resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If sequential comparison of code portions is used, then processing accuracy is maintained, but processing time and resource consumption increase

Engineering Contradiction:
Improvecode comparison speedVSAvoidprocessor resource usage
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The code sets are divided into multiple portions that can be compared independently and concurrently. The system identifies corresponding portions between first and second code sets, allowing parallel processing of multiple comparison tasks simultaneously, thus improving productivity while managing processor resources efficiently.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Multiple code portion comparisons are merged into a single concurrent processing operation. The system combines the comparison of multiple first portions with their corresponding second portions in parallel, achieving faster overall comparison speed while optimizing processor resource utilization through coordinated parallel execution.

Inventive Principle:
Principle #5Merging (Combining)

2Ease of operation

If manual code comparison is performed, then detailed analysis is possible, but user effort and time consumption increase

Engineering Contradiction:
Improveuser effort in debuggingVSAvoidtime for understanding code differences
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs automated code comparison and independently generates comparison information identifying differences between code sets. This self-service capability eliminates the need for manual line-by-line analysis by developers, significantly reducing user effort and time consumption while maintaining accurate difference identification.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system provides structured feedback by generating comparison information that highlights specific differences between code portions. This automated feedback mechanism presents differences in an easily interpretable format, reducing the time and effort required for developers to understand code changes without sacrificing analysis depth.

Inventive Principle:
Principle #23Feedback

3Reliability

If comprehensive code comparison is performed, then all differences are identified, but processing complexity and resource usage increase

Engineering Contradiction:
Improveaccuracy of difference identificationVSAvoidcomparison system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The comprehensive comparison task is segmented into smaller, manageable portions that are processed independently. By dividing the code sets into multiple first and second portions, the system maintains accurate difference identification across the entire code base while reducing the complexity of individual comparison operations and optimizing resource usage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs comparison on selected portions of code rather than treating the entire code base as a single unit. This partial action approach allows comprehensive coverage of all necessary code sections while managing processing complexity through modular, incremental comparison of discrete portions.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10191737B2Program code comparison and reporting
Publication Date: 2019.01.29 ACCENTURE GLOBAL SOLUTIONS LTD
  • US10191737B2 patent drawing
  • US10191737B2 patent drawing
  • US10191737B2 patent drawing

AI summary

A device may include one or more processors. The device may obtain a first code set and a second code set. The first code set may have at least one difference from the second code set. The at least one difference may relate to addition, removal, or modification of code of the first code set in comparison to code of the second code set. The device may identify one or more first portions of the first code set and one or more second portions of the second code set. The device may concurrently compare the one or more first portions and the one or more corresponding second portions to identify the at least one difference. The device may generate comparison information identifying the at least one difference. The device may store or provide the comparison information.