SOURCE CODE MIGRATION TOOL

• US 20180150380A1
• Filed: 11/28/2016
• Published: 05/31/2018
• Est. Priority Date: 11/28/2016
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Darbha, Kiran Subramanyam, Kotla, Srikanth
• Granted Patent: US 10,102,107 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/3604 Software analysis for verifying properties of programs byte-code verification G06F9/44589
• CPC Class Codes: G06F 11/3616 using software metrics
• CPC Class Codes: G06F 11/3624 by performing operations on the source code, e.g. via a compiler
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software

Abstract

A source code migration tool comprising a memory, a receiver, a resolved source code file generation engine, and a verification engine. The memory is configured to store source code for an application, a plurality of configuration files comprising one or more parameter values defining one or more parameters, and metadata corresponding to the application. The receiver is configured to receive notice that the application has migrated from a lower environment and the resolved source code file generation engine is configured to generate a resolved source code file based on the source code of the application. The verification engine is configured to perform one or more checks on the resolved source code file and determine whether the resolved source code file passes or fails each performed check. The checks comprise one or more of a parameter check, a metadata check, a connectivity check, a credentials check, and an access check.

Claims

1. A source code migration tool comprising:

a memory configured to store;

source code for an application;

a plurality of configuration files comprising one or more parameter values defining one or more parameters;

metadata corresponding to the application, the metadata comprising source code referred metadata and lower environment metadata;

a receiver configured to receive notice that the application has migrated from a lower environment; and

a resolved source code file generation engine configured to generate a resolved source code file based on the stored source code, wherein generating the resolved source code file comprises;

creating a copy of the source code;

modifying the copy of the source code by;

identifying each instance of a parameter within the copy of the source code;

determining, for each identified parameter, a corresponding parameter value in one of the plurality of configuration files;

substituting the determined parameter value for the parameter within the copy of the source code;

a verification engine configured to perform one or more checks on the resolved source code file before the application is executed in a production environment and determine whether the resolved source code file passes or fails each of the performed checks, wherein the checks comprise one or more of;

a parameter check comprising identifying, within the resolved source code file, each instance of a parameter that is not defined by a parameter value;

a metadata check comprising;

comparing the source code referred metadata to the lower environment metadata;

identifying each inconsistency between the source code referred metadata and the lower environment metadata;

a connectivity check comprising;

identifying each server required for executing the application;

confirming that the application can connect to each identified server;

a credentials check comprising verifying the validity of login credentials;

an access check comprising;

identifying, within the resolved source code file, each file and folder of a plurality of files and folders stored in a server that the application requires access to; and

confirming that the application has permission to access each identified folder.

2. The source code migration tool of claim 1, further comprising a flagging engine configured to flag one or more portions of the resolved source code file, wherein the flagged portions correspond to portions of the resolved source code file that failed the one or more checks.

3. The source code migration tool of claim 1, wherein a failed check comprises one or more of:

a determination that the resolved source code file comprises a parameter that is not defined by a parameter value;

an determination that the source code referred metadata is inconsistent with the lower environment metadata;

a determination that the application cannot connect to each identified server;

a determination that the login credentials do not match any credentials stored in the server;

a determination that the application does not have permission to access one or more of the identified files and folders.

4. The source code migration tool of claim 1, further comprising a reporting engine configured to generate a report comprising an identification of each check performed and a pass or fail status of each performed check.

5. The source code migration tool of claim 1, wherein the lower environment is a development environment.

6. The source code migration tool of claim 1, wherein the checks performed by the verification engine are based on user input.

7. The source code migration tool of claim 2, wherein flagging a portion of the resolved source code file comprises distinguishing some text of the resolved source code file from other text of the resolved source code file.

8. The source code migration tool of claim 1, wherein determining that the resolved source code file passed each performed check corresponds to a likelihood that the application can be executed without failure in the production environment.

9. A method comprising:

receiving notice that an application has migrated from a lower environment; and

generating a resolved source code file based on source code of the application, wherein the resolved source code file includes one or more parameter values that define one or more parameters;

performing one or more checks on the resolved source code of the application before the application is executed in a production environment, the checks comprising one or more of;

a parameter check comprising identifying, within the resolved source code file, each instance of a parameter that is not defined by a parameter value;

a metadata check comprising;

comparing source code referred metadata to lower environment metadata;

identifying each inconsistency between the source code referred metadata and the lower environment metadata;

a connectivity check comprising;

identifying each server required for executing the application;

confirming that the application can connect to each identified server;

a credentials check comprising verifying the validity of login credentials;

an access check comprising;

identifying, within the resolved source code file, each file and folder of a plurality of files and folders stored in a server that the application requires access to;

confirming that the application has permission to access each identified folder; and

determining whether the resolved source code file passes or fails each of the performed checks.

10. The method of claim 9, further comprising flagging one or more portions of the resolved source code file, wherein the flagged portions correspond to portions of the resolved source code file that failed the one or more checks.

11. The method of claim 9, wherein determining that the resolved source code file failed a check comprises one or more of:

a determination that the resolved source code file comprises a parameter that is not defined by a parameter value;

an determination that the source code referred metadata is inconsistent with the lower environment metadata;

a determination that the application cannot connect to each identified server;

a determination that the login credentials do not match any credentials stored in the server;

a determination that the application does not have permission to access one or more of the identified files and folders.

12. The method of claim 9, further comprising generating a report comprising an identification of each check performed and a pass or fail status of each performed check.

13. The method of claim 9, wherein the lower environment is a development environment.

14. The method of claim 9, wherein the one or more performed checks are based on user input.

15. The method of claim 10, wherein flagging a portion of the resolved source code file comprises distinguishing some text of the resolved source code file from other text of the resolved source code file.

16. The method of claim 9, wherein determining that the resolved source code file passed each performed check corresponds to a likelihood that the application can be executed without failure in the production environment.

17. One or more computer-readable non-transitory storage media embodying software that is operable when executed to:

receive notice that an application has migrated from a lower environment; and

generate a resolved source code file based on source code of the application, wherein the resolved source code file includes one or more parameter values that define one or more parameters;

perform one or more checks on the resolved source code of the application before the application is executed in a production environment, the checks comprising one or more of;

a parameter check comprising identifying, within the resolved source code file, each instance of a parameter that is not defined by a parameter value;

a metadata check comprising;

comparing source code referred metadata to lower environment metadata; and

identifying each inconsistency between the source code referred metadata and the lower environment metadata;

a connectivity check comprising;

identifying each server required for executing the application;

confirming that the application can connect to each identified server;

a credentials check comprising verifying the validity of login credentials;

an access check comprising;

identifying, within the resolved source code file, each file and folder of a plurality of files and folders stored in a server that the application requires access to; and

confirming that the application has permission to access each identified folder; and

determine whether the resolved source code file passes or fails each of the performed checks.

18. The media of claim 17, wherein the software is further operable when executed to flag one or more portions of the resolved source code file, wherein the one or more flagged portions correspond to portions of the resolved source code file that failed a check

19. The media of claim 17, wherein determining that the resolved source code file failed a check comprises one or more of:

a determination that the resolved source code file comprises a parameter that is not defined by a parameter value;

an determination that the source code referred metadata is inconsistent with the lower environment metadata;

a determination that the application cannot connect to each identified server;

a determination that the login credentials do not match any credentials stored in the server;

a determination that the application does not have permission to access one or more of the identified files and folders.

20. The media of claim 17, wherein the software is further operable when executed to generate a report comprising an identification of each check performed and a pass or fail status of each performed check.