Real world decision tables can get very complex. The question is how to better manage the complexity of the enterprise decision model. One approach is the Decision Model View.

 

A View is like looking at the Decision Model through a filter, just as one may look at a complex database through the filter of a SQL View to focus on just the data that is of interest at a given time.

In fact, the Decision Model View is created by integrating  relational model principles into Decision Model structures. Using this approach Decision Models can be created, managed, analyzed and  implemented as Views of the underlying Enterprise Decision Model.

 

One approach would be to no longer manage Decision Models, but their Views; this is similar to the concept of never permitting application developers to directly address tables in RDBMS, but limit their access to Views only. This enables the Data Modeler to completely isolate and make changes to the schema without changing applications accessing the data. In a similar fashion we can generate multiple views of the same underlying rule sheet that show the rules in ways that make most sense to different business users. It also provides a way to control which users have access to which parts of a rule sheet by granting them access only to the appropriate View of the underlying rule sheet.

See attachment for examples