• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
BPMN in Pegasystems PRPC Flow Rules
 

BPMN in Pegasystems PRPC Flow Rules

on

  • 5,319 views

There is a perception that Pegasystems PRPC can be used to create BPMN-compliant process models. However, I consider this perception to be incorrect. ...

There is a perception that Pegasystems PRPC can be used to create BPMN-compliant process models. However, I consider this perception to be incorrect.

This slide show takes you through my reasoning

Statistics

Views

Total Views
5,319
Views on SlideShare
4,441
Embed Views
878

Actions

Likes
1
Downloads
75
Comments
2

4 Embeds 878

http://www.chellar.com 872
http://www.slashdocs.com 4
http://131.253.14.98 1
http://webcache.googleusercontent.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

12 of 2 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Thisisanexample of a sub-processmodelledusing BPMN.This sub-process “ReviewLeaveRequest” ispart of a higher-levelworkflowforhandlingleaverequests.Thatworkflowconsists of three sub-processes: RequestLeave, ReviewLeaveRequest and ReviewRejectedLeaveRequest.Thelevel of modellingonthisdiagramcallsoutallthelogicalstepsthatneedtotake place in ordertoreview a leaverequest.Detailssuch as data requirements and business rules do notappearonthediagram, althoughstepswherebusiness rules are invoked are indicated.
  • Thisslide shows howtheinitialdraft of the PRPC Flow Rule might look usingPega’sversion of BPMN shapes.
  • All Pega doesis re-paintitsFlow Rule shapesto look like BPMN shapes.Thisisnotthesame as BPMN-compliance.
  • Thisisnotthesame as BPMN-compliance.
  • Thisslide introducestheargumentthatPega´sversion of BPMN isactuallynot BPMN at all.
  • Thisslidelistslimitationsto Pega BPMN which are allowed in BPMN.
  • Thisslidelistslimitationsto Pega BPMN which are allowed in BPMN.
  • Thisslidelistslimitationsto Pega BPMN which are allowed in BPMN.

BPMN in Pegasystems PRPC Flow Rules BPMN in Pegasystems PRPC Flow Rules Presentation Transcript

  • BPMN in Pegasystems PRPC Flow Rules by Declan Chellar @AnalysisFu
  • Pega BPMN: the perceptionThere is a perception that PegasystemsPRPC can be used to create BPMN-compliant process models.* * This slide deck is relevant up to PRPC version 6.2.
  • What the Pega Developers Network says “BPMN stencil — By selecting a BPMN Visio stencil, you can create flow diagrams that closely match the appearance and notation used in Business Process Management Notation (BPMN) diagrams.”** http://pdn.pega.com/Devnet/Announcements/Announce61/process.asp
  • What the Pega Developers Network says “BPMN stencil — By selecting a BPMN Visio stencil, you can create flow diagrams that closely match the appearance and notation used in Business Process Management Notation (BPMN) diagrams.”* Notice the words “closely match”. This is not the same as saying that Pega’s BPMN stencil is BPMN-compliant.* http://pdn.pega.com/Devnet/Announcements/Announce61/process.asp
  • What the Pega Developers Network says “BPMN stencil — By selecting a BPMN Visio stencil, you can create flow diagrams that closely match the appearance and notation used in Business Process Management NotationCAVEAT: diagrams.”* (BPMN) Pega does not claim that “Pega BPMN” Flow Rules are BPMN-complaint. Notice the words “closely match”. This is not the same as saying that Pega’s BPMN stencil is BPMN-compliant.* http://pdn.pega.com/Devnet/Announcements/Announce61/process.asp
  • A sub-process expressed using BPMN• The next slide contains an example of a sub-process modelled using BPMN.• This sub-process “Review Leave Request” is part of a higher- level workflow for handling leave requests.• That workflow consists of three sub-processes: • Request Leave • Review Leave Request • Review Rejected Leave Request.• The level of modelling on this diagram calls out all the logical steps that need to take place in order to review a leave request.• Details such as data requirements and business rules do not appear on the diagram, although steps where business rules get invoked are indicated.
  • A sub-process expressed using BPMN
  • The sub-process as implemented by a Flow Rule Here we see how an initial draft of the PRPC Flow Rule for “Review Leave Request” might look. This diagram shows Pega Standard shapes.
  • The same Flow Rule in Pega’s version of BPMN And here we see how the initial draft of the PRPC Flow Rule might look using Pega’s version of BPMN shapes.
  • Compare the levels of visible detail
  • Compare the levels of visible detailBoth are supposed to be BPMN models of the sub-process
  • Compare the levels of visible detailPega Developers Network says: “BPMN stencil — By selectinga BPMN Visio stencil, you can create flow diagrams that closelymatch the appearance and notation used in Business ProcessManagement Notation (BPMN) diagrams.”
  • Compare the levels of visible detailBPMN is a standard modelling notation maintained by the Object Management Group.
  • Compare the levels of visible detailA BPMN modelling tool is either BPMN-compliant or it is not. Closely matching is not compliance.
  • Compare the levels of visible detailMoreover, the diagram on the right does not closely match the one on the left.
  • Compare the levels of visible detailBPMN-trained business stakeholders would understand the diagram on the left, but would be confused by the lack of BPMN-compliance in the Flow Rule on the right.
  • Compare the levels of visible detailIt would be better to show business stakeholders a Pega Standard Flow Rule and get them used to the Pega Standard notation.
  • Pega BPMN is just a way of “re-decorating” Flow Rules The Pega Standard notation is on the left and Pega BPMN on the right.
  • Pega BPMN is just a way of “re-decorating” Flow RulesAll Pega does is “re-paint” its Flow Rule shapes to look like BPMN shapes.
  • Pega BPMN is just a way of “re-decorating” Flow Rules This is not the same as BPMN-compliance.
  • Pega BPMN is just a way of “re-decorating” Flow RulesPRPC Flow Rules implement the business process andas design/implementation devices, they do not make all the necessary business steps explicit on the Flow.
  • Much of the logical detail is not explicit in the Flow Rule This slide highlights business process steps which are unlikely to be explicit on the Flow Rule, even though they are handled by Rules “behind” the Flow.
  • Compare the levels of visible detail From a business stakeholder perspective , the Flowdiagram does not fully represent the business process.
  • Compare the levels of visible detailHowever, a Flow Rule is not meant to illustrate the business process, rather its implementation.
  • Compare the levels of visible detailBut you should not try to use your Flow Rule to express something which it cannot.
  • Pega BPMN is not BPMN compliant
  • Pega BPMN is not BPMN compliantThe Integration shape that Pega uses on the “BPMN” view of the Flow is not part of the BPMN palette.
  • Pega BPMN is not BPMN compliantIn BPMN “diamond” shapes are known as “Gateways”and serve only as visual aids in navigating the diagram. No processing takes place inside a Gateway.
  • Pega BPMN is not BPMN compliantInstead, in BPMN, business rules are invoked and executed inside a task shape.
  • Pega BPMN is not BPMN compliantIn PRPC’s version of BPMN, there is behaviour going on inside “diamond” shapes, which breaks the rules of BPMN.
  • Pega BPMN is not BPMN compliantAlthough it is correct from a PRPC perspective to hideprocess details behind Flow Rule shapes, from a BPMN perspective, this is not correct.
  • Further limitations to Pega BPMN• Pega BPMN cannot and should not include manual steps. BPMN can and should.• Pega BPMN cannot and should not include steps and sub-processes executed in non PRPC systems. BPMN can and should.• Pega BPMN cannot and should not include steps and sub-processes which are out of scope for the current software implementation. BPMN can and should.• BPMN is technology-agnostic; Pega BPMN is technology-specific.
  • Conclusion• The Pega BPMN stencil is not a tool for creating BPMN models within PRPC.• It is a way of viewing PRPC Flow Rules using shapes reminiscent of BPMN.• Pega BPMN is not BPMN-compliant.• This non-compliance is likely to confuse stakeholders who are BPMN-trained.• Better to get stakeholders used to Pega Standard Flow Rules.
  • ConclusionIn golf, no matter how good your 3-iron is, you can’tturn it into an 8-iron by scratching on the number.
  • www.chellar.com/AnalysisFu