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.
Process Model versus PRPC Discovery Map            by Declan Chellar
Discovery Maps According to Pega• A Discovery Map is a flexible process mapping  tool that captures a projects high level ...
An Example Process Model
An Example Process ModelBased on a real process for making payments  against an account  using a Credit Card.
An Example Process Model This diagram reveals  the top-level of theprocess from start to all    possible ends.
An Example Process ModelSub-process can equate to Sub-process shapes  on a Discovery Map.
An Example Process Model But the nature of thebusiness trigger cannot    be shown on a    Discovery Map.
An Example Process ModelNor can end results beshown on a Discovery        Map.
An Example Process Model  And manual stepscannot be shown on a   Discovery Map.
An Example Process ModelBranch points cannot  be modelled on a   Discovery Map.
An Example Process ModelNot least when thosebranch points reflect  human choices.
An Example Process Model  As a result, overallprocess flow cannot be    modelled in a   Discovery Map.
An Example Process Model  Consider the amountof useful information in this top-level business     process model.
An Example Process Model  Then remove whatDiscovery Maps cannot  model at this level.
An Example Process ModelHowever, Discovery Maps representautomated process      flow.
An Example Process Model  Whereas many top-level processes are user         driven.                  What does            ...
An Example Process ModelSo the top level of the  process cannot be modelled as a single    Discovery Map                  ...
An Example Process Model   Each sub-process becomes a DM on its  own, losing the toplevel view inside PRPC.
An Example Process ModelLet’s take a look inside    one of the sub-       processes.
The “Take Payment” Sub-process
The “Take Payment” Sub-processLet’s convert this sub-    process into a   Discovery Map.
The “Take Payment” Sub-process  Any User/System   interactions arerepresented by green       shapes.
The “Take Payment” Sub-process  Any steps the System   carries out withoutinput from the User are         yellow.
The “Take Payment” Sub-processExcept for steps wherethe System integrates     with anothersystem, which are red.
The “Take Payment” Sub-process An understanding ofany manual steps is key to understanding the    business need.
The “Take Payment” Sub-processBut a Discovery Mapcannot show manual       steps.
The “Take Payment” Sub-process Nor can a DiscoveryMap show end results.
The “Take Payment” Sub-processOr branch points andtheir alternate paths.
The “Take Payment” Sub-processA Discovery Map doesknow the sequence of steps in the “Happy”         path.
The “Take Payment” Sub-process          By virture of the       sequence in which you       place the steps on the        ...
The “Take Payment” Sub-process But since a Discovery Map does not knowabout branch points or   alternate flows…
The “Take Payment” Sub-process        …it has no idea what       the correct sequence       of alternate steps is or      ...
The “Take Payment” Sub-process       So alternate steps are       lumped together after         a red divider on the      ...
The “Take Payment” Sub-processLet’s remind ourselves   of the wealth of  information in thevisual process model.
The “Take Payment” Sub-process          Versus what the        equivalent Discovery         Map can show us.              ...
The “Take Payment” Sub-process                Check whetherInput Payment                   Submit payment    Display payme...
The “Take Payment” Sub-process                                                                     PRPC can automatically ...
The “Take Payment” Sub-process      Start                              Our Discovery Map                                  ...
The “Take Payment” Sub-process      Start                                        Notice the absence of                    ...
The “Take Payment” Sub-process      Start                             And how the alternate                               ...
The “Take Payment” Sub-process     Start                                                                    The draft Flow...
The “Take Payment” Sub-process     Start                                                                        But the DM...
Recap                                                                      The Discovery Map is                           ...
Recap                                                                       But at best all it can                        ...
Recap        Instead of this.
The “Take Payment” Sub-process      Start                               A Discovery Map is                                ...
The “Take Payment” Sub-process      Start                                        But the best it can do is                ...
Recap     Start                                                                        Instead of this.CapturePayment    D...
Recap        When you go into your         DCO sessions armed             with this…
Recap     Start                                                                        …it takes only minutes             ...
Discovery Maps in Reality• A Discovery Map is NOT flexible because it  cannot model branch points or alternate  flows.• Be...
Recommendation• If you want to document business process  within PRPC:  1. Model the process using BPMN before your Pega  ...
WWW.CHELLAR.COM/BLOG
Upcoming SlideShare
Loading in …5
×

Process Model versus PRPC Discovery Map

3,164 views

Published on

A brief comparison of business process models and Pegasystems PRPC Discovery Maps.

Published in: Economy & Finance, Business
  • Be the first to comment

Process Model versus PRPC Discovery Map

  1. 1. Process Model versus PRPC Discovery Map by Declan Chellar
  2. 2. Discovery Maps According to Pega• A Discovery Map is a flexible process mapping tool that captures a projects high level processing steps in business terms.• Steps are color-coded to indicate a flow shape: • Sub Process - Blue • Human Based Step - Green • Automated Step - Yellow • Integration - Red(Pega Developers Network article PRKB-26125)
  3. 3. An Example Process Model
  4. 4. An Example Process ModelBased on a real process for making payments against an account using a Credit Card.
  5. 5. An Example Process Model This diagram reveals the top-level of theprocess from start to all possible ends.
  6. 6. An Example Process ModelSub-process can equate to Sub-process shapes on a Discovery Map.
  7. 7. An Example Process Model But the nature of thebusiness trigger cannot be shown on a Discovery Map.
  8. 8. An Example Process ModelNor can end results beshown on a Discovery Map.
  9. 9. An Example Process Model And manual stepscannot be shown on a Discovery Map.
  10. 10. An Example Process ModelBranch points cannot be modelled on a Discovery Map.
  11. 11. An Example Process ModelNot least when thosebranch points reflect human choices.
  12. 12. An Example Process Model As a result, overallprocess flow cannot be modelled in a Discovery Map.
  13. 13. An Example Process Model Consider the amountof useful information in this top-level business process model.
  14. 14. An Example Process Model Then remove whatDiscovery Maps cannot model at this level.
  15. 15. An Example Process ModelHowever, Discovery Maps representautomated process flow.
  16. 16. An Example Process Model Whereas many top-level processes are user driven. What does Customer want me to do next?
  17. 17. An Example Process ModelSo the top level of the process cannot be modelled as a single Discovery Map What does Customer want me to do next?
  18. 18. An Example Process Model Each sub-process becomes a DM on its own, losing the toplevel view inside PRPC.
  19. 19. An Example Process ModelLet’s take a look inside one of the sub- processes.
  20. 20. The “Take Payment” Sub-process
  21. 21. The “Take Payment” Sub-processLet’s convert this sub- process into a Discovery Map.
  22. 22. The “Take Payment” Sub-process Any User/System interactions arerepresented by green shapes.
  23. 23. The “Take Payment” Sub-process Any steps the System carries out withoutinput from the User are yellow.
  24. 24. The “Take Payment” Sub-processExcept for steps wherethe System integrates with anothersystem, which are red.
  25. 25. The “Take Payment” Sub-process An understanding ofany manual steps is key to understanding the business need.
  26. 26. The “Take Payment” Sub-processBut a Discovery Mapcannot show manual steps.
  27. 27. The “Take Payment” Sub-process Nor can a DiscoveryMap show end results.
  28. 28. The “Take Payment” Sub-processOr branch points andtheir alternate paths.
  29. 29. The “Take Payment” Sub-processA Discovery Map doesknow the sequence of steps in the “Happy” path.
  30. 30. The “Take Payment” Sub-process By virture of the sequence in which you place the steps on the Discovery Map itself. Check whetherInput Payment Submit payment Display payment duplicate Details request to Bank confirmation payment
  31. 31. The “Take Payment” Sub-process But since a Discovery Map does not knowabout branch points or alternate flows…
  32. 32. The “Take Payment” Sub-process …it has no idea what the correct sequence of alternate steps is or where they fit. Check whetherInput Payment Submit payment Display payment duplicate Details request to Bank confirmation payment Save payment Display error details message
  33. 33. The “Take Payment” Sub-process So alternate steps are lumped together after a red divider on the Discovery Map. Check whetherInput Payment Submit payment Display payment Save payment Display error duplicate Details request to Bank confirmation details message payment
  34. 34. The “Take Payment” Sub-processLet’s remind ourselves of the wealth of information in thevisual process model.
  35. 35. The “Take Payment” Sub-process Versus what the equivalent Discovery Map can show us. Check whetherInput Payment Submit payment Display payment Save payment Display error duplicate Details request to Bank confirmation details message payment
  36. 36. The “Take Payment” Sub-process Check whetherInput Payment Submit payment Display payment Save payment Display error duplicate Details request to Bank confirmation details message payment “A Discovery Map is a flexible process mapping tool that captures a projects high level processing steps in business terms.” (Pega Developers Network)
  37. 37. The “Take Payment” Sub-process PRPC can automatically generate a Flow Rule from a Discovery Map. Check whetherInput Payment Submit payment Display payment Save payment Display error duplicate Details request to Bank confirmation details message payment
  38. 38. The “Take Payment” Sub-process Start Our Discovery Map would generate a Flow Rule like this. CapturePayment Details Display Error Check for Message Duplicate Payment SaveSubmit Payment PaymentRequest to Bank Details Display Confirmation
  39. 39. The “Take Payment” Sub-process Start Notice the absence of branch points. CapturePayment Details Display Error Check for Message Duplicate Payment SaveSubmit Payment PaymentRequest to Bank Details Display Confirmation
  40. 40. The “Take Payment” Sub-process Start And how the alternate flows are poorly represented. CapturePayment Details Display Error Check for Message Duplicate Payment SaveSubmit Payment PaymentRequest to Bank Details Display Confirmation
  41. 41. The “Take Payment” Sub-process Start The draft Flow Rule we really need would beCapturePayment Details more like this. Duplicate Duplicate Payment Not Duplicate Immediate Immediate Submit Payment Payment Request to Bank Future Submit Not Successful Display Error Successful Message Save Payment Successful Details Display Confirmation
  42. 42. The “Take Payment” Sub-process Start But the DM cannot generate the actualCapturePayment draft Flow Rule Details needed. Duplicate Duplicate Payment Not Duplicate Immediate Immediate Submit Payment Payment Request to Bank Future Submit Not Successful Display Error Successful Message Save Payment Successful Details Display Confirmation
  43. 43. Recap The Discovery Map is supposed to model the business process. Check whetherInput Payment Submit payment Display payment Save payment Display error duplicate Details request to Bank confirmation details message payment
  44. 44. Recap But at best all it can model is this. Check whetherInput Payment Submit payment Display payment Save payment Display error duplicate Details request to Bank confirmation details message payment
  45. 45. Recap Instead of this.
  46. 46. The “Take Payment” Sub-process Start A Discovery Map is supposed to generate a Flow Rule. CapturePayment Details Display Error Check for Message Duplicate Payment SaveSubmit Payment PaymentRequest to Bank Details Display Confirmation
  47. 47. The “Take Payment” Sub-process Start But the best it can do is this. CapturePayment Details Display Error Check for Message Duplicate Payment SaveSubmit Payment PaymentRequest to Bank Details Display Confirmation
  48. 48. Recap Start Instead of this.CapturePayment Details Duplicate Duplicate Payment Not Duplicate Immediate Immediate Submit Payment Payment Request to Bank Future Submit Not Successful Display Error Successful Message Save Payment Successful Details Display Confirmation
  49. 49. Recap When you go into your DCO sessions armed with this…
  50. 50. Recap Start …it takes only minutes to produce this FlowCapturePayment Details Rule manually. Duplicate Duplicate Payment Not Duplicate Immediate Immediate Submit Payment Payment Request to Bank Future Submit Not Successful Display Error Successful Message Save Payment Successful Details Display Confirmation
  51. 51. Discovery Maps in Reality• A Discovery Map is NOT flexible because it cannot model branch points or alternate flows.• Because DM shapes indicate Flow Rule shapes, a DM does NOT model in business terms, but in PRPC implementation terms.• A DM can only model what is to be implemented in PRPC, so does NOT model the entire business process.
  52. 52. Recommendation• If you want to document business process within PRPC: 1. Model the process using BPMN before your Pega project starts 2. Build your Flow Rules manually based on the process models (it only takes minutes if your models are robust) 3. Attach the process model to the relevant Flow Rule (that is DCO too, you know)
  53. 53. WWW.CHELLAR.COM/BLOG

×