Automated data store access source code review

• US 10,585,663 B1
• Filed: 10/13/2017
• Issued: 03/10/2020
• Est. Priority Date: 10/13/2017
• Status: Active Grant

• Current Assignee: State Farm Mutual Automobile Insurance Company (State Farm)
• Original Assignee: State Farm Mutual Automobile Insurance Company (State Farm)
• Inventors: Anderson, Matthew, Snyder, Richard T., Galvin, Daniel George
• Primary Examiner(s): Tecklu, Isaac T
• Application Number:
  US15/783,319
• Time in Patent Office: 879 Days
• Field of Search: None
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 8/77 Software metrics
• CPC Class Codes: G06F 9/45529 Embedded in an application, e.g. JavaScript in a Web browser

Abstract

A computer-implemented automated review method for source code files seeking to access a data store comprises the steps of receiving a request to review data store access source code; determining computer files which include the data access source code; examining structured query language (SQL) source code files and determining compliance with non-syntax-related guidelines; examining data access object (DAO) source code files and determining compliance with guidelines for invoking SQL components within Java source code; examining configuration source code files and determining compliance with data store connection and object definition guidelines; examining configuration source code files and determining compliance with transaction-related guidelines; examining configuration source code files and determining compliance with datasource configuration guidelines; and issuing a halt signal if any of the guidelines are not followed.

Claims

1. A computer-implemented automated review method for source code files seeking to access a data store, the method comprising the steps of:

receiving a request to review data store access source code;

determining computer files which include the data access source code;

examining structured query language (SQL) source code files and determining compliance with non-syntax-related guidelines;

executing an explain command on SQL statements in the SQL source code files and producing an explain output including information about a sequence of operations for executing the SQL statements;

examining data access object (DAO) source code files and determining compliance with guidelines for invoking SQL components within Java source code;

examining configuration source code files and determining compliance with data store connection and object definition guidelines;

examining configuration source code files and DAO source code files and determining compliance with transaction-related guidelines;

examining configuration source code files and determining compliance with datasource configuration guidelines;

setting the issue flag if any of the guidelines are not followed;

reviewing the status of the issue flag;

issuing a first signal to information technology personnel to halt deployment of the source code files if the issue flag is set; and

issuing a second signal to information technology personnel to proceed with deployment of the source code files if the issue flag is not set.

2. The computer-implemented automated review method of claim 1, further comprising the steps of:

determining service operations in each source code file;

determining an execution frequency of each service operation based on business volumetrics; and

setting an issue flag if the execution frequency of any service operation is greater than an execution frequency threshold for each service operation.

3. The computer-implemented automated review method of claim 1, further comprising the steps of:

determining service operations in each source code file;

determining an execution time of each service operation based on business volumetrics; and

setting the issue flag if the execution time of any service operation is less than an execution time threshold.

4. The computer-implemented automated review method of claim 1, wherein the non-syntax-related guidelines for SQL source code files include determining the occurrence of specific SQL commands which are known to be time-consuming or resource-intensive to execute.

5. The computer-implemented automated review method of claim 1, wherein the non-syntax-related guidelines for SQL source code files include determining whether a type of data to be written to the data store matches a type of data in the data store.

6. The computer-implemented automated review method of claim 1, wherein the guidelines for invoking SQL source code within Java source code include checking for usage of spring Java database connectivity (JDBC) framework.

7. The computer-implemented automated review method of claim 1, wherein the guidelines for invoking SQL components within Java source code include checking that a type of data passed to the SQL components matches a type of data expected by the SQL components.

8. The computer-implemented automated review method of claim 1, wherein the guidelines for data store connection and object definitions include checking that a bean definition for a database points to the data store.

9. The computer-implemented automated review method of claim 1, wherein the guidelines for data store connection and object definitions include checking that pointers to open source framework software are correct.

10. The computer-implemented automated review method of claim 1, wherein the transaction-related guidelines include checking for the presence of a transaction manager definition.

11. The computer-implemented automated review method of claim 1, wherein the datasource configuration guidelines include checking for a definition of a datasource.

12. A computer-implemented automated review method for source code files seeking to access a data store, the method comprising the steps of:

receiving a request to review data store access source code;

determining computer files which include the data access source code;

examining structured query language (SQL) source code files and determining compliance with non-syntax-related guidelines, the guidelines including determining whether a type of data to be written to the data store matches a type of data in the data store;

executing an explain command on SQL statements in the SQL source code files and producing an explain output including information about a sequence of operations for executing the SQL statements;

examining data access object (DAO) source code files and determining compliance with guidelines for invoking SQL components within Java source code, the guidelines including checking that a type of data passed to the SQL components matches a type of data expected by the SQL components;

examining configuration source code files and determining compliance with data store connection and object definition guidelines, the guidelines including checking that a bean definition for a database points to the data store;

examining configuration source code files and DAO source code files and determining compliance with transaction-related guidelines, the guidelines including checking for the presence of a transaction manager definition;

examining configuration source code files and determining compliance with datasource configuration guidelines, the guidelines including checking for a definition of a datasource;

setting the issue flag if any of the guidelines are not followed;

reviewing the status of the issue flag;

issuing a first signal to information technology personnel to halt deployment of the source code files if the issue flag is set; and

issuing a second signal to information technology personnel to proceed with deployment of the source code files if the issue flag is not set.

13. The computer-implemented automated review method of claim 12, further comprising the steps of:

determining service operations in each source code file;

determining an execution frequency of each service operation based on business volumetrics; and

setting an issue flag if the execution frequency of any service operation is greater than an execution frequency threshold.

14. The computer-implemented automated review method of claim 12, further comprising the steps of:

determining service operations in each source code file;

determining an execution time of each service operation based on business volumetrics; and

setting the issue flag if the execution time of any service operation is less than an execution time threshold.

15. The computer-implemented automated review method of claim 12, wherein the non-syntax-related guidelines for SQL source code files include determining the occurrence of specific SQL commands which are known to be time-consuming or resource-intensive to execute.

16. The computer-implemented automated review method of claim 12, wherein the guidelines for invoking SQL source code within Java source code include checking for usage of spring Java database connectivity (JDBC) framework.

17. The computer-implemented automated review method of claim 12, wherein the guidelines for data store connection and object definitions include checking that pointers to open source framework software are correct.

18. A computer-implemented automated review method for data store access source code files, the method comprising the steps of:

receiving a request to review data store access source code;

determining computer files which include the data access source code;

determining service operations in each source code file;

determining an execution frequency and an execution time of each service operation based on business volumetrics;

setting an issue flag if the execution frequency of any service operation is greater than an execution frequency threshold;

setting the issue flag if the execution time of any service operation is less than an execution time threshold;

examining structured query language (SQL) source code files and determining compliance with non-syntax-related guidelines;

executing an explain command on SQL statements in the SQL source code files and producing an explain output including information about a sequence of operations for executing the SQL statements;

examining data access object (DAO) source code files and determining compliance with guidelines for invoking SQL source code within Java source code;

examining configuration source code files and determining compliance with data store connection and object definition guidelines;

examining configuration source code files and DAO source code files and determining compliance with transaction-related guidelines;

examining configuration source code files and determining compliance with datasource configuration guidelines;

setting the issue flag if any of the guidelines are not followed;

reviewing the status of the issue flag;

issuing a first signal to information technology personnel to halt deployment of the source code files if the issue flag is set; and

issuing a second signal to information technology personnel to proceed with deployment of the source code files if the issue flag is not set.

19. The computer-implemented automated review method of claim 18, wherein the non-syntax-related guidelines for SQL source code files includes

determining the occurrence of specific SQL commands which are known to be time-consuming or resource-intensive to execute, and

determining whether a type of data to be written to the data store matches a type of data in the data store.

20. The computer-implemented automated review method of claim 18, wherein the guidelines for invoking SQL source code within Java source code include checking for usage of spring Java database connectivity (JDBC) framework, and checking that a type of data passed to the SQL components matches a type of data expected by the SQL components.