Decision Model and Notation – Basics
Download as PPTX, PDF0 likes780 views
This document introduces Decision Model and Notation (DMN), a standard for modeling decisions in business processes and automatic decision-making systems. DMN allows modeling both human decision-making and requirements for automated decisions. It provides a standardized way to describe decision logic and policies using decision tables and FEEL (Friendly Enough Expression Language). DMN aims to simplify decision modeling and make it accessible to both business users and IT professionals. It has been adopted for applications like pricing, marketing automation, fraud detection, and more. Several tools exist for working with DMN models.
Decision Model and Notation – Basics
- 1. Decision Model and Notation Fresh look at the business logic modelling
- 2. Val Budkin • Interests: • Business Process Management, • Adaptive Case Management, • Decision Modeling, • Enterprise Architecture, • Agile • val.budkin@gmail.com • val.budkin
- 3. Purposes as understood by the purposer will be misunderstood by others Chisholm’s Third Law of Human Interaction
- 4. Price decisions Competitors data Demand by geography Stocks Local monopoly Vendor’s policy Purchase price Costs Marketing strategy Turnover
- 6. Standard bridge for decisions Model human decision making Model requirements for automatic decision making Implem ent automatic decision making
- 7. BPMN 2.0
- 10. BABOK v.3
- 12. BPMN 2.0 Business rule task
- 13. DMN simplifies
- 15. IT adds some geek stuff
- 16. Standartized XML
- 17. Decision policies • U – Unique (single) • A – Any (single) • P – Priority (single) • F – First (single) • C – Collect (multiple)
- 18. Aggregators for Collect policy • C+ SUM • C< MIN • C> MAX • C# COUNT
- 19. Simplified Friendly Enough Expression Language (S FEEL) < 42 (10. .19) 3,27 not(13) >= myvariable [date(“2016-07-29”)..date(“2016-07-30”)
- 20. FEEL • If Risk is “Low” or “Medium” and PTI<0.3 then “Approved” else “Declined”
- 21. Manage BP = change BP • Business process flow: Months and years. Changes are difficult from the side of business and IT. Development and organizational changes are necessary. Decision tables columns: Months. Changes are trivial from the side of business and can be difficult from the side of IT. Development is necessary. • Decision tables lines: Hours. Changes are trivial from the side of business and IT.
- 24. Decision (FEEL or DT) Business knowledge model Business knowledge DRD elements Direct data input
- 25. Industry cases • Pricing • Marketing automation • Fraud detection • Compliance • Reclamations • Human relations
- 26. Tools • Camunda Modeler • Signavio Decision Manager • FICO DMN Modeler • IBM Blueworks Live • Oracle Decision Service • Trisotech modeler
- 28. Some books to check
- 29. Questions?
Editor's Notes
- #4: If anything can go wrong, it will. When things are going well, something will go wrong. Purposes as understood by the purposer will be misunderstood by others a professor of English at Wisconsin State College in River Falls 1963
- #11: Стр. 271
- #18: Priority – отдельно задаётся приоритет output-ов
- #19: Examples? Page 83 of DMN 1.1
- #27: Images?