Patent Issued for Automated Transaction And Datasource Configuration Source Code Review (USPTO 10,592,391)

2020 MAR 26 (NewsRx) -- By a News Reporter-Staff News Editor at Insurance Daily News -- A patent by the inventors Anderson, Matthew (Bloomington, IL); Snyder, Richard T. (Colfax, IL); Galvin, Daniel George (Bloomington, IL), filed on October 13, 2017, was published online on March 30, 2020, according to news reporting originating from Alexandria, Virginia, by NewsRx correspondents.

Patent number 10,592,391 is assigned to State Farm Mutual Automobile Insurance Company (Bloomington, Illinois, United States).

The following quote was obtained by the news editors from the background information supplied by the inventors: “Field of the Invention

“Embodiments of the current invention relate to methods and devices for automatically reviewing transaction and datasource configuration source code that seeks to access a data store or database.

“Description of the Related Art

“Large-scale data stores, or databases, such as those maintained by an insurance provider or a financial institution, not only include a great volume of data, but are also accessed at a high frequency. An exemplary insurance provider may have anywhere from hundreds of thousands to tens of millions of customers or clients. Associated with each customer may be personal information, such as a name, a birthdate, an address, etc., and policy information, such as a homeowner’s policy with coverage terms and details about the house or property being covered, or an automobile policy with coverage terms and details about the vehicle being covered. Also associated with each customer may be account information, such as payment history and the like. All of this information is stored in one or more data stores. An exemplary insurance provider may further have thousands of employees, such as agents, representatives, adjusters, accountants, and so forth. Each employee may wish to access the data stores to create new policies, update existing policies, retrieve information about policies, delete accounts, retrieve account information, or the like. In addition, some requests for access may involve hundreds of accounts, such as preparing billing information on any given day. If the insurance provider also offers online or web service for customers to directly access policy or account information, then the traffic to the data stores could increase significantly.

“Access to the data stores is controlled by data store access software. The software may include deployables, which are built from source code files. Each task or type of task may require one or more deployables. For example, creating new policies may require a first one or more deployables, while updating policy data may require a second one or more deployables, and so forth. Given the volume of data to be handled and the frequency of access, each deployable must as efficient in adding, retrieving, or modifying data as possible. Typically, data store managers, database administrators (DBAs), data access developers, or other information technology (IT) personnel review the source code used to build the deployables to ensure proper operation and performance. Since new deployables, or modifications to existing deployables, may be built or updated every day, it is difficult for data store managers and IT personnel to adequately review the source code and ensure proper performance. This leads to either inefficient code being deployed or long delays in implementing properly operating deployables.

“Furthermore, the deployables may be created from at least three types of source code files. A first type of source code may provide modification to the data store contents, by adding, deleting, or changing data. A second type of source code may provide an interface between the first type of source code and applications, typically business applications, that seek to access the data store. A third type of source code may provide configuration of the software components of the first and second types of source code. It is possible that each type of source code may be written by a different group of coders or programmers. Each group may specialize in the type of source code that they write, but may have little knowledge of the requirements of the other types of source code. The fact that different groups with different concerns write the data store access source code may further contribute to inconsistencies and inefficiencies in the deployables.”

In addition to the background information obtained for this patent, NewsRx journalists also obtained the inventors’ summary information for this patent: “Embodiments of the current invention solve the above-mentioned problems and provide a distinct advance in the art of automated source code review. Specifically, embodiments of the current invention provide computer-implemented methods that may automatically review data store access source code files by checking for compliance with guidelines regarding configuration source code. The configuration source code may provide transaction and datasource definitions. Transactions are operations that may modify the contents of the data store, while the datasource may identify the data store. If any of the source code files do not comply with the guidelines, then deployment of the source code may be halted until issues can be examined.

“In one embodiment, the current invention provides a computer-implemented automated review method for transaction and datasource configuration source code files seeking to access a data store. The method may broadly comprise 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; checking 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 the configuration source code files for exception handling within data access object method definitions that change the contents of the data store; 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.

“In another embodiment, the current invention provides a computer-implemented automated review method for transaction and datasource configuration source code files seeking to access a data store. The method may broadly comprise 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; checking 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 the configuration source code files for exception handling within data access object method definitions that change the contents of the data store; setting the issue flag if the method definition does not include an exception handler; checking 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 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.

“In yet another embodiment, the current invention provides a computer-implemented automated review method for transaction and datasource configuration source code files seeking to access a data store. The method may broadly comprise 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, 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 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 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 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 a 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 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 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.

“This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Other aspects and advantages of the current invention will be apparent from the following detailed description of the embodiments and the accompanying drawing figures.”

The claims supplied by the inventors are:

“Having thus described various embodiments of the invention, what is claimed as new and desired to be protected by Letters Patent includes the following:

“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.”

URL and more information on this patent, see: Anderson, Matthew; Snyder, Richard T.; Galvin, Daniel George. Automated Transaction And Datasource Configuration Source Code Review. U.S. Patent Number 10,592,391, filed October 13, 2017, and published online on March 30, 2020. Patent URL: http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=%2Fnetahtml%2FPTO%2Fsrchnum.htm&r=1&f=G&l=50&s1=10,592,391.PN.&OS=PN/10,592,391RS=PN/10,592,391

(Our reports deliver fact-based news of research and discoveries from around the world.)