Source Code Dependency Risk Evaluation for Task Automation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing source code verification methods for task automation are complex, time-consuming, prone to human errors, and fail to adequately address risks associated with referenced source code, leading to potential malfunctions and resource-intensive troubleshooting.

Innovation Solution

A system and method to analyze source code and referenced code to identify dependencies, decompose them into tasks, evaluate operations for risks, and generate reports to modify the code before execution, using modular rules and context analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual verification methods are used for source code, then verification can be performed, but the process becomes complex and time-consuming

Engineering Contradiction:

Improveverification accuracyVSAvoidverification time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces manual verification processes with automated computational analysis. The system uses computer-implemented methods to automatically analyze source code, identify dependencies, and evaluate risks without human intervention in the verification process itself, thereby reducing time loss while maintaining reliability through systematic automated evaluation.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent performs preliminary analysis of source code before execution by identifying dependencies and evaluating risks in advance. This preliminary action includes obtaining referenced source code, decomposing it into tasks, and assessing potential risks before the automation is deployed, preventing issues rather than detecting them after execution.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If comprehensive source code analysis is performed, then risks are identified, but computing resources are consumed

Engineering Contradiction:

Improverisk identification accuracyVSAvoidcomputing resource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments the source code analysis into distinct components: dependency identification, task decomposition, and risk evaluation. By dividing the comprehensive analysis into modular stages, the system processes only relevant portions of the code at each stage, reducing overall computing resource consumption while maintaining thorough risk identification through systematic segmentation of the analysis process.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS12468808B2Risk dependency evaluation of a source code for task automation

Publication Date: 2025.11.11 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A risk dependency platform may obtain a source code for task automation. The risk dependency platform may analyze the source code to determine one or more dependencies associated with the source code. The one or more dependencies may identify referenced source code that are included in the source code by reference. The risk dependency platform may obtain the referenced source code and may decompose the source code and the referenced source code into a plurality of tasks. The plurality of tasks may invoke a plurality of modules that are executables. The risk dependency platform may analyze the plurality of tasks to determine operations that are performed based on the plurality of modules being executed. The risk dependency platform may evaluate the operations to identify one or more risks associated with performing the operations. The risk dependency platform may perform an action based on the one or more risks.