Bpmn2010

1,406 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,406
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
26
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Bpmn2010

  1. 1. Fachliche vs. Technische Prozesse Jakob Freund, camunda services GmbH
  2. 2. Camunda is a small BPM consulting company Your • BPM Business • BPMN • Agile • BRM camunda Business Consulting Your Your Your Process Process Process Application Application Application camunda IT Consulting
  3. 3. 09/2009 Aktuelle Trends x2 Quelle: BPM-Netzwerk.de x1,6 07/2010
  4. 4. Über 80 Neukunden in zwei Jahren
  5. 5. Prozessmodelle für verschiedenste Zwecke und Rollen ISO-Zertifizierung Mindestanforderungen Für Risiko-Management (MARisk) Organisationshandbuch Prozessanalyse und Schriftlich -verbesserung fixierte Ordnung Workflow Management Automatisierung Serviceorientierte Anforderungs- Architekturen (SOA) management
  6. 6. Exemplarische Themen und Prozesse  Bereitstellung von DSL-Anschlüssen  Aus- und Umbau des Mobilfunknetzes  Regulierung von Schäden (Kfz, Hausrat etc.)  Vertrieb von Darlehen  Vertrieb von Medikamenten  Logistische Abwicklung von Waren und Fertigungserzeugnissen  Prüf- und Genehmigungsverfahren (ÖD)  Rechnungseingangsbearbeitung  Angebotserstellung und -nachverfolgung  … und die Klassiker: Reisen, Urlaub, Fortbildung, Helpdesk etc.
  7. 7. Leben und leben lassen… We value… • Developer-Friendliness over Zero Coding • Smart Communication over Single-Source-Models • Composite Architectures over one-stop-shops • Open Source over Out-of-the-Box Business-IT-Alignment mit
  8. 8. camunda BPMN-Framework Prozesslandschaft Inhalt: Prozess im Überblick Ebene 1 Ziel: Schnelles Verständnis Strategisches Semantik: logisch-abstrakt Prozessmodell Inhalt: Operative Abläufe Ebene 2 Ziel: Abstimmung von Details Fachlich Operatives Prozessmodell Semantik: physisch-konkret (Business) Technisch (IT) Ebene 3a Inhalt: Technische Details Ebene 3b Technisches Ziel: Umsetzung IT-Spezifikation Prozessmodell Semantik: physisch-konkret Mit Process Engine Ebene 4b Implementierung Ohne Process Engine
  9. 9. Branche: Verlagswesen Der logisch-abstrakte Ablauf Tool: Signavio Process Editor
  10. 10. Branche: Verlagswesen Der physisch-konkrete Ablauf Tool: Signavio Process Editor
  11. 11. Kerngedanke #1: Brüche nach oben verlagern Prozesslandschaft Inhalt: Prozess im Überblick Ebene 1 Ziel: Schnelles Verständnis Strategisches Prozessmodell Inhalt: Operative Abläufe Ebene 2 Ziel: Arbeits- und Fachlich Operatives Prozessmodell Umsetzungsgrundlage (Business) Technisch (IT) Ebene 3a Ebene 3b Technisches IT-Spezifikation Prozessmodell Inhalt: Technische Details Ziel: Umsetzung Mit Process Engine Ebene 4b Implementierung Ohne Process Engine
  12. 12. Business vs. IT? It‘s NOT that simple! •Creates Technical Processes etc. •Manages the project •Plays the main part in process •Creates/Manages typical solution development project documents •Knows BPMN best (in IT) •Creates Process Models Project Lead •Links Process Models with •Is expert in certain aspect (e.g. GUI) other Requirements •Supports Process Engineer if needed •Knows BPMN Best (in •Creates services / components used Business) in process by plain development •Represents user •Knows the solution‘s •Defines Guidelines purpose best •Is somehow useful :-) •Can answer any question about functionality Process Analyst Architect Process Engineer Developer Domain Expert Business IT
  13. 13. Next Slides are based on BPMN 2.0 by Example BPMN 2.0 by Example http://www.omg.org/cgi-bin/doc?dtc/10-06-02 Activiti Showcase http://www.bpm-guide.de/activiti/
  14. 14. This is directly executable BPMN 2.0
  15. 15. Some Details depend on your BPM platform
  16. 16. <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <definitions id="oryx_c6b54c98-e3e8-44aa-8745-1f092b3150b6" typeLanguage="http://www.w3.org/2001/XMLSchema" expressionLanguage="http://www.w3.org/1999/XPath" targetNamespace="http://www.omg.org/bpmn20" xmlns="http://schema.omg.org/spec/BPMN/2.0" xmlns:bpmndi="http://bpmndi.org"> The corresponding BPMN 2.0 - XML <process isClosed="false" processType="executable" id="oryx_45eeff22-1e3f-4543-be07-084ea7cfd0b7"> <laneSet name="Process Engine" id="Process Engine"> <lane name="1st level support" id="1st level support_1"> <flowElementRef>Handle Problem [ID: ${issueID}]: ${issueTitle}_2</flowElementRef> <flowElementRef>Is issue resolved?_2</flowElementRef> <flowElementRef>issue reported_2</flowElementRef> <flowElementRef>Send an email back to the Call Center Agent_2</flowElementRef> <flowElementRef>ticket closed_2</flowElementRef> <flowElementRef>Send a confirmation email back to the Call Center Agent_2</flowElementRef> <flowElementRef>Set the issue classifciation_2</flowElementRef> </lane> <lane name="2snd level support" id="2snd level support_1"> <flowElementRef>Task Finished_2</flowElementRef> <flowElementRef>Edit Ticket from Level 1 [ID: ${issueID}]: ${issueTitle}_2</flowElementRef> <flowElementRef>Is issue now resolved?_2</flowElementRef> <flowElementRef>Insert issue into product backlog_2</flowElementRef> </lane> </laneSet> <userTask implementation="webService" completionQuantity="1" startQuantity="1" isForCompensation="false" name="Handle Problem [ID: ${issueID}]: ${issueTitle}" id="Handle Problem [ID: ${issueID}]: ${issueTitle}_2"/> <exclusiveGateway gatewayDirection="Diverging" name="Is issue resolved?" id="Is issue resolved?_2"/> <startEvent isInterrupting="true" name="issue reported" id="issue reported_2"> <messageEventDefinition/> </startEvent> <sendTask implementation="webService" completionQuantity="1" startQuantity="1" isForCompensation="false" name="Send an email back to the Call Center Agent" id="Send an email back to the Call Center Agent_2"/> <endEvent name="ticket closed" id="ticket closed_2"/> <sendTask implementation="webService" completionQuantity="1" startQuantity="1" isForCompensation="false" name="Send a confirmation email back to the Call Center Agent" id="Send a confirmation email back to the Call Center Agent_2"/> <scriptTask scriptLanguage="" completionQuantity="1" startQuantity="1" isForCompensation="false" name="Set the issue classifciation" id="Set the issue classifciation_2"> <script></script> </scriptTask> <message isInitiating="true" name="Task Finished" id="Task Finished_2"/> <userTask implementation="webService" completionQuantity="1" startQuantity="1" isForCompensation="false" name="Edit Ticket from Level 1 [ID: ${issueID}]: ${issueTitle}" id="Edit Ticket from Level 1 [ID: ${issueID}]: ${issueTitle}_2"/> <exclusiveGateway gatewayDirection="Diverging" name="Is issue now resolved?" id="Is issue now resolved?_2"/> <sendTask implementation="webService" completionQuantity="1" startQuantity="1" isForCompensation="false" name="Insert issue into product backlog" id="Insert issue into product backlog_2"/> <sequenceFlow targetRef="Is issue now resolved?_2" sourceRef="Edit Ticket from Level 1 [ID: ${issueID}]: ${issueTitle}_2" name="" id="SequenceFlow_6"/> <sequenceFlow targetRef="ticket closed_2" sourceRef="Send an email back to the Call Center Agent_2" name="" id="SequenceFlow_5"/> <sequenceFlow targetRef="Send a confirmation email back to the Call Center Agent_2" sourceRef="issue reported_2" name="" id="SequenceFlow_3"/> <sequenceFlow targetRef="Handle Problem [ID: ${issueID}]: ${issueTitle}_2" sourceRef="Send a confirmation email back to the Call Center Agent_2" name="" id="SequenceFlow_7"/> <sequenceFlow targetRef="Set the issue classifciation_2" sourceRef="Handle Problem [ID: ${issueID}]: ${issueTitle}_2" name="" id="SequenceFlow_9"/> <sequenceFlow targetRef="Is issue resolved?_2" sourceRef="Set the issue classifciation_2" name="" id="SequenceFlow"/> <sequenceFlow targetRef="Send an email back to the Call Center Agent_2" sourceRef="Insert issue into product backlog_2" name="" id="SequenceFlow_4"/> <sequenceFlow targetRef="Send an email back to the Call Center Agent_2" sourceRef="Is issue resolved?_2" name="" id="SequenceFlow_10"> <conditionExpression xsi:type="tFormalExpression" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">${issueResolved}</conditionExpression> </sequenceFlow> <sequenceFlow targetRef="Edit Ticket from Level 1 [ID: ${issueID}]: ${issueTitle}_2" sourceRef="Is issue resolved?_2" name="" id="SequenceFlow_8"> <conditionExpression xsi:type="tFormalExpression" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">${!issueResolved}</conditionExpression> </sequenceFlow> <sequenceFlow targetRef="Insert issue into product backlog_2" sourceRef="Is issue now resolved?_2" name="" id="SequenceFlow_1"> <conditionExpression xsi:type="tFormalExpression" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">${!issueResolved}</conditionExpression> </sequenceFlow> <sequenceFlow targetRef="Send an email back to the Call Center Agent_2" sourceRef="Is issue now resolved?_2" name="" id="SequenceFlow_2"> <conditionExpression xsi:type="tFormalExpression" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">${issueResolved}</conditionExpression> </sequenceFlow> </process> </definitions>
  17. 17. Here‘s your to-be- Business-IT-Alignment with executable that‘s process, ready to models? Huh, looks complicated! Where is the part deploy. Could you please approve? my business? Ehm, it‘s here. And there. And over there. Well somehow, half of that is somone else‘s todo. And some steps and But there are parts of decisions are completely the process (that automated. concern me) missing! Yes but those parts won‘t be executed by the engine. I cannot And what are those model them, they‘d break the technical flow. steps for then? Nobody Call Center specified them! Agent IT Yes but we need those steps. Otherwise we will get data inconsistencies Inconti-what!? This is in the process context. just your coding again, and not my process! I won‘t approve this. Ah, F*** Y**!
  18. 18. This what the Call Center Agent is really interested in • What do I have to do? • Who is the one I must interact with? • How do I work with the system? • What are my concerns?
  19. 19. The User and the Solution collaborate
  20. 20. It‘s all about collaboration! Domain Expert Process participants Process Process Engineer Engine Domain Expert Domain Expert Process Analyst Domain Expert
  21. 21. Kerngedanke #2: Verschiedene Sichten auf Ebene 2 Betrachter Process Participant Process Analyst Process Engineer „Wie muss ich „Wie wird „Was macht die Zentrale Frage arbeiten?“ gearbeitet?“ Engine?“ Eigene Gesamte Orchestrierung der Sicht Orchestrierung Kollaboration Process Engine Prozesslandschaft Ebene 1 Strategisches Prozessmodell Inhalt: Prozess im Überblick Ziel: Schnelles Verständnis Ebene 2: Operatives Prozessmodell Inhalt: Operative Abläufe Ebene 2 Ziel: Arbeits- und Fachlich Operatives Prozessmodell Umsetzungsgrundlage (Business) Technisch (IT) Ebene 3a Ebene 3b Technisches IT-Spezifikation Prozessmodell Inhalt: Technische Details Ziel: Umsetzung Mit Process Engine Ebene 4b Implementierung Ohne Process Engine
  22. 22. Branche: Schwerindustrie Kundenbeispiel: Reisemanagement Tool: SAP Netweaver CE 7.2
  23. 23. Branche: Energieversorger Kundenbeispiel: Stromzählerwartung Tool: inubit BPM-Suite
  24. 24. Tool-Unterstützung am Beispiel Signavio
  25. 25. Tool-Unterstützung am Beispiel Signavio
  26. 26. Tool-Unterstützung am Beispiel Signavio
  27. 27. IT-Projekt vs. Prozess-Projekt
  28. 28. Activiti (Open Source BPM Platform), an european project
  29. 29. Activiti Cycle (Contributed by Camunda)
  30. 30. Also der „Glue“ zwischen Ebene 2 und 3 Signavio / Activiti Modeler / Oryx Business-IT-Glue Activiti Cycle JBoss jBPM / Activiti / Bonita
  31. 31. Der Prozess im Zentrum der Anforderungen GUI Daten Funktio- Prozess Regeln nalität Tests NFRs
  32. 32. Basic Use Cases von Cycle
  33. 33. Prozessmodell mit JIRA koppeln
  34. 34. Hands-on-Collaboration: BPMN-Diagrams in JIRA
  35. 35. Den Entwicklungsfortschritt visualisieren
  36. 36. Wir machen uns Gedanken – Sie auch? I wish… I like… I mean… I ask… I hate… I think… I want… I… I need… I suck… BPM-Netzwerk.de Test.BPMN.info BPMB.de Camunda.com
  37. 37. Let‘s skip the peak (and the trough as well ) As-Is To-Be
  38. 38. Vielen Dank für Ihre Aufmerksamkeit!
  39. 39. camunda services GmbH Vielen Dank! Zossener Str. 55-58 1096 Berlin 1 Telefon: +49 30 664 0409-00 Telefax: +49 30 664 0409-29 Email: info@camunda.com Jakob Freund Geschäftsführer Jakob.Freund@camunda.com Der Praxis-Blog zu BPM: www.bpm-guide.de

×