Source Code Error Reoccurrence Prevention System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software development tools do not actively monitor source code errors and corresponding fixes over time, leading to a need for systems that can identify and prevent source code error reoccurrence.

Innovation Solution

A computerized method and system for continuous monitoring of source code development, which includes receiving and storing source code files with modification records, identifying and notifying developers of potential errors, and preventing the commit of modified files that may reintroduce errors, using a centralized repository and communication network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If developers manually monitor and track source code errors over time, then error reoccurrence can be prevented, but this requires considerable time and effort from developers

Engineering Contradiction:
Improveerror preventionVSAvoiddeveloper time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system automatically monitors source code changes, compares them against the error database, and sends notifications without requiring developer intervention. The server computing device performs autonomous error detection and alerting, freeing developers from manual monitoring tasks while maintaining high reliability in error prevention.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system establishes a feedback loop where source code changes are continuously monitored, automatically compared with the error database, and notifications are sent back to developers when potential errors are detected. This automated feedback mechanism prevents error reoccurrence while minimizing developer time investment.

Inventive Principle:
Principle #23Feedback

2Reliability

If software tools actively monitor and alert developers of source code errors in real-time, then error reoccurrence is prevented, but the system complexity increases

Engineering Contradiction:
Improveerror detectionVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a server computing device as an intermediary between the source code repository and developers. This intermediary automatically monitors code changes, compares them with the error database, and sends notifications. By placing this intelligent mediator in the middle, the system achieves reliable error detection without requiring complex integration into each developer's workflow or tools.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The error monitoring and notification functionality is extracted as a separate, standalone system (server computing device) rather than being embedded within existing development tools. This extraction simplifies the overall system architecture by creating an independent error prevention service that can be added to any development workflow without modifying existing tools.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If developers review and correct source code errors before committing changes, then error reoccurrence is reduced, but this slows down the development process

Engineering Contradiction:
Improveerror preventionVSAvoiddevelopment speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary error detection by maintaining a database of known errors and their fixes, and automatically comparing upcoming code changes against this database before commits are finalized. By detecting potential errors in advance through automated comparison and notification, developers can make informed decisions without manual review, maintaining both high reliability and development speed.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20220253371A1Systems and methods for source code error reoccurrence prevention
Publication Date: 2022.08.11 FMR CORP
  • US20220253371A1 patent drawing
  • US20220253371A1 patent drawing
  • US20220253371A1 patent drawing

AI summary

Systems and methods for preventing source code error reoccurrence. The method includes receiving a source code file including a record of modifications of the source code and a record of source code errors. The method also includes storing the source code file in a database. The method further includes receiving a modified source code file including an identification of a user that created the modified source code file on a user device. The method also includes determining a portion of the source code file that has been modified based on a comparison of the source code file and the modified source code file. The method further includes determining whether the portion of the source code file that has been modified corresponds to an error in the record of source code errors. The method also includes generating a notification corresponding to the error for display on the user device.