The document discusses business process modeling notation (BPMN) which is an OMG standard for visually representing business processes. It provides an overview of BPMN concepts including flow elements, artifacts, pools and lanes. As an example, it shows a basic order management process diagram. The purpose of process modeling is for documentation, analysis, optimization and preparation for automation through workflow systems.

2. Basic concepts of OMGs Business Process Modeling Notation

3. Graphical elements of BPMN

4. Examples for applying concepts and notation

5. Module: Intro to modeling of processes

6. SOA Technologies Services as implementation of activities BPMN Model as base for executable BPEL Process Services as partners to define process interaction Services as implementation of activities BPMN Model as base for executable BPEL Process Services as partners to define process interaction Service layers Service layers

11. More information like required data, responsible persons, or utilized resources are required

12. “Enriched” models of control and data flow enable process automation

14. Modeling processes without having sophisticated technical IT-skills e.g. using Event-driven Process Chains (EPC), BPMN

15. Technical modeling deals with creating executable processes (aka “workflows”)

16. Refinement and technical implementation of process models

18. Arbitrary process models can be transformed without loss of information or manual changing/adapting process models

19. Module: Intro to BPMN “ This Version of BPMN does provide a non-normative mapping from BPMN to WS-BPEL, but the BPMN-Specification is known to be incomplete with respect to capturing all the required information for WS-BPEL. So mapping is insufficient in any case.” (BPMN Specification)

21. Business Process Diagram as a standardized graphical representation of business processes

23. Expressiveness: Further elements to describe “real life” processes in detail

24. Bridging the gap between business process design and implementation

25. Supports a basic mapping to BPEL, no automatic transformation from BPMN to BPEL available (even in theory!)

26. Example Process: Order management

28. Modeling collaboration is supported

30. Message flow for communication between different process participants

34. Three standardized artifacts ... but more can be added proprietary (Data Object, Group, Annotation)

36. Event: Occurs in the processing of the process

37. Gateway: to split/merge the control flow (sequence flow)

38. Connector: Define the order of processing of the elements Example:

41. Association must be undirected directional Non - directional