System and method for managing changes to business rules

• US 7,827,206 B2
• Filed: 11/03/2005
• Issued: 11/02/2010
• Est. Priority Date: 11/03/2005
• Status: Expired due to Fees

• Current Assignee: LinkedIn Corporation (Microsoft Corporation)
• Original Assignee: International Business Machines Corporation
• Inventors: Joseph, Joshy, Sachdeva, Naveen, Holmes, Peter
• Primary Examiner(s): Trujillo; James
• Assistant Examiner(s): Singh; Amresh
• Application Number:
  US11/267,782
• Publication Number:
  US 20070100859A1
• Time in Patent Office: 1,825 Days
• Field of Search: 707/104.1, 707/100, 707/802, 705/7, 705/1
• US Class Current: 707/802
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A rules change management system and method. The system comprises a first computing system comprising a first memory system. The first memory system comprises a rules change management engine. The first computing system receives a set of meta-rules associated with rules stored in a second memory system within a second computing system. The set of meta-rules are stored in the first memory system. The computing system receives a request to change a rule of the rules. The rules change management engine applies at least one associated meta-rule of the set of meta-rules to the request. The rules change management engine determines if the request may be executed based on the applying.

Claims

1. A rules change management method, comprising:

receiving by a first computing system comprising a first computer processor and a first memory system, a set of meta-rules, wherein said first memory system comprises a rules change management engine, wherein said set of meta-rules is associated with rules stored in a second memory system within a second computing system comprising a second computer processor, wherein said meta-rules comprise conditions that must be satisfied before any change within each rule of said rules is permitted, wherein said conditions comprise allowable changes within each said rule against boundary conditions for parameters and data referenced within each said rule, wherein said changes are associated with changing a monetary limit and a boundary within each said rule, and wherein said meta-rules comprise additional conditions under which completely new rule sets may be created;

storing said set of meta-rules in said first memory system;

receiving by said first computing system from a rules administrator party via an administrator computer interface terminal, a first request to generate changes within a rule of said rules;

applying, by said rules change management engine, at least one associated meta-rule of said set of meta-rules to said first request, wherein said applying comprises first applying a first meta-rule of said set of meta-rules to a first portion within said rule and second applying a second meta-rule of said set of meta-rules to a second portion within said rule, wherein said first portion differs from said second portion, wherein said first meta-rule comprises a first explicit set of values allowable for said first portion, and wherein said second meta-rule comprises a differing second explicit set of values allowable for said second portion;

determining, by said first computer processor, if said request may be executed based on said applying, wherein said determining has determined that said first request may be executed based on said applying, wherein said first computer processor executes said rules change management engine to perform said determining;

identifying, by said first computing system, said at least one associated meta-rule;

transmitting, by said first computing system to an external validator, a second request for an evaluation of said first request, wherein said external validator comprises a human manager;

evaluating by said external validator in response to said second request, said first request;

deciding by said external validator, if said first request should be approved based on said evaluating;

performing, by said first computing system, a regression test to determine if said first request should be approved;

generating, by said first computing system, a rule change log report, wherein said rules change log report comprises results associated with said determining and results of said identifying;

storing, by said first computing system, said rule change log report; and

listing, by said first computing system, said first explicit set of values and said second explicit set of values.

2. The method of claim 1, further comprising:

executing by said rules change management engine, said first request;

changing, first boundary conditions for parameters and data referenced within said rule in response to said executing; and

storing said changed rule in said second memory system.

3. The method of claim 1, further comprising:

denying by said rules change management engine, said first request; and

maintaining, said rule in response to said denying.

4. The method of claim 1, wherein said deciding has determined that said first request may be approved based on said evaluating, and wherein said method further comprises:

approving by said external validator, said first request;

executing by said rules change management engine, said first request;

changing, said rule in response to said executing; and

storing said changed rule in said second memory system.

5. The method of claim 1, wherein said deciding has determined that said first request may not be approved based on said evaluating, and wherein said method further comprises:

denying by said external validator, said first request; and

maintaining, said rule in response to said denying.

6. The method of claim 1, wherein said first computing system and said second computing system are part of a same computing system.

7. The method of claim 1, wherein said first applying indicates that said first request may be executed, wherein said second applying indicates that said first request may not be executed, and wherein said determining has determined that said first request may be not executed based on said second applying.

8. The method of claim 1, wherein said first applying indicates that said first request may be executed, wherein said second applying indicates that said first request may not be executed, and wherein said determining has determined that said first request may be executed based on said first applying.

9. The method of claim 1, wherein said at least one associated meta-rule may specifies that said external validation is required before said determining, and wherein said method further comprises:

receiving, by said rules change management engine from said user, validation that said first request may be executed.

10. The method of claim 1, wherein said at least one associated meta-rule may specifies that external validation from a regression test is required before said determining, and wherein said method further comprises:

executing, by said rules change management engine, said regression test;

receiving, by said rules change management engine from results of said executed regression test, validation that said first request may be executed.

11. The method of claim 1, wherein said rules comprise monetary limits associated with product orders.

12. The method of claim 1, wherein said meta-rules comprise a condition stating that there is no change permitted to at least one rule of said rules.

13. The method of claim 1, wherein said meta-rules comprise a condition stating an allowable association between least one rule of said rules and a rule group.

14. The method of claim 1, wherein said meta-rules comprise conditions under which completely new rules and rule sets may be created that apply to a same problem domain.

15. The method of claim 1, wherein said meta-rules comprise a meta-rule specifying a relative priority of each rule of said rules with respect to each other rule of said rules.

16. The method of claim 1, further comprising:

performing, by said first computing system, a regression test to determine if said first request should be approved.

17. The method of claim 1, further comprising:

executing by said rules change management engine, said first request;

changing in response to said executing, conditions under which new rules and rule sets may be created that apply to a same problem domain;

creating said new rules and rule sets; and

storing said new rules and rule sets.

18. A first computing system comprising a first computer processor coupled to a first computer-readable memory system, said first memory system comprising a rules change management engine, said rules change management engine comprising instructions that when executed by the first computer processor implements a rules change management method, said method comprising:

receiving by said first computing system, a set of meta-rules, wherein said set of meta-rules is associated with rules stored in a second memory system within a second computing system, wherein said meta-rules comprise conditions that must be satisfied before any change within each rule of said rules is permitted, wherein said conditions comprise allowable changes within each said rule against boundary conditions for parameters and data referenced within each said rule, wherein said changes are associated with changing a monetary limit and a boundary within each said rule, and wherein said meta-rules comprise additional conditions under which completely new rule sets may be created;

storing said set of meta-rules in said first memory system;

receiving by said first computing system from a rules administrator party via an administrator computer interface terminal, a first request to generate changes within a rule of said rules;

applying, by said rules change management engine, at least one associated meta-rule of said set of meta-rules to said first request, wherein said applying comprises first applying a first meta-rule of said set of meta-rules to a first portion within said rule and second applying a second meta-rule of said set of meta-rules to a second portion within said rule, wherein said first portion differs from said second portion, wherein said first meta-rule comprises a first explicit set of values allowable for said first portion, and wherein said second meta-rule comprises a differing second explicit set of values allowable for said second portion;

determining, by said first computer processor, if said request may be executed based on said applying, wherein said determining has determined that said first request may be executed based on said applying, wherein said first computer processor executes said rules change management engine to perform said determining;

identifying, by said first computing system, said at least one associated meta-rule;

transmitting, by said first computing system to an external validator, a second request for an evaluation of said first request, wherein said external validator comprises a human manager;

evaluating by said external validator in response to said second request, said first request;

deciding by said external validator, if said first request should be approved based on said evaluating;

performing, by said first computing system, a regression test to determine if said first request should be approved;

generating, by said first computing system, a rule change log report, wherein said rules change log report comprises results associated with said determining and results of said identifying;

storing, by said first computing system, said rule change log report; and

listing, by said first computing system, said first explicit set of values and said second explicit set of values.

19. The computing system of claim 18, wherein said method further comprises:

executing by said rules change management engine, said first request;

changing, first boundary conditions for parameters and data referenced within said rule in response to said executing; and

storing said changed rule in said second memory system.

20. The computing system of claim 18, wherein said deciding has determined that said first request may not be approved based on said evaluating, and wherein said method further comprises:

denying by said external validator, said first request; and

maintaining, said rule in response to said denying.

21. A computer program product, comprising a computer readable medium comprising computer readable code that when executed on a first computer processor of a first computing system causes the first computing system to perform a rules change management method, said computer readable code comprising a rules change management engine, said method comprising:

receiving by said first computing system, a set of meta-rules, wherein said set of meta-rules is associated with rules stored in a second memory system within a second computing system, wherein said meta-rules comprise conditions that must be satisfied before any change within each rule of said rules is permitted, wherein said conditions comprise allowable changes within each said rule against boundary conditions for parameters and data referenced within each said rule, wherein said changes are associated with changing a monetary limit and a boundary within each said rule, and wherein said meta-rules comprise additional conditions under which completely new rule sets may be created;

storing said set of meta-rules in said first memory system;

receiving by said first computing system from a rules administrator party via an administrator computer interface terminal, a first request to generate changes within a rule of said rules;

applying, by said rules change management engine, at least one associated meta-rule of said set of meta-rules to said first request, wherein said applying comprises first applying a first meta-rule of said set of meta-rules to a first portion within said rule and second applying a second meta-rule of said set of meta-rules to a second portion within said rule, wherein said first portion differs from said second portion wherein said first meta-rule comprises a first ex licit set of values allowable for said first portion, and wherein said second meta-rule comprises a differing second explicit set of values allowable for said second portion;

determining, by said first computer processor, if said request may be executed based on said applying, wherein said determining has determined that said first request may be executed based on said applying, wherein said first computer processor executes said rules change management engine to perform said determining;

identifying, by said first computing system, said at least one associated meta-rule;

transmitting, by said first computing system to an external validator, a second request for an evaluation of said first request, wherein said external validator comprises a human manager;

evaluating by said external validator in response to said second request, said first request;

deciding by said external validator, if said first request should be approved based on said evaluating;

performing, by said first computing system, a regression test to determine if said first request should be approved;

generating, by said first computing system, a rule change log report, wherein said rules change log report comprises results associated with said determining and results of said identifying;

storing, by said first computing system, said rule change log report; and

listing, by said first computing system, said first explicit set of values and said second explicit set of values.

22. The computer program product of claim 21, wherein said method further comprises:

executing by said rules change management engine, said first request;

changing, first boundary conditions for parameters and data referenced within said rule in response to said executing; and

storing said changed rule in said second memory system.

23. The computer program product of claim 21, wherein said method further comprises:

denying by said rules change management engine, said first request; and

maintaining, said rule in response to said denying.

24. The computer program product of claim 21, wherein said deciding has determined that said first request may be approved based on said evaluating, and wherein said method further comprises:

approving by said external validator, said first request;

executing by said rules change management engine, said first request;

changing, said rule in response to said executing; and

storing said changed rule in said second memory system.

25. The computer program product of claim 21, wherein said deciding has determined that said first request may not be approved based on said evaluating, and wherein said method further comprises:

denying by said external validator, said first request; and

maintaining, said rule in response to said denying.

26. A process for integrating computing infrastructure, comprising integrating computer-readable code into a first computing system comprising a first computer processor, wherein said code comprises a rules change management engine, and wherein the code in combination with the first computing system is capable of performing a rules change management method comprising:

receiving by said first computing system, a set of meta-rules, wherein said set of meta-rules is associated with rules stored in a second memory system within a second computing system, wherein said meta-rules comprise conditions that must be satisfied before any change within each rule of said rules is permitted, wherein said conditions comprise allowable changes within each said rule against boundary conditions for parameters and data referenced within each said rule, wherein said changes are associated with changing a monetary limit and a boundary within each said rule, and wherein said meta-rules comprise additional conditions under which completely new rule sets may be created;

storing said set of meta-rules in said first memory system;

receiving by said first computing system from a rules administrator party via an administrator computer interface terminal, a first request to generate changes within a rule of said rules;

applying, by said rules change management engine, at least one associated meta-rule of said set of meta-rules to said first request, wherein said applying comprises first applying a first meta-rule of said set of meta-rules to a first portion within said rule and second applying a second meta-rule of said set of meta-rules to a second portion within said rule, wherein said first portion differs from said second portion, wherein said first meta-rule comprises a first explicit set of values allowable for said first portion, and wherein said second meta-rule comprises a differing second explicit set of values allowable for said second portion;

determining, by said first computer processor, if said request may be executed based on said applying, wherein said determining has determined that said first request may be executed based on said applying, wherein said first computer processor executes said rules change management engine to perform said determining;

identifying, by said first computing system, said at least one associated meta-rule;

transmitting, by said first computing system to an external validator, a second request for an evaluation of said first request, wherein said external validator comprises a human manager;

evaluating by said external validator in response to said second request, said first request;

deciding by said external validator, if said first request should be approved based on said evaluating;

performing, by said first computing system, a regression test to determine if said first request should be approved;

generating, by said first computing system, a rule change log report, wherein said rules change log report comprises results associated with said determining and results of said identifying;

storing, by said first computing system, said rule change log report; and

listing, by said first computing system, said first explicit set of values and said second explicit set of values.

27. The process of claim 26, wherein said method further comprises:

executing by said rules change management engine, said first request;

changing, first boundary conditions for parameters and data referenced within said rule in response to said executing; and

storing said changed rule in said second memory system.

28. The process of claim 26, wherein said method further comprises:

denying by said rules change management engine, said first request; and

maintaining, said rule in response to said denying.

29. The process of claim 26, wherein said deciding has determined that said first request may be approved based on said evaluating, and wherein said method further comprises:

approving by said external validator, said first request;

executing by said rules change management engine, said first request;

changing, said rule in response to said executing; and

storing said changed rule in said second memory system.

30. The process of claim 26, wherein said deciding has determined that said first request may not be approved based on said evaluating, and wherein said method further comprises:

denying by said external validator, said first request; and

maintaining, said rule in response to said denying.