Decision Model and Notation

from Wikipedia, the free encyclopedia

Decision Model and Notation (DMN for short) is an official notation standard for decision rules in business process management that was defined by the Object Management Group (OMG). This standard is used to describe and model repeatable decisions in organizations. DMN enables users from a wide variety of departments to collaborate effectively on decision modeling.

development

The first version of the standard appeared in September 2015. The Decision Model and Notation 1.1 version has been available since June 2016.

object

DMN serves to document decisions of non-situational and deliberately chosen alternative courses of action based on known pre-selectively determined and non-influenceable evaluation criteria. Decisions on opinion-forming, on interpersonal relationships, spontaneously made as well as strategic, higher-level decisions, which would still allow several alternative courses of action in their operationalization, cannot be described by the DMN, or only to a very limited extent.

The DMN facilitates communication between departments. Starting with the business analyst , who documents the decision requirements, through the technical developer, who automates the decision rules, to the application and monitoring of the decision rules by the specialist department.

aims

The aim of the DMN is to detach the decisions from the business processes. For this purpose, decision-making processes are represented graphically and decision-making rules are established. This makes recurring decisions in the day-to-day business of a company transparent. If the basis for decision-making changes, only these need to be adjusted, but the business processes that are dependent on them remain unchanged.

application

DMN can be used for different purposes. One possibility is to analyze the business processes in detail by questioning them and splitting the decisions into partial decisions. Another possibility is the automation of decisions with the help of decision tables and the expression language FEEL (Friendly Enough Expression Language).

advantages

  • Rapid adaptation of business rules to changing requirements without changing business processes
  • Automation of the decision logic
  • Possibility of seamless integration in BPMN (Business Process Model and Notation)

elements

Decision Model and Notation is made up of the Decision Requirements Diagram (DRD for short, German: Decision Diagram), the graphic representation of the decision rule, and the Decision Table (German: Decision Table), which is used to read the appropriate decision for each input supplied. The expression language FEEL (Friendly Enough Expression Language) is used as the language. By using this language, decisions can be automated.

Connection to BPMN

DMN (Decision Model and Notation) is a stand-alone notation, but the design enables a simple link with BPMN (Business Process Model and Notation). Processes can be viewed separately from decisions, with the advantage that the process is streamlined and the decision is comprehensible. To achieve this, you can proceed as follows:

  • Identify decisions in the business process
  • Consider the decision model separately from the process
  • Implement reporting and update processes in order to be able to carry out continuous optimizations

literature

  • Tom Debevoise and James Taylor: Process and Decision Modeling in BPMN / DMN. January 1, 2016, ISBN 978-1519542960

Web links

Individual evidence

  1. ↑ Object Management Group: Decision Model and Notation (DMN) V1.1. June 1, 2016
  2. ↑ Björn Richerzhagen: Automate decisions. In: Blog. MINAUTICS GmbH, March 12, 2020, accessed on April 17, 2020 .
  3. ↑ Sven Dobke (MID GmbH): What is DMN (Decision Model and Notation)? In a nutshell! Blog post from September 28, 2016
  4. ↑ Tom Debevoise, James Taylor: Process and Decision Modeling in BPMN / DMN. January 1, 2016 (pp. 9/10)
  5. ↑ Marcus Winteroll: Analyze and model decisions with DMN. Technical article in Business Technology, February 2015 edition. Oose Innovative Informatik
  6. ↑ Michael Jacob (MID GmbH): DMN, ACM, BPM, BRM, CMMN - all right? Blog post from September 16, 2016 .
  7. ↑ Marcus Winteroll: Analyze and model decisions with DMN. Technical article in Business Technology, February 2015 edition. Oose Innovative Informatik
  8. ^ Johannes Stöhr (Signavio GmbH): Methodical approach with DMN. November 2015 white paper
  9. ↑ Bernd Rücker: Decision Model and Notation: Between Business and IT. Technical article in Business Technology, February 2016 edition. Camunda
  10. ↑ Rainer Feldbrügge: Modeling business rules. Blog post from December 16, 2014. Dr. Rainer Feldbrügge, HR and organizational consultancy
  11. ↑ Marcus Winteroll: Analyze and model decisions with DMN. Technical article in Business Technology, February 2015 edition. Oose Innovative Informatik