State Farm Mutual Automobile Insurance Company

Matthew Anderson

Richard T Snyder

Daniel George Galvin

Nathan Lee Tofte

Nick U Christopulos

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.

Automated data store access source code review

A computer-implemented automated review method for structured query language (SQL) source code files seeking to access a data store comprises the steps of calculating an SQL complexity score; setting an issue flag if the SQL complexity score is greater than a threshold; checking the SQL source code for SQL-92 compliance; setting the issue flag if any of the SQL source code files is not SQL-92 compliant; comparing a type of data in the SQL source code files to be input to the data store with a type of a field in the data store set to receive the input data; setting the issue flag if the type of any input data does not match the type of a corresponding data store field; checking the SQL source code for SQL triggers set to activate when selected SQL commands are executed; and setting the issue flag if there are any SQL triggers.

Automated SQL source code review

A computer-implemented method for automatically reviewing structured query language (SQL) statements comprises the steps of receiving SQL code from a user seeking to access a database, parsing the SQL code to retrieve SQL keywords, mathematical operators, and logical operators, applying a complexity score calculation algorithm to the parsed code, calculating a complexity score, and executing the SQL code on a computing system which stores the database if the complexity score is less than or equal to a threshold. On the other hand, if the complexity score is greater than the threshold, the SQL code may be flagged to be rewritten.

Automatic review of SQL statement complexity

A computer-implemented automated review method for data access object (DAO) source code files seeking to access a data store comprises the steps of checking the DAO source code files for a database connectivity framework usage; setting an issue flag if the DAO source code files do not include any database connectivity framework usage; checking the DAO source code files for a configuration of structured query language (SQL) components; setting the issue flag if the SQL components are not of type 'SQL'; checking the DAO source code files for an injection of inputs into the SQL components; setting the issue flag if each input into the SQL components is not typed as a structured object or a single value; 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.

Automated data access object source code review

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.

Automated transaction and datasource configuration source code review

A computer-implemented automated review method for spring wiring 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 definitions of a namespace; setting an issue flag if the configuration source code files do not include definitions of the namespace; checking the configuration source code files for a definition of a data store access driver; setting the issue flag if the configuration source code files do not include the definition of the data store access driver; checking the configuration source code files for a definition of a 'database'; setting the issue flag if the configuration source code files do not include the definition of the 'database'; reviewing the status of the issue flag; and issuing a halt signal or a proceed signal.

Automated spring wiring source code review

A system for providing vehicle information at an automobile point of purchase includes a user device having a camera or other image capturing device that is used to capture an image of an automobile. An application on or associated with the image capturing device can either transmit the image to a service provider for processing, or can implement one or more steps in a feature recognition process locally, and thereafter transmit the data to a service provider. In either case, the service provider can then complete the feature recognition processing and identify the automobile from the image. The service provider can then communicate with a make and model database to provide useful information on the vehicle, which can then be transmitted to the user device and conveniently displayed.

Growing community of inventors

Bloomington, IL, United States of America

Matthew Anderson