System and method for classifying software code based on functionality and criticality

A method for classifying software code, comprising:

• accessing a first log file and a second log file, wherein:
• the first log file comprising information about historical executions of a first software code;
• and
• the second log file comprising information about historical executions of a second software code;
• determining a first function of the first software code from the first log file;
• determining a first set of operations performed by the first software code from the first log file;
• determining that a first number of the first set of operations is within a first range of values;
• determining a first criticality level of the first software code based at least in part upon determining that the first number of the first set of operations is within the first range of values;
• determining a second function of the second software code from the second log file;
• determining a second set of operations performed by the second software code from the second log file;
• determining that a second number of the second set of operations is within the first range of values;
• determining a second criticality level of the second software code based at least in part upon determining that the second number of the second set of operations is within the first range of values;
• comparing each operation from among the first set of operations with a counterpart operation from among the second set of operations;
• determining, based at least in part upon the comparison of each operation, that the first software code has at least one operation in common with the second software code based at least in part upon the first set of operations and the second set of operations;
• comparing the first function of the first software code with the second function of the second software code;
• determining, based at least in part upon the comparison of the first function and with the second function, that the first function of the first software code corresponds to the second function of the second software code;
• classifying the first software code and the second software code in a first group, in response to:
• determining that the first software code has at least one operation in common with the second software code;
• determining that the first criticality level corresponds to the second criticality level;
• and
• determining that the first function of the first software code corresponds to the second function of the second software code;
• receive a request to update one or more software codes associated with the first function;
• and
• in response to receiving the request, executing a first update instruction that causes at least a first portion of the first software code and a second portion of the second software code that are related to the first function to be updated.

A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to:

• access a first log file and a second log file, wherein:
• the first log file comprising information about historical executions of a first software code;
• and
• the second log file comprising information about historical executions of a second software code;
• determine a first function of the first software code from the first log file;
• determine a first set of operations performed by the first software code from the first log file;
• determine that a first number of the first set of operations is within a first range of values;
• determine a first criticality level of the first software code based at least in part upon determining that the first number of the first set of operations is within the first range of values;
• determine a second function of the second software code from the second log file;
• determine a second set of operations performed by the second software code from the second log file;
• determine that a second number of the second set of operations is within the first range of values;
• determine a second criticality level of the second software code based at least in part upon determining that the second number of the second set of operations is within the first range of values;
• compare each operation from among the first set of operations with a counterpart operation from among the second set of operations;
• determine, based at least in part upon the comparison of each operation, that the first software code has at least one operation in common with the second software code based at least in part upon the first set of operations and the second set of operations;
• compare the first function of the first software code with the second function of the second software code;
• determine, based at least in part upon the comparison of the first function and with the second function, that the first function of the first software code corresponds to the second function of the second software code;
• classify the first software code and the second software code in a first group, in response to:
• determining that the first software code has at least one operation in common with the second software code;
• determining that the first criticality level corresponds to the second criticality level;
• and
• determining that the first function of the first software code corresponds to the second function of the second software code;
• receive a request to update one or more software codes associated with the first function;
• and
• in response to receiving the request, execute a first update instruction that causes at least a first portion of the first software code and a second portion of the second software code that are related to the first function to be updated.