Relational logic management system

Abstract

In one aspect, the invention relates to a method to propagate relations between a first rule set and a second rule set wherein the first and second rule sets are invoked by a common workflow model. The method includes tracing paths forward through the workflow model from the first rule set to the second rule set. Enumerating relations that extend forward from the first rule set to the second rule set is another step in the method. Additionally, using multi-valued logic, calculating the effects to the relations of control flow through the workflow model from the first rule set to the second rule set, tracing paths backward through the workflow model from the first rule set to the second rule set, enumerating relations that extend backward form the second rule set to the first rule set, and using multi-valued logic, calculating the effects on the relations of control flow backwards through the workflow model from the second rule set to the first rule set are also steps in the method.

What is claimed is: 
     
         1 . A method for implementation by one or more data processors comprising:
 receiving, by at least one data processor, user-generated input via a user interface capturing at least one sequence of steps and rule sets of a first workflow model of a business process;   storing, by at least one data processor, the sequence of steps and rule sets as a single business logic module;   storing, by at least one data processor, relational information computed for each variable used in the sequence within the single business logic module; and   enabling, by at least one data processor, reuse of the single business logic module for another workflow model for a different business process.   
     
     
         2 . A method as in  claim 1 , wherein relations between a first business parameter and a second business parameter are invoked by the workflow model. 
     
     
         3 . A method as in  claim 2 , wherein each business parameter is chosen from a group consisting of a workflow, a rule set, and a rule. 
     
     
         4 . A method as in  claim 2 , wherein the method further comprises:
 tracing, by at least one data processor, paths along a first direction through the first workflow model from the first business parameter to the second business parameter;   automatically enumerating, by at least one data processor, relations that extend along the first direction from first the business parameter to the second business parameter; and   computing, by at least one data processor using multi-valued logic, the effects on the relations of control flow through the workflow model from the first business parameter to the second business parameter.   
     
     
         5 . A method as in  claim 4 , wherein the first direction comprises a forward direction. 
     
     
         6 . A method as in  claim 4 , wherein the first direction comprises a backward direction. 
     
     
         7 . A method as in  claim 4 , further comprising:
 tracing, by at least one data processor, paths along a second direction different than the first direction through the workflow model from the second business parameter to the first business parameter;   automatically enumerating, by at least one data processor, relations that extend along the second direction from the second business parameter to the first business parameter; and   computing, by at least one data processor using multi-valued logic, the effects on the relations of control flow backwards through the workflow model from the second business parameter to the first business parameter.   
     
     
         8 . A method as in  claim 4 , wherein the tracing paths along a first direction through the workflow model from the first business parameter to the second business parameter comprises creating flow graphs characterizing the relations in a user interface. 
     
     
         9 . A method as in  claim 2 , further comprising:
 generating, by at least one data processor, a map organized at hierarchical levels and providing a view of the relationships between the first business parameter, the second business parameter, and other business parameters.   
     
     
         10 . A method as in  claim 2 , further comprising:
 providing, by at least one data processor, visual feedback in a graphical user interface to enable reconciliation of conflicts, redundancies, and/or overlaps between the first business parameter to the second business parameter within the workflow model.   
     
     
         11 . A method as in  claim 2 , wherein the first business parameter and the second business parameter utilize conflicting terminology or rules, and wherein the workflow model creates a format that allows interoperability between the first business parameter and the second business parameter. 
     
     
         12 . A method as in  claim 11 , wherein the first business parameter and the second business parameter are executed at different stages of a business process defined by the workflow model. 
     
     
         13 . A computer readable storage medium encoded with instructions, which when loaded in a computing device implements a method comprising:
 receiving user-generated input via a user interface capturing at least one sequence of steps and rule sets of a first workflow model of a business process;   storing the sequence of steps and rule sets as a single business logic module;   storing relational information computed for each variable used in the sequence within the single business logic module; and   enabling reuse of the single business logic module for another workflow model for a different business process.   
     
     
         14 . An article as in  claim 13 , wherein relations between a first business parameter and a second business parameter are invoked by the workflow model. 
     
     
         15 . An article as in  claim 14 , wherein each business parameter is chosen from a group consisting of a workflow, a rule set, and a rule. 
     
     
         16 . An article as in  claim 14 , wherein the implemented method further comprises:
 tracing paths along a first direction through the first workflow model from the first business parameter to the second business parameter;   automatically enumerating relations that extend along the first direction from first the business parameter to the second business parameter; and   computing, using multi-valued logic, the effects on the relations of control flow through the workflow model from the first business parameter to the second business parameter.   
     
     
         17 . An article as in  claim 16 , wherein the first direction comprises a forward direction. 
     
     
         18 . An article as in  claim 16 , wherein the first direction comprises a backward direction. 
     
     
         19 . An article as in  claim 16 , wherein the implemented method further comprises:
 tracing paths along a second direction different than the first direction through the workflow model from the second business parameter to the first business parameter;   automatically enumerating relations that extend along the second direction from the second business parameter to the first business parameter; and   computing, using multi-valued logic, the effects on the relations of control flow backwards through the workflow model from the second business parameter to the first business parameter.   
     
     
         20 . An article as in  claim 16 , wherein the tracing paths along a first direction through the workflow model from the first business parameter to the second business parameter comprises creating flow graphs characterizing the relations in a user interface. 
     
     
         21 . An article as in  claim 14 , wherein the implemented method further comprises:
 generating a map organized at hierarchical levels and providing a view of the relationships between the first business parameter, the second business parameter, and other business parameters.   
     
     
         22 . A method as in  claim 21 , wherein the implemented method further comprises:
 providing visual feedback in a graphical user interface to enable reconciliation of conflicts, redundancies, and/or overlaps between the first business parameter to the second business parameter within the workflow model.   
     
     
         23 . An article as in  claim 22  wherein the first business parameter and the second business parameter utilize conflicting terminology or rules, and wherein the workflow model creates a format that allows interoperability between the first business parameter and the second business parameter. 
     
     
         24 . An article as in  claim 23 , wherein the first business parameter and the second business parameter are executed at different stages of a business process defined by the workflow model. 
     
     
         25 . A method for implementation by one or more data processors comprising:
 receiving, by at least one data processor, user-generated input via a user interface capturing at least one sequence of steps and rule sets of a first workflow model of a first business process;   storing, by at least one data processor, the sequence of steps and rule sets as a single business logic module;   storing, by at least one data processor, relational information computed for each variable used in the sequence within the single business logic module; and   enabling, by at least one data processor, reuse of the single business logic module for a second workflow model for a second business process, wherein the second workflow model incorporates the stored sequence of steps and rules sets as well as other steps and rules sets.