IP Library Granted Patent US 12693854
Granted Patent B2
US 12693854 · App. 18/385,596 · Granted Jul 28, 2026

Systems and methods for evaluating computing programming code changes using AI to improve computing performance and component consumption

Inventors: A Likhitha (Hyderabad, IN); Yenamandra Satya Murthy (Hyderabad, IN)
Assignee: BANK OF AMERICA CORPORATION
G06F8/71G06F8/35
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12693854
App. No.
18/385,596
Granted
Jul 28, 2026
Kind
B2
Abstract

Systems, computer program products, and methods are described herein for evaluating computing programming code changes using AI to improve computing performance and component consumption. The present invention is configured to identify at least one code commit change; determine whether the at least one code commit change matches at least one runtime restriction statement; classify the at least one code commit change as a restriction code commit change; identify at least one object reference, at least one class, and at least one method associated with the restriction code commit change; initiate a trigger-class method trace module on the restriction code commit change, wherein the trigger-class method trace module generates at least one runtime restriction weight associated with each restriction code commit change; and initiate a trigger flow trace module on the restriction code commit change and generate at least one suggested code commit change.

Claims (98)

1 . A system for evaluating computing programming code changes using AI to improve computing performance and component consumption, the system comprising:

a memory device with computer-readable program code stored thereon;

at least one processing device, wherein executing the computer-readable code is configured to cause the at least one processing device to perform the following operations:

identify at least one code commit change;

compare the at least one code commit change to at least one runtime restriction statement stored in a rule-set database module;

determine whether the at least one code commit change matches the at least one runtime restriction statement;

classify, in response to determining the at least one code commit change matches the at least one runtime restriction statement, the at least one code commit change as an at least one restriction code commit change;

identify at least one object reference, at least one class, and at least one method associated with the at least one restriction code commit change;

initiate a trigger-class method trace module on the at least one restriction code commit change, wherein the trigger-class method trace module generates at least one runtime restriction weight associated with each restriction code commit change; and

initiate a trigger flow trace module on the at least one restriction code commit change,

wherein the trigger flow trace module generates at least one suggested code commit change based on at least one of the at least one runtime restriction weight, the at least one object reference, or the at least one method,

wherein the at least one suggested code commit change decreases a runtime restriction level;

wherein the trigger flow trace module comprises a trigger trace module, a trained artificial intelligence engine, and

wherein the trained artificial intelligence engine comprises a neural network, and wherein the trained artificial intelligence engine is configured to:

process the at least one code commit change;

determine whether the at least one code commit change is part of a trigger flow action, wherein the trigger flow action is based on the at least one runtime restriction statement associated with the at least one code commit change;

generate, in response to determining whether the at least one code commit change is part of the trigger flow action, a status update interface component,

wherein, in an instance where the at least one code commit change is part of the trigger flow action, the status update interface component comprises the at least one runtime restriction weight for the at least one code commit change and at least one previous committed runtime restriction weight, or

wherein, in an instance where the at least one code commit change is not part of the trigger flow action, the status update interface component comprises an accepted code change of the at least one code commit change; and

transmit the status update interface component to a user device and configure a graphical user interface of the user device with the status update interface component.

2 . The system of claim 1 , wherein the at least one code commit change is associated with at least one source code, at least one file, or at least one code repository comprising previously committed code.

3 . The system of claim 2 , wherein executing the computer-readable code is configured to cause the at least one processing device to perform the following operations:

identify at least one previous object reference associated with the previously committed code; and

determine, based on the at least one previous object reference, a previous committed runtime restriction weight.

4 . The system of claim 3 , wherein executing the computer-readable code is configured to cause the at least one processing device to perform the following operations:

identify at least one of at least one class, at least one method, or at least one runtime restriction statement for the previously committed code; and

determine, based on at least one of the at least one class, the at least one method, or the at least one runtime restriction statement for the previously committed code, the previous committed runtime restriction weight.

5 . The system of claim 1 , wherein the runtime restriction weight is based on the trigger flow action, and wherein the at least one object reference is based on an action location for the trigger flow action.

6 . The system of claim 1 , wherein executing the computer-readable code is configured to cause the at least one processing device to perform the following operations:

generate a pull request alert interface component based on the at least one suggested code commit change; and

transmit the pull request alert interface component to the user device, wherein the pull request alert interface component configures the graphical user interface of the user device.

7 . The system of claim 6 , wherein the at least one pull request alert interface component comprises an identifier associated with the at least one restriction code commit change.

8 . The system of claim 1 , wherein the trigger-class method module comprises at least one lexical analysis component comprising a regular expression component, and wherein the trigger-class method module is configured to:

identify, by the at least one lexical analysis component, the at least one class or the at least one method for the at least one code commit change;

analyze each method of the at least one method for the at least one code commit change;

determine, based on the analyzation of each method, the at least one runtime restriction statement based on the rule-set database module;

generate, based on the at least one runtime restriction statement, a runtime restriction weight;

refine the at least one code commit change associated with the at least one runtime restriction statement and identify the object reference for the at least one code commit change; and

maintain a logic flow associated with the at least one code commit change, wherein the logic flow comprises a hierarchical data format and the at least one object runtime restriction weight.

9 . The system of claim 1 , wherein the trigger trace module comprises at least one lexical analysis component comprising a regular expression component, and wherein the trigger trace module is configured to:

identify at least one trigger associated with the at least one code commit change, wherein the at least one trigger is associated with the at least one object reference;

analyze the at least one trigger associated with the at least one object reference;

identify, by the at least one lexical analysis component, at least one class-method callout associated with the at least one trigger;

analyze the at least one class-method callout and determine the at least one runtime restriction statement based on the rule-set database module;

generate, based on the at least one runtime restriction statement, a runtime restriction weight;

refine the at least one code commit change associated with the at least one runtime restriction statement and identify the object reference for the at least one code commit change; and

maintain a logic flow associated with the at least one code commit change, wherein the logic flow comprises a hierarchical data format and the at least one object runtime restriction weight.

10 . A computer program product for evaluating computing programming code changes using AI to improve computing performance and component consumption, wherein the computer program product comprises at least one non-transitory computer-readable medium having computer-readable program code portions embodied therein, the computer-readable program code portions which when executed by a processing device are configured to cause a processor to perform the following operations:

identify at least one code commit change;

compare the at least one code commit change to at least one runtime restriction statement stored in a rule-set database module;

determine whether the at least one code commit change matches the at least one runtime restriction statement;

classify, in response to determining the at least one code commit change matches the at least one runtime restriction statement, the at least one code commit change as an at least one restriction code commit change;

identify at least one object reference, at least one class, and at least one method associated with the at least one restriction code commit change;

initiate a trigger-class method trace module on the at least one restriction code commit change, wherein the trigger-class method trace module generates at least one runtime restriction weight associated with each restriction code commit change; and

initiate a trigger flow trace module on the at least one restriction code commit change,

wherein the trigger flow trace module generates at least one suggested code commit change based on at least one of the at least one runtime restriction weight, the at least one object reference, or the at least one method,

wherein the at least one suggested code commit change decreases a runtime restriction level;

wherein the trigger flow trace module comprises a trigger trace module, a trained artificial intelligence engine, and

wherein the trained artificial intelligence engine comprises a neural network, and wherein the trained artificial intelligence engine is configured to:

process the at least one code commit change;

determine whether the at least one code commit change is part of a trigger flow action, wherein the trigger flow action is based on the at least one runtime restriction statement associated with the at least one code commit change;

generate, in response to determining whether the at least one code commit change is part of the trigger flow action, a status update interface component,

wherein, in an instance where the at least one code commit change is part of the trigger flow action, the status update interface component comprises the at least one runtime restriction weight for the at least one code commit change and at least one previous committed runtime restriction weight, or

wherein, in an instance where the at least one code commit change is not part of the trigger flow action, the status update interface component comprises an accepted code change of the at least one code commit change; and

transmit the status update interface component to a user device and configure a graphical user interface of the user device with the status update interface component.

11 . The computer program product of claim 10 , wherein the at least one code commit change is associated with at least one source code, at least one file, or at least one code repository comprising previously committed code.

12 . The computer program product of claim 11 , wherein the computer-readable program code portions which when executed by the processing device are configured to cause the processor to perform the following operations:

identify at least one previous object reference associated with the previously committed code; and

determine, based on the at least one previous object reference, a previous committed runtime restriction weight.

13 . The computer program product of claim 12 , wherein the computer-readable program code portions which when executed by the processing device are configured to cause the processor to perform the following operations:

identify at least one of at least one class, at least one method, or at least one runtime restriction statement for the previously committed code; and

determine, based on at least one of the at least one class, the at least one method, or the at least one runtime restriction statement for the previously committed code, the previous committed runtime restriction weight.

14 . The computer program product of claim 10 , wherein the runtime restriction weight is based on the trigger flow action, and wherein the at least one object reference is based on an action location for the trigger flow action.

15 . A computer implemented method for evaluating computing programming code changes using AI to improve computing performance and component consumption, the computer implemented method comprising:

identifying at least one code commit change;

comparing the at least one code commit change to at least one runtime restriction statement stored in a rule-set database module;

determining whether the at least one code commit change matches the at least one runtime restriction statement;

classifying, in response to determining the at least one code commit change matches the at least one runtime restriction statement, the at least one code commit change as an at least one restriction code commit change;

identifying at least one object reference, at least one class, and at least one method associated with the at least one restriction code commit change;

initiating a trigger-class method trace module on the at least one restriction code commit change, wherein the trigger-class method trace module generates at least one runtime restriction weight associated with each restriction code commit change; and

initiating a trigger flow trace module on the at least one restriction code commit change,

wherein the trigger flow trace module generates at least one suggested code commit change based on at least one of the at least one runtime restriction weight, the at least one object reference, or the at least one method, and

wherein the at least one suggested code commit change decreases a runtime restriction level,

wherein the trigger flow trace module comprises a trigger trace module, a trained artificial intelligence engine, and

wherein the trained artificial intelligence engine comprises a neural network, and wherein the trained artificial intelligence engine is configured to:

process the at least one code commit change;

determine whether the at least one code commit change is part of a trigger flow action,

wherein the trigger flow action is based on the at least one runtime restriction statement associated with the at least one code commit change

generate, in response to determining whether the at least one code commit change is part of the trigger flow action, a status update interface component,

wherein, in an instance where the at least one code commit change is part of the trigger flow action, the status update interface component comprises the at least one runtime restriction weight for the at least one code commit change and at least one previous committed runtime restriction weight, or

wherein, in an instance where the at least one code commit change is not part of the trigger flow action, the status update interface component comprises an accepted code change of the at least one code commit change: and transmit the status update interface component to a user device and configure a graphical user interface of the user device with the status update interface component.

16 . The computer implemented method of claim 15 , wherein the at least one code commit change is associated with at least one source code, at least one file, or at least one code repository comprising previously committed code.

17 . The computer implemented method of claim 16 , wherein the computer implemented method further comprises:

identifying at least one previous object reference associated with the previously committed code; and

determining, based on the at least one previous object reference, a previous committed runtime restriction weight.

18 . The computer implemented method of claim 17 , wherein the computer implemented method further comprises:

identifying at least one of at least one class, at least one method, or at least one runtime restriction statement for the previously committed code; and

determining, based on at least one of the at least one class, the at least one method, or the at least one runtime restriction statement for the previously committed code, the previous committed runtime restriction weight.