Combining DMN and the Knowledge Base Paradigm for Flexible Decision Enactment

Ingmar Dasseville, Laurent Janssens,

Gerda Janssens, Jan Vanthienen,Marc Denecker

http://krr.bitbucket.org/autoconfig

DMN

Decision Requirements Diagram

Input

Output

U	At Risk Model	Convertible	Price	Potential Theft Rating
	Boolean	Boolean	Currency ($)	{High, Moderate,Low}
1	True	-	-	High
2	False	True	-	High
3	False	False	>45K	High
4	False	False	[20K...45K]	Moderate
5	False	False	<20K	Low

But wait... There's more!

Traditional Execution

Information doesn't
do anything. 

We do things with
information.

The Knowledge Base Paradigm

A Knowledge Base System as a multi-directional execution system for DMN

Knowledge Base System

based on

First Order Logic

(+extensions)

in short

FO(·)

Specifying Knowledge

1. What are you talking about?

2. What do you know about it?

vocabulary V {
    type Price constructed from 
            { lessthan20k
            , between20And45k
            , over45k}

    type TheftRating constructed from 
                { high
                , moderate
                , low}
    
    Convertible
    CarPrice : Price
    HighTheftProbabibilityAuto
    PotentialTheftRating : TheftRating
}

1. What are you talking about?

2. What do you know about it?

U	At Risk Model	Convertible	Price	Potential Theft Rating
	Boolean	Boolean	Currency ($)	{High, Moderate,Low}
1	True	-	-	High
2	False	True	-	High
3	False	False	>45K	High
4	False	False	[20K...45K]	Moderate
5	False	False	<20K	Low

PotentialTheftRating = high <- HighTheftProbabibilityAuto.
PotentialTheftRating = high <- Convertible.
PotentialTheftRating = high <- CarPrice = over45k. 
PotentialTheftRating = moderate <- CarPrice = between20And45k 
                                    & PotentialTheftRating ~= high.
PotentialTheftRating = low <- CarPrice = lessthan20k 
                              & PotentialTheftRating ~= high 
                              & PotentialTheftRating ~= moderate.