Automated transaction and datasource configuration source code review

• US 10,592,391 B1
• Filed: 10/13/2017
• Issued: 03/17/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): Rampuria, Satish
• Application Number:
  US15/783,669
• Time in Patent Office: 886 Days
• Field of Search: 717120-135
• CPC Class Codes: G06F 11/302 where the computing system component is a software system
• CPC Class Codes: G06F 11/3409 for performance assessment
• 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 2201/81 Threshold
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A computer-implemented automated review method for transaction and datasource configuration source code files seeking to access a data store comprises the steps of receiving a request to review configuration source code files seeking to access the data store; checking the configuration source code files for a definition of a transaction manager; setting an issue flag if the configuration source code files do not include the definition of the transaction manager; checking the configuration source code files to determine whether a transaction definition is at an outer boundary of a service object or a method; setting the issue flag if the transaction definition does not appear before the start of the service object class or method definition; reviewing the status of the issue flag; issuing a halt signal if the issue flag is set; and issuing a proceed signal if the issue flag is not set.

Claims

1. A computer-implemented automated review method for transaction and datasource configuration source code files seeking to access a data store, the method comprising the steps of, wherein each step is performed by a processor of a computer:

receiving a request to review configuration source code files seeking to access the data store;

checking, using the processor of the computer, the configuration source code files for a definition of a transaction manager, wherein the definition includes a bean;

setting an issue flag if the configuration source code files do not include the definition of the transaction manager;

checking, using the processor of the computer, the configuration source code files to determine whether a transaction definition is at an outer boundary of a service object or a method;

setting the issue flag if the transaction definition does not appear before the start of the service object class or method definition;

checking, using the processor of the computer, the configuration source code files for loops within a service object method definition;

setting the issue flag if service object method definition includes any loop structures;

checking, using the processor of the computer, the configuration source code files for exception handling within data access object method definitions that change the contents of the data store, wherein the exception handling within data access object method definitions includes the term “

throws”

followed by a name of an exception handler cited in the first line of the method definition;

setting the issue flag if the method definition does not include an exception handler;

reviewing the status of the issue flag;

issuing a halt signal if the issue flag is set; and

issuing a proceed signal if the issue flag is not set.

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

checking, using the processor of the computer, the configuration source code files for changes in isolation level; and

setting the issue flag if the configuration source code files include the term “

read committed”

or “

read uncommitted”

.

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

checking, using the processor of the computer, the configuration source code files for a datasource definition; and

setting the issue flag if the datasource definition is not present or does not include a predetermined address.

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

checking, using the processor of the computer, the configuration source code files for asynchronous flows within a service object method; and

setting the issue flag if the method definition includes any asynchronous method or functions calls.

5. The computer-implemented automated review method of claim 1, wherein the configuration source code files may include data access object source code files.

6. The computer-implemented automated review method of claim 1, wherein the configuration source code files include files with the term “

applicationContext”

in the filename.

7. The computer-implemented automated review method of claim 1, wherein the definition of the transaction manager includes an address of a database connectivity framework transaction manager and the issue flag is set if the address is incorrect.

8. The computer-implemented automated review method of claim 1, wherein the transaction definition includes the term “

@Transactional (readOnly=True)”

or “

@Transactional (readOnly=False)”

appearing above the start of the class or method definition.

9. A computer-implemented automated review method for transaction and datasource configuration source code files seeking to access a data store, the method comprising the steps of, wherein each step is performed by a processor of a computer:

receiving a request to review configuration source code files seeking to access the data store;

checking, using the processor of the computer, the configuration source code files for a definition of a transaction manager, wherein the definition includes a bean;

setting an issue flag if the configuration source code files do not include the definition of the transaction manager;

checking, using the processor of the computer, the configuration source code files to determine whether a transaction definition is at an outer boundary of a service object or a method;

setting the issue flag if the transaction definition does not appear before the start of the service object class or method definition;

checking, using the processor of the computer, the configuration source code files for loops within a service object method definition;

setting the issue flag if service object method definition includes any loop structures;

checking, using the processor of the computer, the configuration source code files for exception handling within data access object method definitions that change the contents of the data store, wherein the exception handling within data access object method definitions includes the term “

throws”

followed by a name of an exception handler cited in the first line of the method definition;

setting the issue flag if the method definition does not include an exception handler;

checking, using the processor of the computer, the configuration source code files for changes in isolation level;

setting the issue flag if the configuration source code files include the term “

read committed”

or “

read uncommitted”

;

checking, using the processor of the computer, the configuration source code files for a datasource definition;

setting the issue flag if the datasource definition is not present or does not include a predetermined address;

reviewing the status of the issue flag;

issuing a halt signal if the issue flag is set; and

issuing a proceed signal if the issue flag is not set.

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

checking, using the processor of the computer, the configuration source code files for asynchronous flows within a service object method; and

setting the issue flag if the method definition includes any asynchronous method or functions calls.

11. The computer-implemented automated review method of claim 9, wherein the configuration source code files may include data access object source code files.

12. The computer-implemented automated review method of claim 9, wherein the configuration source code files include files with the term “

applicationContext”

in the filename.

13. The computer-implemented automated review method of claim 9, wherein the definition of the transaction manager includes an address of a database connectivity framework transaction manager and the issue flag is set if the address is incorrect.

14. The computer-implemented automated review method of claim 9, wherein the transaction definition includes the term “

@Transactional (readOnly=True)”

or “

@Transactional (readOnly=False)”

appearing above the start of the class or method definition.

15. A computer-implemented automated review method for transaction and datasource configuration source code files seeking to access a data store, the method comprising the steps of, wherein each step is performed by a processor of a computer:

receiving a request to review configuration source code files seeking to access the data store;

checking, using the processor of the computer, the configuration source code files for a definition of a transaction manager, including an address of a database connectivity framework transaction manager;

setting an issue flag if the configuration source code files do not include the definition of the transaction manager or the address is incorrect;

checking, using the processor of the computer, the configuration source code files to determine whether a transaction definition is at an outer boundary of a service object or a method;

setting the issue flag if the transaction definition does not appear before the start of the service object class or method definition;

checking, using the processor of the computer, the configuration source code files for loops within a service object method definition;

setting the issue flag if service object method definition includes any loop structures;

checking, using the processor of the computer, the configuration source code files for exception handling within data access object method definitions that change the contents of the data store, the exception handling including the term “

throws”

followed by a name of an exception handler cited in the first line of the method definition;

setting the issue flag if the method definition does not include the exception handler;

checking, using the processor of the computer, the configuration source code files for changes in isolation level;

setting the issue flag if the configuration source code files include the term “

read committed”

or “

read uncommitted”

;

checking, using the processor of the computer, the configuration source code files for a datasource definition;

setting the issue flag if the datasource definition is not present or does not include a predetermined address;

reviewing the status of the issue flag;

issuing a halt signal if the issue flag is set; and

issuing a proceed signal if the issue flag is not set.

16. The computer-implemented automated review method of claim 15, wherein the configuration source code files may include data access object source code files.

17. The computer-implemented automated review method of claim 15, wherein the configuration source code files include files with the term “

applicationContext”

in the filename.

18. The computer-implemented automated review method of claim 15, wherein the transaction definition includes the term “

@Transactional (readOnly=True)”

or “

@Transactional (readOnly=False)”

appearing above the start of the class or method definition.