Business Process Model and Notation

1. Business Process Model and Notation Presenter： 蔡旻衛 2010/11/23

2. Outline • Introduction • Objective • BPMN Scope • Types of BPMN sub-model • BPMN Elements • BPMN Mappings to WS-BPEL

3. Introduction • A graphical representation for specifying business processes in a business process modeling. • Why we need BPMN？ • There are many process modeling tools and methodologies. • There are many business analysts define Business Processes with simple flow charts. • WS-BPELis hard to understand by the business analysts and managers to manage the process.

4. Introduction(cont.) • BPMN is currently maintained by the Object Management Group. • The web site of BPMN：http://www.bpmn.org/ • The current version of BPMN is 1.2, with a major revision process for BPMN 2.0 in progress.

5. Objective • To Provide a notation that is readily understandable by all business users, business analysts and technical developers. • To standardize a business process model and notation in the face of many different modeling notations. • To Ensure WS-BPEL that is visualized with a business-oriented notation.

6. BPMN Scope • BPMN will be constrained to support only the concepts of modeling that are applicable to business processes. • The modeling of the following will not be a part of BPMN： • Definition of organizational models and resources. • Modeling of functional breakdowns • Data and information models • Modeling of strategy • Business rules models

7. Types of BPMN sub-model • Processes (Orchestration) • Private non-executable Business Processes • Private executable Business Processes • Public Processes • Choreographies • Collaborations • Processes • Choreographies • Conversations

8. Processes • Private (Internal) Business Processes. • Public Processes.

9. Choreographies • A Choreography is different in that the Activities are interactions that represent a set (1 or more) of Message exchanges, which involves two (2) or more Participants.

10. Collaborations • All combinations of Pools, Processes, and a Choreography are allowed in a Collaboration.

11. Conversations • A Conversation is the logical relation of Message exchanges.

12. BPMN Elements • Flow Objects. • Data • Connecting Objects • Swimlanes • Artifacts

13. Flow Objects • Events • Activities • Gateways

14. Events

15. Activities • Task (Atomic) • Choreography Task • Collapsed Sub-Process • Expanded Sub-Process • Collapsed Sub-Choreography • Expanded Sub-Choreography

16. Activities(cont.)

17. Transaction

18. Event Sub-Process

19. Activity Markers

20. Task Types

21. Gateway

22. Looping • Activity Looping • Sequence Flow Looping

23. Multiple Instances

24. Data • Data Objects • Data Inputs • Data Outputs • Data Stores

25. Connecting Objects • Sequence Flows.

26. Connecting Objects(cont.) • Message Flows • Associations • Data Associations

27. Swim-lanes • Pools • Lanes

28. Artifacts • Group • Text Annotation

29. Exception Handler

30. Compensation

31. BPMN Mappings to WS-BPEL • Not all BPMN orchestration Processes can be mapped to WS-BPEL in a straight-forward way. • There are certain restrictions such as control-flow being either block-structured or not containing cycles

32. Process

33. Activities-Service Task

34. Receive Task

35. Send Task

36. Abstract Task

37. Message

38. Interface and Operation

39. Conversations and Correlation

40. Sub-Process

41. Event Sub-Processes(1)

42. Event Sub-Processes(2)

43. Event Sub-Processes(3)

44. Standard Loop

45. Loop with Maximum

46. Multi-Instance

47. Message Start Event

48. Message Intermediate Events(Non-boundary)

49. Timer Intermediate Events(Non-boundary)

50. Compensation Intermediate Events(Non-boundary)