Producing characteristic Rulesheet patterns

Because Corticon Studio is a visual environment, patterns often appear in the Rulesheet that provide insight into the decision logic. Once a rule writer recognizes and understands what these patterns mean, he or she can often accelerate rule modeling in the Rulesheet. The Compression Tool is designed to reproduce Rulesheet patterns in some common cases.

For example, take the following rule statement:

Applying some of the techniques from this manual, we might implement rule 1 as:

Figure 238. Implementing the 747 Rule

Now, letting the Completeness Checker populate the missing columns:

Figure 239. Remaining Columns Produced by the Completeness Checker

To remind you of the underlying Cross Product used by the Completeness Checker, we will Expand the Rulesheet momentarily and examine the sub-rules present:

Figure 240. Underlying Sub-Rules Produced by the Completeness Checker

A total of 26 new columns (counting both rules and sub-rules) have been created – exactly what we expect and what the Completeness Check message window states.

Note: Three Conditions each with three members in their Values sets yields a Cross Product of 27 combinations (3*3*3 or 3 cubed). Subtracting the combination already present in column 1, we expect 26 new columns to be added.

Now, Compress

the Rulesheet and fill in the Actions for the new columns as shown:

Figure 241. Missing Rules with Actions Assigned

Because the added rules are non-overlapping, we can be sure they won't introduce any ambiguities into the Rulesheet. To prove this, select the Conflict Checker

Figure 242. Proof that no New Conflicts have been Introduced by the Completeness Check

This pattern tells us that the only case where the aircraft type is a 747 is when max cargo volume is greater than 300 AND max cargo weight is greater than 200,000 AND tail number is N123UA. This rule is expressed in column 1. In all other cases, specifically where max cargo volume is 300 or less OR max cargo weight is 200,000 or less OR tail number is something other than N123UA will the aircraft type be a DC-10 (or any of the values are null). These rules are expressed in columns 2, 3 and 4, respectively.

The characteristic diagonal line of Condition values in columns 2-4, surrounded by dashes indicates a classic OR relationship between the 3 Conditions in these columns. The Compression algorithm was designed to produce this characteristic pattern whenever the underlying rule logic is present. It helps the rule writer to better see how the rules relate to each other.