Patent Issued for Automated Spring Wiring Source Code Review (USPTO 10,275,237)

2019 MAY 15 (NewsRx) -- By a News Reporter-Staff News Editor at Insurance Daily News -- State Farm Mutual Automobile Insurance Company (Bloomington, Illinois, United States) has been issued patent number 10,275,237, according to news reporting originating out of Alexandria, Virginia, by NewsRx editors.

The patent’s inventors are Anderson, Matthew (Bloomington, IL); Snyder, Richard T. (Colfax, IL); Galvin, Daniel George (Bloomington, IL).

This patent was filed on October 13, 2017 and was published online on May 13, 2019.

From the background information supplied by the inventors, news correspondents obtained the following quote: “Field of the Invention

“Embodiments of the current invention relate to methods and devices for automatically reviewing spring wiring 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.”

Supplementing the background information on this patent, NewsRx reporters 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 ‘spring wiring’, which defines the connections of the data store modification and application interface types of source code to specific frameworks and/or systems. The methods may check configuration source code files which may be written in extensible markup language. 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 spring wiring 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 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’; checking the configuration source code files for a stereotype of each data access object class definition; setting the issue flag if the configuration source code files do not include the term ‘@Repository’ before each data access object class 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.

“In another embodiment, the current invention provides a computer-implemented automated review method for spring wiring 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 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 definitions of templates belonging to a database connectivity framework; setting the issue flag if the configuration source code files do not include the definitions of the templates or if the definitions of the templates include improper addresses for the templates; checking the configuration source code files for templates belonging to a database connectivity framework to be autowired within a data access object class definition; setting the issue flag if the configuration source code files do not include the term ‘@Autowired’ before the definition of each template; 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’; checking the configuration source code files for a stereotype of each data access object class definition; setting the issue flag if the configuration source code files do not include the term ‘@Repository’ before each data access object class 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.

“In yet another embodiment, the current invention provides a computer-implemented automated review method for spring wiring 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 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 definitions of ‘JDBCTemplate’ and ‘NamedParameterJdbcTemplate’ templates; setting the issue flag if the configuration source code files do not include the definitions of the templates or if the definitions of the templates include improper addresses for the templates; checking the configuration source code files and data access object source code files for ‘JDBCTemplate’ and ‘NamedParameterJdbcTemplate’ templates to be autowired within a data access object class definition; setting the issue flag if the configuration source code files do not include the term ‘@Autowired’ before the definition of each template; checking the configuration source code files and data access object 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’; checking the configuration source code files for a stereotype of each data access object class definition; setting the issue flag if the configuration source code files do not include the term ‘@Repository’ before each data access object class 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.

“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:

“The invention claimed is:

“1. A computer-implemented automated review method for spring wiring configuration source code files seeking to access a data store, the method comprising 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”; checking the configuration source code files for a stereotype of each data access object class definition; setting the issue flag if the configuration source code files do not include the term “@Repository” before each data access object class definition; reviewing the status of the issue flag; issuing a halt signal if the issue flag is set; deploying a source code included in the configuration source code files during off-peak hours 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 the configuration source code files for definitions of templates belonging to a database connectivity framework; and setting the issue flag if the configuration source code files do not include the definitions of the templates or if the definitions of the templates include improper addresses for the templates.

“3. The computer-implemented automated review method of claim 2, wherein the templates include “JDBCTemplate” and “NamedParameterJdbcTemplate”.

“4. The computer-implemented automated review method of claim 2, wherein the configuration source code files include files with the term “applicationContext” in the filename.

“5. The computer-implemented automated review method of claim 1, further comprising the steps of: checking the configuration source code files for templates belonging to a database connectivity framework to be autowired within a data access object class definition; and setting the issue flag if the configuration source code files do not include the term “@Autowired” before the definition of each template.

“6. The computer-implemented automated review method of claim 5, wherein the templates include “JDBCTemplate” and “NamedParameterJdbcTemplate”.

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

“8. The computer-implemented automated review method of claim 1, wherein checking the configuration source code files for definitions of the namespace includes checking a project object model file written in extensible markup language.

“9. The computer-implemented automated review method of claim 1, wherein checking the configuration source code files for definitions of the namespace includes determining that the definition of the namespace has a version number that is greater than a version number threshold, and setting the issue flag if the definition of the namespace has the version number that is not greater than the version number threshold.

“10. The computer-implemented automated review method of claim 1, wherein checking the configuration source code files for the definition of the data store access driver includes determining that the definition of the data store access driver has a version number that is greater than a version number threshold, and setting the issue flag if the definition of the data store access driver has the version number that is not greater than the version number threshold.

“11. The computer-implemented automated review method of claim 1, wherein checking the configuration source code files for the definition of the data store access driver includes determining that the definition of the data store access driver includes a predetermined type of driver, and setting the issue flag if the definition of the data store access driver does not include the predetermined type of driver.

“12. A computer-implemented automated review method for spring wiring configuration source code files seeking to access a data store, the method comprising 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 definitions of templates belonging to a database connectivity framework; setting the issue flag if the configuration source code files do not include the definitions of the templates or if the definitions of the templates include improper addresses for the templates; checking the configuration source code files for templates belonging to a database connectivity framework to be autowired within a data access object class definition; setting the issue flag if the configuration source code files do not include the term “@Autowired” before the definition of each template; 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”; checking the configuration source code files for a stereotype of each data access object class definition; setting the issue flag if the configuration source code files do not include the term “@Repository” before each data access object class definition; reviewing the status of the issue flag; issuing a halt signal if the issue flag is set; deploying a source code included in the configuration source code files during off-peak hours if the issue flag is set; and issuing a proceed signal if the issue flag is not set.

“13. The computer-implemented automated review method of claim 12, wherein the templates include “JDBCTemplate” and “NamedParameterJdbcTemplate”.

“14. The computer-implemented automated review method of claim 12, wherein the configuration source code files include files with the term “applicationContext” in the filename.

“15. The computer-implemented automated review method of claim 12, wherein checking the configuration source code files for templates belonging to a database connectivity framework includes checking data access object source code files.

“16. The computer-implemented automated review method of claim 12, wherein checking the configuration source code files for definitions of the namespace includes checking a project object model file written in extensible markup language.

“17. The computer-implemented automated review method of claim 12, wherein checking the configuration source code files for definitions of the namespace includes determining that the definition of the namespace has a version number that is greater than a version number threshold, and setting the issue flag if the definition of the namespace has the version number that is not greater than the version number threshold.

“18. The computer-implemented automated review method of claim 12, wherein checking the configuration source code files for the definition of the data store access driver includes determining that the definition of the data store access driver has a version number that is greater than a version number threshold, determining that the definition of the data store access driver includes a predetermined type of driver, and setting the issue flag if the definition of the data store access driver has the version number that is not greater than the version number threshold or the definition of the data store access driver does not include the predetermined type of driver.

“19. A computer-implemented automated review method for spring wiring configuration source code files seeking to access a data store, the method comprising 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 definitions of “JDBCTemplate” and “NamedParameterJdbcTemplate” templates; setting the issue flag if the configuration source code files do not include the definitions of the templates or if the definitions of the templates include improper addresses for the templates; checking the configuration source code files and data access object source code files for “JDBCTemplate” and “NamedParameterJdbcTemplate” templates to be autowired within a data access object class definition; setting the issue flag if the configuration source code files do not include the term “@Autowired” before the definition of each template; checking the configuration source code files and data access object 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”; checking the configuration source code files for a stereotype of each data access object class definition; setting the issue flag if the configuration source code files do not include the term “@Repository” before each data access object class definition; reviewing the status of the issue flag; issuing a halt signal if the issue flag is set; deploying a source code included in the configuration source code files during off-peak hours if the issue flag is set; and issuing a proceed signal if the issue flag is not set.

“20. The computer-implemented automated review method of claim 19, wherein the configuration source code files include files with the term “applicationContext” in the filename.”

For the URL and additional information on this patent, see: Anderson, Matthew; Snyder, Richard T.; Galvin, Daniel George. Automated Spring Wiring Source Code Review. U.S. Patent Number 10,275,237, filed October 13, 2017, and published online on May 13, 2019. 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,275,237.PN.&OS=PN/10,275,237RS=PN/10,275,237

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