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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

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.

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.

Abstract: 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.