Download as ODP, PPTX
Uploaded byGeoffrey De Smet
2011-03-29 London - Why do I need the guvnor BRMS?
The document discusses the benefits of using the Guvnor BRMS (Business Rules Management System) for businesses where decisions require domain expertise or rules change frequently. It provides examples of use cases like determining mortgage approvals that rely on complex financial logic understood best by domain experts. The Guvnor allows non-technical domain experts to author and test rules visually, while also providing an auditable record of rule changes over time to understand past decisions.
More Related Content
Similar to 2011-03-29 London - Why do I need the guvnor BRMS?
2011-03-29 London - Why do I need the guvnor BRMS?
- 1. Geoffrey De SmetWhy do I need the Guvnor BRMS?
- 2. Guvnor agenda Usecases
- 3. My business requiresdomain expertise
- 4. My business ruleschange often
- 5.
- 6.
- 7. Use cases Ihave hammer, so every problem is a nail?
- 8. The myth BecauseDrools can fulfil business rules
- 9. Drools is Turing complete we should write the entire business layer in Drools? No!
- 10. Not imperative likeJava, Scala, Groovy, ...
- 11. Declarative like RegEx,SQL, JPA-QL, … Easier to read, better at scaling Extract business decisions in Drools that either: Require schooled domain expertise
- 12.
- 13. Use cases Financialdecisions Mortgages acceptance and interest calculation
- 14. Insurances acceptance andfee calculation Price calculations Phone/Telecom bills Diagnostics Possible diseases based on symptoms Complex validation Car parts selection Not a good use case: an XML parser Use Java code for that
- 15.
- 16. Developers don't likedata input from spreadsheets Before App 1.0: Mortgages rules in a spreadsheet Which version/copy of the spreadsheet file?
- 17. Which field hasthe result our application need? Version 1 Version 2
- 18. Mortgage experts likethe flexibility of spreadsheets Since App 1.0: Mortgages rules in source code Changing business rules not flexible enough Business rules are hard coded in Java Invalid: must be a number Flooded with new improvement requests: when income below 500
- 19. when income below1000 and age above 50
- 20. when income below1% of mortgage amount
- 21. Data model inGuvnor Import POJO jar
- 22. or Designthe model in Guvnor:
- 23. Mortgage expertslike the flexibility of Guvnor App 2.0: Mortgage rules in Guvnor repository Flexible like spreadsheet But fields clearly defined No spreadsheet versions/copies Auditable
- 24. My business requiresdomain expertise Only mortgage managers understand mortgage rules
- 25. Schooled domain expertiseAre we, the developers, domain experts? Yes, we've been working in this company for year(s). Do we have university's degree in economics? No
- 26. participated in mortgagesconferences/courses? No
- 27. years of mortgagecustomer experience? No Do we have a clue when the mortgage rules need to change? No
- 28. Are we, thedevelopers, domain experts? No Mortgage manager is the domain expert
- 29. Domain experts cannot read/write Java source code Communication problem Domain expert can not read it: for (Mortgage m : mortgages ) { for (Applicant a : m.getApplicants()) { if (a.getAge() > 70 ) { boolean existsGuarantor = false ; for (Guarantor g : m.getGuarantors() { if (g.getAge < 60 ) { existsGuarantor = true ; } } // Will they spot the bug in this code? if (existsGuarantor) { m.setApproved( false ); } } } } DRL scales better than this Java code
- 30. Domain experts canread/write DRL with Guided Rule Editor Change
- 31. Guided Rule Editordemo video Demo video
- 32. Domain experts canread/write DSL even better DSL is even easier to read/write Developers create the building blocks
- 33. Domain experts makethe building Source: wikipedia
- 34. My business ruleschange often This mortgage rule change must be released by noon
- 35.
- 36. Business rule changeNot a data change Requires test and release lifecycle
- 37. Logic changes Nota software change Delivered in hours, not days
- 38. Self-service by mortgagemanager
- 39. Testing before releasingDomain experts need to unit test too Example: mortgage of Erik (75) must be disapproved
- 40. Releasing Release asnapshot of the rules package
- 41. Available at URL:http://127.0.0.1:8888/org.drools.guvnor.Guvnor/package/presentationmortgages/mortgagesDeployment
- 42.
- 43. Auditable and reproducibleWhy was that mortgage approved last year?
- 44. Auditing View oldrevisions of rules
- 45.
- 46. Modules: reuse rulesModule contains assets (rules) Packages will be renamed to modules Module can depend on other modules Reuse of assets (rules) from other modules
- 47. Dependency graph (likeMaven/OSGi but simplified) Mortgage rules Car loan rules General loan rules Customer rules 2.0 1.1 1.1 2.1
- 48.
- 49.
- 50.
- 51. Immutable (all dependentmodules are released)
- 52.
- 53. Summary Use Droolsand Guvnor
- 54. when your businessdecisions either Require domain expertise
- 55.
- 56. Q & AQuestions?
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64. Mailing lists (foruminterface through nabble.com)
- 65.