Task: Define Rule Set |  |
Disciplines: Rule Design
Relationships
Roles | Primary Performer: Rule Architect | Additional Performers:
Inputs | Mandatory: Decision Point Table Rule Description Document | Optional: None
Outputs | Ruleset
Main Description
When designing an application using one BRE and a simple rule set this activity will be done quickly. The rule developer still needs to think about the parameters the exception management, what are the rule part of the rule set, and how they are executed. So for a simple unique rule set the following information needs to be designed and documented: Input, output parameters Type of data model Rule execution flow using a rule flow. But it is still possible with modern BRE to use re-entrant rule set, so executing a rule flow from a rule task or rule package. Exception management Inference objects like a result object which may be used to control the future execution of the caller application or the BRE. What are the rule part of the rule set What is their execution order. It is recommended to avoid using a ordering mechanism like the rule priority, but some time at a rule task level it is needed to use sorting mechanism When does a rule is not candidate to enter in a rule set. This is linked to the rule life cycle.
Steps
Define rule set parameters
Develop or enhance prototyped Rule Flow
Organize the tasks with the business logic and the technical rules needed to prepare the rule execution. There are always a need to have some functions, technical rules, or asserting type of rules (rule without conditions which are asserting object in working memory) that needs to be included in pre or post processing of the rule flow.
Selecting and Extracting the Rule Artifacts that Go Into the Ruleset
Work on the rule execution sequence
Define when a rule is part or not of a rule set
This program and the accompanying materials are made available under the Eclipse Public License V1.0, which accompanies this distribution. EPF Copyright.