Business Process Modelling -10.2/2013 -
description
Transcript of Business Process Modelling -10.2/2013 -
Business Process Modelling-10.2/2013 -
Marcello La Rosa
Queensland University of Technology
Brisbane, 26 September 2013
© INB/INN320 10.2/2013 – 26 September 2013
Quick Repeat from Week 9
• How can we compensate for the effects of an activity?
• How can we perform routines in parallel to a process?
• What is an alternative notation to boundary events?
BPMN Modelling- Choreography diagrams -
© INB/INN320 10.2/2013 – 26 September 2013
BPMN 2.0 model types
© INB/INN320 10.2/2013 – 26 September 2013
Choreography Diagram
Focuses on the interactions among two or more participants.
Order
Order Cancelation
Cancelation Ack
Order Confirmation Payment
Invoice
Cus
tom
erM
anuf
actu
rer
Requestfor Quote
Quote
© INB/INN320 10.2/2013 – 26 September 2013
Choreography Diagram (cont’ed)
Cancel Order
Order
Place OrderGet Quote
Confirm Order
Order Cancelation
Cancelation Ack
Order Confirmation Payment
Pay for Order
Invoice
Cus
tom
erM
anuf
actu
rer
Requestfor Quote
Quote
Interactions can be explicitly
captured
© INB/INN320 10.2/2013 – 26 September 2013
Choreography Diagram (cont’ed)
Cancel Order
Customer
ManufactuerOrder
Place Order
Manufacturer
Customer
Requestfor Quote
Quote
Get Quote
Manufacturer
Customer
Confirm Order
Customer
Manufactuer
Order Cancelation
Cancelation Ack
Order Confirmation Payment
Pay for Order
Manufacturer
Customer
Invoice
Pools can be dropped
© INB/INN320 10.2/2013 – 26 September 2013
Choreography
Process model of the interactions taking place between two or more business parties
• Focuses on message exchange between parties• Acts as a contract between parties• Can be refined into private processes or into a
collaboration diagram
© INB/INN320 10.2/2013 – 26 September 2013
Choreography Task
• Atomic activity• Represents an interaction between two business parties• Either one-way (asynchronous) or two-way
(synchronous)• Distinction between initiating and receiving party
Recipient
Initiator
Choreography Task Name
© INB/INN320 10.2/2013 – 26 September 2013
Choreography Task
• Band of initiating party unfilled• Message icons optional
Choreography Task Collaboration View
Garage
Customer
Estimate of costs
Car
Cost estimate
Cus
tom
er
Handover car Evaluate cost estimation
Gar
age
Evaluate damage
CarCost estimate
...
...
© INB/INN320 10.2/2013 – 26 September 2013
Basic Choreography Elements
Sequence flow – Connects and orders choreography tasks, events and gateways
Events – Most process events allowed. No non-interrupting events
Gateways – All process gateways allowed: Exclusive, Inclusive, Parallel and Event-based gateways
AnnotationText annotations, groups – No restrictions on their use
© INB/INN320 10.2/2013 – 26 September 2013
Choreography Sequencing Constraints
The initiator of a Choreography Activity must have been involved in the previous Activity (excluding first activity)
Why?!
Business Process Model and Notation, Page 338OMG Document Number: formal/2011-01-03
January 2011
© INB/INN320 10.2/2013 – 26 September 2013
Choreography Sequencing Constraints
Business Process Model and Notation, Page 339
OMG Document Number: formal/2011-01-03
January 2011
© INB/INN320 10.2/2013 – 26 September 2013
Example: Choreography of an auction
A Seller sends information about an item he wants to sell to an auction Provider. The Provider publishes the auction by offering the item to the Bidder. Once the auction has started the Bidder may place an offer. In case the item is sold the auction Provider finalises the purchase with the Buyer, otherwise he notifies the Seller that his item has not been sold.
© INB/INN320 10.2/2013 – 26 September 2013
Solution: Choreography of an auction
Auction Provider
Seller
Compile auction
Auction Provider
Bidder
Place offer
Auction Provider
Buyer
Finalize purchaseItemsold
Auction Provider
Seller
Notify of unsold item
Itemnot sold
Auction Provider
Bidder
Offer item
Decision needs to be taken by
preceding interaction,
based on available data
Initiator must be the party that
took the decision
© INB/INN320 10.2/2013 – 26 September 2013
Choreography Task – Internal Markers
Only one of the loop or multi-instance applicable Loop Multi-instance
Party B
Party A
Choreography Task
Party
A Send Message
Party
B
Receive Message
Party B
Party A
Choreography Task
Party
A Send Message
Party
B
Receive Message
© INB/INN320 10.2/2013 – 26 September 2013
Choreography TaskMulti-instance Party marker
• Parties may be multi-instance• E.g. customers or shippers
Party B
Party A
Choreography Task
Party
A Send Message
Party
B Receive Message
© INB/INN320 10.2/2013 – 26 September 2013
Auction Provider
Seller
Compile auction
Auction Provider
Bidder
Place offer
Auction Provider
Buyer
Finalize purchaseItemsold
Auction Provider
Seller
Notify of unsold item
Itemnot sold
Auction Provider
Bidder
Offer item
Example: Choreography of an auction
Where can we use the MI party in the auction example?
Auction Provider
Seller
Compile auction
Auction Provider
Bidder
Place offer
Auction Provider
Buyer
Finalize purchaseItemsold
Auction Provider
Seller
Notify of unsold item
Itemnot sold
Auction Provider
Bidder
Offer item
© INB/INN320 10.2/2013 – 26 September 2013
Sub-Choreography
• Compound activity of a choreography• Involves at least two business parties• Loop, MI activity and MI party markers are applicable
Party A
Party C
Party B
Choreography Sub-Process Name
Party A
Party C
Party B
Choreography Sub-Process Name
Party A
Party B
Choreography Task Name X
Party B
Party C
Choreography Task Name Y
© INB/INN320 10.2/2013 – 26 September 2013
What is this choreography doing?
All parties involved in the interactions following the split must be involved in the interaction preceding the split, to
be aware of the timer
The interactions following an event-based split must have the same
receiver
© INB/INN320 10.2/2013 – 26 September 2013
Example: Choreography
Use this diagram as a template to build the corresponding collaboration diagram
© INB/INN320 10.2/2013 – 26 September 2013
Solution
So, what’s the difference between Collaboration and Choreography diagrams?
© INB/INN320 10.2/2013 – 26 September 2013
References
Required• Section 4.7 of Chapter 4 of textbook “Fundamentals of BPM”
Recommended• OMG (2011): BPMN 2.0 Specification• BPM Offensive (2011): BPMN 2.0 Poster• OGM (2010): BPMN 2.0 By Example
Web References• OMG BPM Initiative• BPMN Community
Books on BPMN• Silver B. (2011): “BPMN Method & Style” 2nd Edition, Cody-Cassidy
© INB/INN320 10.2/2013 – 26 September 2013
A/Prof. Marcello La RosaIS School Academic Director(Corporate Programs and Partnerships)BPM Discipline, IS School
Science & Engineering FacultyQueensland University of Technology126 Margaret StreetBrisbane QLD 4000Australia
p +61 (0)7 3138-9482e [email protected] www.marcellolarosa.com