Abstract: Disclosed herein is a method of managing decision logic. The method includes receiving data, storing the data, and receiving a set of rules. A decision is generated based at least in part on the data and on the set of rules, and is a part of the decision logic. The decision logic is managed in a first mode or a second mode. When in the first mode or the second mode, the set of rules is managed in the context of the data by a first user. The managing includes reviewing and editing the set of rules for the decision logic in the context of the data. The editing is done by at least one of (i) modifying a rule in the set of rules, (ii) creating another rule and adding it to the set of rules and (iii) making an exception to a rule in the set of rules.

Abstract: Disclosed herein is a method of managing decision logic. The method includes receiving data, storing the data, and receiving a set of rules. A decision is generated based at least in part on the data and on the set of rules, and is a part of the decision logic. The decision logic is managed in a first mode or a second mode. When in the first mode or the second mode, the set of rules is managed in the context of the data by a first user. The managing includes reviewing and editing the set of rules for the decision logic in the context of the data. The editing is done by at least one of (i) modifying a rule in the set of rules, (ii) creating another rule and adding it to the set of rules and (iii) making an exception to a rule in the set of rules.

Abstract: The present invention is a method of creating decision logic. A first set of rules for the decision logic is received. The user is queried for data and this data is stored in a memory. A first decision is generated for a user based at least in part on the data. Input is received from the user for editing the first set of rules to create a new set of rules for the decision logic in the context of data. A final decision is generated derived at least in part from the data using the new set of rules.

Abstract: The present invention is a method of creating decision logic. A first set of rules for the decision logic is received. The user is queried for data and this data is stored in a memory. A first decision is generated for a user based at least in part on the data. Input is received from the user for editing the first set of rules to create a new set of rules for the decision logic in the context of data. A final decision is generated derived at least in part from the data using the new set of rules.

Abstract: The present invention is a method of creating decision logic. A first set of rules for the decision logic is received. The user is queried for data and this data is stored in a memory. A first decision is generated for a user based at least in part on the data. Input is received from the user for editing the first set of rules to create a new set of rules for the decision logic in the context of data. A final decision is generated derived at least in part from the data using the new set of rules.

Abstract: The present invention is a method for business users to collaborate on a decision within a decision bubble. A decision bubble is a specifically created environment in which a group of collaborators can interact with the purpose of creating and modifying decisions or business rules, and through which the system captures interactions between collaborators and enables traceability with respect to the resulting decisions. Using a lightweight business process, a decision bubble is initiated by a business user, the bubble owner, and can have in its scope any section of the decisions being managed. The bubble owner may issue invitations to the bubble to collaborators, some of which may be suggested by the system using a reputation system that scores users with respect to types of tasks and entities. The decision bubble contains all the contextual information required for the bubble collaborators to collaborate on the implementation or modifications of the decisions or rules.

Abstract: The present invention is a method of creating decision logic. A first set of rules for the decision logic is received. The user is queried for data and this data is stored in a memory. A first decision is generated for a user based at least in part on the data. Input is received from the user for editing the first set of rules to create a new set of rules for the decision logic in the context of data. A final decision is generated derived at least in part from the data using the new set of rules.

Abstract: A computer-implemented method described for making a recommendation with respect to a plurality of items using a plurality of adaptive models or agents. The described method includes receiving one or more business rules; receiving a request for a recommendation; receiving attributes relating to the request; activating one or more adaptive agents such that each activated adaptive agent generates one or more recommendations with respect to the items based at least in part on an evaluation of prior outcomes relating to the items; selecting from among the one or more recommendations at least one final recommendation; and displaying the at least one final recommendation to a user. Related apparatus, systems, techniques and articles are also described.

Abstract: An approach is described for developing software that executes rules, such as business rules. A group of rule templates defines a rule structure for rules that may be executed by a rules engine. Separate ruleflow templates define tasks that entail the execution of rules. Each of the ruleflow templates associates a task with the group of rule templates. Because the ruleflow templates define the association between the tasks and the group of rule templates, during execution of the tasks a rules engine executes rules defined by the group of templates. User interfaces are automatically generated based on the group of rule templates. A user may interact with the user interfaces to edit the rules defined by the group of templates. After editing the rules, executing the tasks associated with the group of templates will cause execution of the modified rules.

Abstract: A computer-implemented method described for making a recommendation with respect to a plurality of items using a plurality of adaptive models or agents. The described method includes receiving one or more business rules; receiving a request for a recommendation; receiving attributes relating to the request; activating one or more adaptive agents such that each activated adaptive agent generates one or more recommendations with respect to the items based at least in part on an evaluation of prior outcomes relating to the items; selecting from among the one or more recommendations at least one final recommendation; and displaying the at least one final recommendation to a user. Related apparatus, systems, techniques and articles are also described.

Abstract: A novel approach for generating and updating rules allows non-technical users to create and modify rules. A rules generation system includes a rules engineer interface, user interfaces and a rules generator. The rules engineer interface is an interface through which a rules engineer, such as rules engineer, may generate templates. Templates contain data that define rule “templates” that in turn specify a rule structure, rule elements that may be chosen by a user, and rule elements that may not be chosen by user. Templates may also define a set of choices, for example values, that user may choose for those rule elements. Templates may also be used to generate user interfaces. The user interfaces guide a user to create or edit rules.

Abstract: An approach is described for developing software that executes rules, such as business rules. A group of rule templates defines a rule structure for rules that may be executed by a rules engine. Separate ruleflow templates define tasks that entail the execution of rules. Each of the ruleflow templates associates a task with the group of rule templates. Because the ruleflow templates define the association between the tasks and the group of rule templates, during execution of the tasks a rules engine executes rules defined by the group of templates. User interfaces are automatically generated based on the group of rule templates. A user may interact with the user interfaces to edit the rules defined by the group of templates. After editing the rules, executing the tasks associated with the group of templates will cause execution of the modified rules.

Abstract: An approach is described for developing software that executes rules, such as business rules. A group of rule templates defines a rule structure for rules that may be executed by a rules engine. Separate ruleflow templates define tasks that entail the execution of rules. Each of the ruleflow templates associates a task with the group of rule templates. Because the ruleflow templates define the association between the tasks and the group of rule templates, during execution of the tasks a rules engine executes rules defined by the group of templates. User interfaces are automatically generated based on the group of rule templates. A user may interact with the user interfaces to edit the rules defined by the group of templates. After editing the rules, executing the tasks associated with the group of templates will cause execution of the modified rules.

Abstract: The present invention is directed to a method and mechanism for using rules metaphors to implement rules and ruleflows. Examples of such rules metaphors include decision tables, trees, scoreboards, state transition diagrams, and questionaires. By providing a choice of different rules metaphors, a rule developer can advantageously tailor the framework by which rules are created and accessed to more closely match the specific processes or task being addressed.

Abstract: A novel approach for generating and updating rules allows non-technical users to create and modify rules. A rules generation system includes a rules engineer interface, user interfaces and a rules generator. The rules engineer interface is an interface through which a rules engineer, such as rules engineer, may generate templates. Templates contain data that define rule “templates” that in turn specify a rule structure, rule elements that may be chosen by a user, and rule elements that may not be chosen by user. Templates may also define a set of choices, for example values, that user may choose for those rule elements. Templates may also be used to generate user interfaces. The user interfaces guide a user to create or edit rules.

Abstract: A novel approach for generating and updating rules allows non-technical users to create and modify rules. A rules generation system includes a rules engineer interface, user interfaces and a rules generator. The rules engineer interface is an interface through which a rules engineer, such as rules engineer, may generate templates. Templates contain data that define rule “templates” that in turn specify a rule structure, rule elements that may be chosen by a user, and rule elements that may not be chosen by user. Templates may also define a set of choices, for example values, that user may choose for those rule elements. Templates may also be used to generate user interfaces. The user interfaces guide a user to create or edit rules.

Abstract: An approach is described for developing software that executes rules, such as business rules. A group of rule templates defines a rule structure for rules that may be executed by a rules engine. Separate ruleflow templates define tasks that entail the execution of rules. Each of the ruleflow templates associates a task with the group of rule templates. Because the ruleflow templates define the association between the tasks and the group of rule templates, during execution of the tasks a rules engine executes rules defined by the group of templates. User interfaces are automatically generated based on the group of rule templates. A user may interact with the user interfaces to edit the rules defined by the group of templates. After editing the rules, executing the tasks associated with the group of templates will cause execution of the modified rules.

Abstract: An approach is described for developing software that executes rules, such as business rules. A group of rule templates defines a rule structure for rules that may be executed by a rules engine. Separate ruleflow templates define tasks that entail the execution of rules. Each of the ruleflow templates associates a task with the group of rule templates. Because the ruleflow templates define the association between the tasks and the group of rule templates, during execution of the tasks a rules engine executes rules defined by the group of templates. User interfaces are automatically generated based on the group of rule templates. A user may interact with the user interfaces to edit the rules defined by the group of templates. After editing the rules, executing the tasks associated with the group of templates will cause execution of the modified rules.

Abstract: A novel approach for generating and updating rules allows non-technical users to create and modify rules. A rules generation system includes a rules engineer interface, user interfaces and a rules generator. The rules engineer interface is an interface through which a rules engineer, such as rules engineer, may generate templates. Templates contain data that define rule “templates” that in turn specify a rule structure, rule elements that may be chosen by a user, and rule elements that may not be chosen by user. Templates may also define a set of choices, for example values, that user may choose for those rule elements. Templates may also be used to generate user interfaces. The user interfaces guide a user to create or edit rules.

Abstract: An approach is described for developing software that executes rules, such as business rules. A group of rule templates defines a rule structure for rules that may be executed by a rules engine. Separate ruleflow templates define tasks that entail the execution of rules. Each of the ruleflow templates associates a task with the group of rule templates. Because the ruleflow templates define the association between the tasks and the group of rule templates, during execution of the tasks a rules engine executes rules defined by the group of templates. User interfaces are automatically generated based on the group of rule templates. A user may interact with the user interfaces to edit the rules defined by the group of templates. After editing the rules, executing the tasks associated with the group of templates will cause execution of the modified rules.