Abstracting business logic into centralized database controls

• US 8,924,921 B2
• Filed: 04/20/2009
• Issued: 12/30/2014
• Est. Priority Date: 04/20/2009
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Rush, Jon, Salz, Richard Donald, Sandberg, Michael John, Tate, Kay Anderson
• Primary Examiner(s): Do, Chat
• Assistant Examiner(s): CURBELO III, SERGIO JOSE
• Application Number:
  US12/426,722
• Publication Number:
  US 20100269088A1
• Time in Patent Office: 2,080 Days
• Field of Search: 717/104, 717/106, 703 1- 22, 707790-812
• US Class Current: 717/104
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems

Abstract

Methods, systems, and products for abstracting business logic into centralized database controls are disclosed herein. In one general embodiment, a method, executed by a computer system, includes identifying data use code in business logic: analyzing the data use code to determine a general data model: and implementing the general data model in the centralized database controls. The general data model is an abstraction embodying the functionality inherent in the data use code. In specific embodiments, identifying data use code in the business logic may be carried out by identifying the data use code in at least one subcomponent of the business logic, such as a user interface code component, a database coding, a table, or a file. The computer system may remove the data use code from the business logic or designate the data use code for removal.

Claims

1. A computer-implemented method for abstracting business logic in a legacy application into a relational database, the method comprising:

identifying the data use code in one or more subcomponents of the business logic comprising business logic code, user interface code, one or more data tables, one or more files, and database coding, the identifying the data use code comprising;

analyzing the business logic code for implementing a business rule; and

analysing the user interface code, the one or more data tables, the one or more files, and the database coding for constraint checking code and data model information,

wherein the business logic code contains a first instance of the data use code,

wherein the user interface code contains a second instance of the data use code, and

wherein the one or more files contain a third instance of the data use code;

consolidating the first instance of the data use code in the business logic code and the second instance of the data use code in the user interface code to generate a first general data model;

consolidating the third data code instance in the one or more files to generate a second general data model;

implementing the first and the second general data models, in centralized database controls, comprising;

creating a stored procedure for the business rule implementation identified in the analyzed data use code;

creating one or more database triggers for the constraint checking code identified in the analyzed data use code; and

creating a database artifact for the data model information identified in the analyzed data use code;

2. The computer implemented method according to claim 1, further comprising designating the data use code for removal.

3. The computer implemented method according to claim 2, further comprising removing the data use code in the legacy application.

4. A computer program product disposed on a non-transitory computer-readable medium for abstracting business logic in a legacy application into a relational database, the computer program product comprising:

computer program instructions for identifying data use code in one or more subcomponents of the business logic comprising business logic code, user interface code, one or more data table, one or more files, and database coding, the computer program instructions for identifying the data use code comprising;

computer program instructions for analysing the business logic code for implementing a business rule; and

computer program instructions for analysing the user interface code, the one or more data tables, the one or more files, and the database coding for constraint checking code and data model information,

wherein the business logic code contains a first instance of the data use code,

wherein the user interface code contains a second instance of the data use code, and

wherein the one or more files contain a third instance of the data use code

computer program instructions for consolidating the first instance of the data use code in the business logic code and the second instance of the data use code in the user interface code to generate a first general data model;

computer program instructions for consolidating the third data code instance in the one or more files to generate a second general data model;

computer program instructions for implementing the first and second general data models in centralized database controls, comprising;

computer program instructions for creating a stored procedure for the business rule implementation identified in the analyzed data use code;

computer program instructions for creating one or more database triggers for the constraint checking code identified in the analyzed data use code; and

computer program instructions for creating a database artifact for the data model information identified in the analyzed data use code.

5. The computer program product according to claim 4, further comprising computer program instructions for designating the data use code for removal.

6. The computer program product according to claim 5, further comprising computer program instructions for removing the data use code in the legacy application.

7. A system for abstracting business logic into a relational database, the system comprising:

a processor; and

a computer memory operatively coupled to the processor, the computer memory having disposed within it;

computer program instructions for identifying data use code in one or more subcomponents of the business logic comprising business logic code, user interface code, one or more data tables, one or more files, and database coding, the computer program instructions for identifying the data use code comprising;

computer program instructions for analyzing the business logic code for implementing a business rule; and

computer program instructions for analyzing the user interface code, the one or more data tables, the one or more files, and the database coding for constraint checking code and data model information,

wherein the business logic code contains a first instance of the data use code,

wherein the user interface code contains a second instance of the data use code, and

wherein the one or more files contain a third instance of the data use code

computer program instructions for consolidating the first instance of the data use code in the business logic code and the second instance of the data use code in the user interface code to generate a first general data model;

computer program instructions for consolidating the third data code instance in the one or more files to generate a second general data model;

computer program instructions for implementing the first and second general data model in centralized database controls, comprising;

computer program instructions for creating a stored procedure for the business rule implementation identified in the analyzed data use code;

computer program instructions for creating one or more database triggers for the constraint checking code identified in the analysed data use code; and

computer program instructions for creating a database artifact for the data model information identified in the analyzed data use code.

8. The system according to claim 7, further comprising computer program instructions for designating the data use code for removal.

9. The system according to claim 8, further comprising computer program instructions for removing the data use code in the legacy application.