John Graham – TD Manager - SOA Edson Tirelli – Drools Fusion Lead Kris Verlaenen – jBPM Lead May 4 th , 2011   EVENT DRIVE...
Agility & Reaction <ul>http://everythingisobvious.com/ </ul><ul><li>Ability of models to predict, rather than describe or ...
Descriptive or normative? How about agile?
Challenge: understand and react in real time </li></ul>
Example Software Process <ul>http://www.eclipse.org/projects/project_summary.php?projectid=technology.epf </ul>
Releasing software entails... <ul>Rules <li>For scope changes
For commits
For code reviews
End game policies </li></ul><ul>Events <li>Bug state transitions
Instability clustering
Feature completion
Builds status
Test status
Staff availability
Infrastructure status </li></ul><ul>Processes <li>Iteration steps
Milestone closure
Change management </li></ul>
Suggestion Use API and reporting mechanisms available with many/most software development tools and infrastructure  combin...
Ready for the future? Traditional BPM systems have problems with change, complexity, flexibility, data-intensive applicati...
Unstructured, non-lineair or flexible processes
Event-driven BPM (edBPM) </li></ul>
 
What is flexibility? “ The quality of being adaptable or variable”
Flexibility = Variability + Change
Exceptional Control Flow 90% 5% 3% 2%
Exceptional Control Flow 90% Rule1 When ... Then ... Rule2 When ... Then ... Rule3 When ... Then ... 5% 3% 2%
Processes + Rules + Events
Model Deploy Execute Monitor Analyze Life Cycle Mining Analysis Optimization Simulation Testing Design Monitoring Reportin...
Upcoming SlideShare
Loading in …5
×

Event-driven BPM the JBoss way

3,249 views
3,103 views

Published on

jBPM5 presentation at JBossWorld

0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,249
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
131
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Event-driven BPM the JBoss way

  1. 2. John Graham – TD Manager - SOA Edson Tirelli – Drools Fusion Lead Kris Verlaenen – jBPM Lead May 4 th , 2011 EVENT DRIVEN BPM THE JBOSS WAY
  2. 3. Agility & Reaction <ul>http://everythingisobvious.com/ </ul><ul><li>Ability of models to predict, rather than describe or explain
  3. 4. Descriptive or normative? How about agile?
  4. 5. Challenge: understand and react in real time </li></ul>
  5. 6. Example Software Process <ul>http://www.eclipse.org/projects/project_summary.php?projectid=technology.epf </ul>
  6. 7. Releasing software entails... <ul>Rules <li>For scope changes
  7. 8. For commits
  8. 9. For code reviews
  9. 10. End game policies </li></ul><ul>Events <li>Bug state transitions
  10. 11. Instability clustering
  11. 12. Feature completion
  12. 13. Builds status
  13. 14. Test status
  14. 15. Staff availability
  15. 16. Infrastructure status </li></ul><ul>Processes <li>Iteration steps
  16. 17. Milestone closure
  17. 18. Change management </li></ul>
  18. 19. Suggestion Use API and reporting mechanisms available with many/most software development tools and infrastructure combined with jBPM 5 and Drools to gain real time understanding and agility.
  19. 20. Ready for the future? Traditional BPM systems have problems with change, complexity, flexibility, data-intensive applications, etc. <ul><li>Adaptive Case Management (ACM)
  20. 21. Unstructured, non-lineair or flexible processes
  21. 22. Event-driven BPM (edBPM) </li></ul>
  22. 24. What is flexibility? “ The quality of being adaptable or variable”
  23. 25. Flexibility = Variability + Change
  24. 26. Exceptional Control Flow 90% 5% 3% 2%
  25. 27. Exceptional Control Flow 90% Rule1 When ... Then ... Rule2 When ... Then ... Rule3 When ... Then ... 5% 3% 2%
  26. 28. Processes + Rules + Events
  27. 29. Model Deploy Execute Monitor Analyze Life Cycle Mining Analysis Optimization Simulation Testing Design Monitoring Reporting Execution Integration Deployment Management Audit Human Interaction Collaboration
  28. 30. Vision A knowledge-oriented platform for developers and business users
  29. 31. Logistics Company – Business Overview <ul><li>Time specific deliveries of critical freight
  30. 32. Exclusive use of non-stop door-to-door services
  31. 33. Blended surface and air services to minimize cost and transit time
  32. 34. Extra care in handling and specially equipped vehicles </li><ul><li>Temperature control, Secured Services, Hazardous Material, Constant Surveilance </li></ul></ul>Source: E. Tirelli & A. Mollenkopf - ORF2009
  33. 35. Logistics Company – goals <ul><li>End-to-end management of shipments </li><ul><li>Dispatch eligibility, fleet scoring and shipment assignment
  34. 36. Route calculation and monitoring
  35. 37. Incident management </li></ul><li>ETA management
  36. 38. Capacity tracking </li></ul>Source: E. Tirelli & A. Mollenkopf - ORF2009
  37. 39. Logistic Company - Solution Source: E. Tirelli & A. Mollenkopf - ORF2009 New Facts Reasoning Inferred Facts K n o w l e d g e B a s e s CEP [ Temporal Reasoning ] Knowledge Based Reasoning Spatial Reasoning Vehicle Event Stream Aircraft Event Stream Traffic Flow Event Stream Traffic Incident Event Stream Weather Event Stream Shipment Event Stream Stop Event Stream
  38. 40. Combining Processes, Rules and Events <ul><li>Integration </li><ul><li>From loose coupling
  39. 41. To advanced integration </li></ul><li>Unification </li><ul><li>Processes and (event) rules are different types of business knowledge assets
  40. 42. Tooling (IDE, repository, management) </li></ul></ul>
  41. 43. Decision Service <ul><li>Different life cycle (agility)
  42. 44. Larger scope (reusable)
  43. 45. Higher-level
  44. 46. Loosely-coupled </li></ul>
  45. 47. <ul><li>RuleSet: Evaluating a set of rules in your process (= local decision service)
  46. 48. Process Rules : Data-driven constraints
  47. 49. Triggers : Rules / events start / signal process
  48. 50. Assignment rules
  49. 51. Describing exceptional situations using rules
  50. 52. Modularizing concerns using rules
  51. 53. Using rules to dynamically alter the behavior of the process </li></ul>Rules and Process Integration
  52. 54. Example: Clinical DSS
  53. 55. Example: Build Management Source: Hudson Execution and Scheduling Architecture
  54. 56. Example: Build Management Source: Hudson Execution and Scheduling Architecture
  55. 57. Continuum Data-driven Lifetime Stability Granularity Change Dynamic Complexity Declarative User-focused
  56. 58. JBoss Projects
  57. 59. jBPM5: What, where? <ul><li>jBPM home page
  58. 60. Source http://github.com/droolsjbpm/jbpm
  59. 61. Hudson http://hudson.jboss.org/hudson/job/jBPM
  60. 62. Blog http://kverlaen.blogspot.com/
  61. 63. #jbpm on irc.codehaus.org
  62. 64. [email_address]
  63. 65. jBPM user forum </li></ul>
  64. 66. Drools: What, where? <ul><li>Drools home page
  65. 67. Source http://github.com/droolsjbpm/jbpm
  66. 68. Hudson http://hudson.jboss.org/hudson/job/drools
  67. 69. Blog http://blog.athico.com/
  68. 70. #drools on irc.codehaus.org
  69. 71. [email_address] </li></ul>

×