Business logic support

• US 6,850,922 B1
• Filed: 07/14/2000
• Issued: 02/01/2005
• Est. Priority Date: 07/14/2000
• Status: Expired due to Term

• Current Assignee: Kyndryl Incorporated (Kyndryl Holdings, Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Wason, James Richard
• Primary Examiner(s): Knight, Anthony
• Assistant Examiner(s): Holmes, Michael B.
• Application Number:
  US09/616,800
• Time in Patent Office: 1,663 Days
• Field of Search: 706 45- 60
• US Class Current: 706/47
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A mechanism to isolate and externalize the definition of business rules, and to support them using visual programming techniques (special editors for Java beans). This means that the rules can be set up by a business expert who does not need specialized programming skills. In addition, the Java beans are preferably implemented as dynamic Java beans.

Claims

1. A method for applying business rules to data used in a computer application, comprising the steps:

defining a set of business rules, each of the rules determining the validity of data used in an associated, defined computer application;

storing the rules on a table external of the computer application;

for each rule,

invoking the rule at the occurrence of each of a defined set of operations on the data and while the rule is stored in said external table,

identifying a predetermined trigger condition for the rule, and

processing the rule if the predetermined trigger condition is satisfied to determine if data used in the computer application are valid.

2. A method according to claim 1, wherein the identifying step includes the steps of:

identifying at least one data value;

identifying a trigger value; and

identifying an operator indicating how the data value will be compared to the trigger value.

3. A method of applying business rules to data used in a computer application, comprising the steps:

defining a set of business rules, each of the rules determining the validity of data in an associated, defined computer application;

storing the rules on a table external of the computer application;

for each rule,

invoking the rule at the occurrence of each of a defined set of operations on the data and while the rule is stored in said external table,

identifying a predetermined trigger condition for the rule,

invoking a predefined method if the trigger condition is partially satisfied, and

using the method to apply the rule to determine if data used in the computer application are valid.

4. A method for managing business rules for data used in a computer application, comprising the steps:

establishing a set of business rules, each of the rules including a trigger condition and a process, and each of the rules determining the validity of data in an associated, defined computer application;

storing the rules in a table external of the computer application;

performing a predefined operation on the data;

checking all the rules in the table to determine if any are invoked by the predefined operation;

for each rule that is invoked, determining whether the trigger condition of the rule is satisfied; and

for each rule the trigger condition of which is satisfied, implementing the process of the rule and while the rule is stored in said external table to determine if data in the computer application are valid.

5. A method according to claim 4, further comprising the steps of:

running an application using the data; and

changing any of the business rules without recompiling or reinstalling the application.

6. A method according to claim 4, further comprising the step, upon rule failure, defining a message and help for each rule using visual programming techniques.

7. A method according to claim 6, further comprising the step, upon rule execution, adding the help and message to an error message list.

12. A method according to claim 4, wherein each rule specifies the conditions under which the rule is invoked.

13. A method according to claim 4, comprising the further step of changing the business rules, wherein said changing does not require any changes to the associated application.

14. A method according to claim 4, comprising the further steps of:

providing a list of subtriggers; and

creating the trigger for each rule from the list of subtriggers.

8. A system for managing business rules for data used in a computer application, comprising:

means for establishing a set of business rules, each of the rules including a trigger condition and a process, and each of the rules determining the validity of data used in an associated, defined computer application;

a table, external of the computer application, for storing the rules;

means for performing predefined operations on the data;

means for checking all the rules in the table to determine if any are invoked by the predefined operation;

means for determining, for each rule that is invoked, whether the trigger condition of the rule is satisfied; and

means for implementing the process of each rule, the trigger condition of which is satisfied, while the rule is stored in said external table to determine if data used in the computer application are valid.

9. A system according to claim 8, further comprising:

means for running an application using the data; and

means for changing any of the business rules without recompiling or reinstalling the application.

10. A program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform method steps for managing business rules for data used in a computer application, said method steps comprising:

establishing a set of business rules, each of the rules including a trigger condition and a process, and each of the rules determining the validity of data in an associated, defined computer application;

storing the rules in a table external of the computer application;

performing a predefined operation on the data;

checking all the rules in the table to determine if any are invoked by the predefined operation;

for each rule that is invoked, determining whether the trigger condition of the rule is satisfied; and

for each rule the trigger condition of which is satisfied, implementing the process of the rule while the rule is stored in said external table to determine if data used in the computer application are valid.

11. A program storage device according to claim 10, wherein said method steps further comprise:

running an application using the data; and

changing any of the business rules without recompiling or reinstalling the application.