Decision Model and Notation, or DMN, is a novel way to model business decisions. DMN allows the capture and modeling of business decisions in a way that is easy to understand for business people and subject matter experts. It is a combination of the following:
- Decision Requirement Diagram – DRD
- Decision Table
- Boxed Expressions
- Friendly Enough Expression Language (FEEL)
Decision Requirement Diagram (DRD)
This is a graphical model that allows modeling dependencies between input data, decision, business knowledge and knowledge sources.
In DRD, the arrows show the dependencies between different nodes in the model. To put it in a simple way, you can read it as if the output result of some nodes will be passed as the input of the other nodes.
In the table below, all of the elements on a DRD model are illustrated:
In Decision Model and Notation, the Decision Table is a tabular form that models rules based on conditions and actions which are also called inputs and outputs. Decision Table is the default type of modeling business rules in DMN. But if your tools support other ways to model business rules then you can freely use them alongside decision table.
Learn more – How to use Decision Table in modeling business rules.
Decision Model and Notation (DMN) is a simple two column table and an effective way to model business formulas, calculations, values and expressions. Then you can share these across multiple decisions and logic.
Boxed expressions simply allows modeling: constant, values, invocation, formulas, etc. Boxed expressions allows you to put together building blocks of logic (i.e. decision table, natural language, flow, etc.) and enables you to reuse these over and over again.
Friendly Enough Expression Language
In Decision Model and Notation, FEEL is an expression language for business people. FEEL defines a syntax for expressing conditions, actions and formulae. FEEL is like using Excel formulas in that it allows you formulate your thinking about a domain in a context. FEEL is designed for ease of use by business people and subject matter experts.
There are benefits to using Decision Model and Notation over the traditional business rules approach. In the business rules approach, very soon you start thinking about the logical implementation of the actual rules. But the DMN approach provides a higher-level abstracted layer that allows you to see the big picture first rather than diving deep into implementation and potentially losing the context and oversight of the solution.
This change of approach:
- Allows scaling of business rules in a more manageable, reusable visual approach across applications and processes.
- Allows better communication between the business, domain experts and IT by enabling a more productive involvement of business people and subject matter experts.
- Allows clearly defined decision boundaries and exposes the decision as a service with a click!
If your tool supports simulation and execution, error checking at design time and runtime with debugging capability, then you will not overlook anything by using a business rules approach, but you will also have a better way to reuse and scale your business rules in a systematic way.
- Import DMN models – XML 1.1
- Boxed Expressions – DMN
- Decision Model and Notation – DMN
- Reusable DRD or Sub DRD in Decision Model and Notation (DMN)
- Decision model and Notation – Policy Example
- Reuse Business Decision
- Flow Orchestration Simplified – Using Decisions
- Workflow Engine or Business Rule Engine
- Decision as a Service
- Modeling Business Logic i.e. Business Processes, Rules, Decisions, Data, Workflow…