Rule matching and HIT Policies
For the decision table we saw in Figure 4.23, a US-based customer, with a customer number of less than 10,000 would match with three rules (Silk Tray, Peanut Crunch, and the default Milk Chocolate). But how do we decide which rule we should use? To do that, we need to talk again about HIT Policies.
In our previous example, we set the HIT policy to First (in the top left corner of the decision table) as it was the easiest to understand. When we match with two rules, Silk Tray comes first, so it’s the one that is chosen.
That’s fine when we have only a couple of rules, but when we have hundreds of rules on a table, it becomes harder to see what is going on. Nudging a rule up or down the decision table could bring big changes to the behavior of the decision model. It also doesn’t leverage the full power of the rule engine. For these reasons, the HIT Policy of First is controversial and doesn’t form part of the OMG Decision...