Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Upcoming SlideShare
Loading in …5
×

# Decision Model and Notation – Basics

565 views

Published on

Presentation for Kharkiv BAConf 2016.

http://baconf.dev-pro.net

Published in: Software
• Full Name
Comment goes here.

Are you sure you want to Yes No
Your message goes here
• Login to see the comments

• Be the first to like this

### Decision Model and Notation – Basics

1. 1. Decision Model and Notation Fresh look at the business logic modelling
2. 2. Val Budkin • Interests: • Business Process Management, • Adaptive Case Management, • Decision Modeling, • Enterprise Architecture, • Agile • val.budkin@gmail.com • val.budkin
3. 3. Purposes as understood by the purposer will be misunderstood by others Chisholm’s Third Law of Human Interaction
4. 4. Price decisions Competitors data Demand by geography Stocks Local monopoly Vendor’s policy Purchase price Costs Marketing strategy Turnover
5. 5. Ugly solution
6. 6. Standard bridge for decisions Model human decision making Model requirements for automatic decision making Implem ent automatic decision making
7. 7. BPMN 2.0
8. 8. Customer order
9. 9. Inside the box
10. 10. BABOK v.3
11. 11. BPMN 2.0 Business rule task
12. 12. DMN simplifies
13. 13. Business like tables
14. 14. IT adds some geek stuff
15. 15. Standartized XML
16. 16. Decision policies • U – Unique (single) • A – Any (single) • P – Priority (single) • F – First (single) • C – Collect (multiple)
17. 17. Aggregators for Collect policy • C+ SUM • C< MIN • C> MAX • C# COUNT
18. 18. Simplified Friendly Enough Expression Language (S FEEL) < 42 (10. .19) 3,27 not(13) >= myvariable [date(“2016-07-29”)..date(“2016-07-30”)
19. 19. FEEL • If Risk is “Low” or “Medium” and PTI<0.3 then “Approved” else “Declined”
20. 20. 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.
21. 21. Decision Requirement Diagram
22. 22. Decision (FEEL or DT) Business knowledge model Business knowledge DRD elements Direct data input
23. 23. Industry cases • Pricing • Marketing automation • Fraud detection • Compliance • Reclamations • Human relations
24. 24. Tools • Camunda Modeler • Signavio Decision Manager • FICO DMN Modeler • IBM Blueworks Live • Oracle Decision Service • Trisotech modeler
25. 25. Camunda Modeler https://camunda.org/bpmn/tool/
26. 26. Some books to check
27. 27. Questions?