Abstract image of a woman sitting on books and studying on a laptop

Evolution of Workflow Technology: Usages, Architectures, Languages

WSO2, profile picture
WSO2

This document discusses the evolution of workflow technology from the 1980s to present day. It covers 7 generations of workflow technology, from early document routing systems to the current focus on modeling and execution convergence. The architectures of workflow management systems are also examined, including key components like process modeling tools, workflow engines, and the invocation of application functions.

Technology
1 of 72
Downloaded 53 times
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
EvoluJon of Workflow Technology: Usages, Architectures, Languages University of Stu/gart Universitätsstr. 38 70569 Stu/gart Germany Phone +49-­‐711-­‐685 88470 Fax +49-­‐711-­‐685 88472 Prof. Dr. Frank Leymann InsJtute of Architecture of ApplicaJon Systems Leymann@iaas.uni-­‐stu/gart.de
© Frank Leymann 2 A Caveat! n “Workflow”, “Business Process” or simply “Process” are used synonymous n Although someJmes people make a subtle difference: n a business process is what happens in the real world, n a workflow is the corresponding representaJon in an IT environment n Same is true for “Workflow Model”, “Business Process Model”, “Process Model” n SomeJmes, it’s ok to speak about “workflow” if “workflow model” is meant n …and “(business) process” vs “(business) process model” n It most ocen clear from the context what is meant
2010 2005 2000 1995 1990 © Frank Leymann Business Processes as a Service Modeling/ExecuJon Convergence Mega Programming 3 Brief History of Workflow Technology (no scien>fic rigor intended) WF AutomaJon People Facing Web Service ComposiJon WF use in EAI Document RouJng/Case Processing 1985 BPR ProducJon WF TransacJonal WF WF-­‐based Apps WF StandardizaJon Begins Graphical Modeling WF in eScience Office AutomaJon, Forms Processing,…
4 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
5 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
© Frank Leymann 6 Why Care About Workflow Technology? n Companies use computers to support their business n The way to do business is prescribed via a business process n ApplicaJons support business processes and have to ensure compliance with business processes e Applica>on = Business Process + Business Func>ons n Changes in how to perform business must be reflected as soon as possible in applicaJons
© Frank Leymann 7 But the Really Important Thing is… From most companies’ perspecJve: Product = Process Thus: n # of products produced, sold,… = # of processes executed n Cost of producing, selling,… = Cost of process execuJon n Time of producing, selling,… = Time of process execuJon n …and so on ⇒ Importance of Business Process Engineering (BPR) ⇒ Importance of enforcing to follow the process model ⇒ Importance of monitoring, analyzing, mining processes
© Frank Leymann 8 Fundamental Metamodel Collect Credit InformaJon Assess Risk Request Approval Accept Credit Reject Credit risk = ‘low’ Layman’s View J salary < 1000 decision = ‘no’
© Frank Leymann 9 Three Dimensions of Workflows What? Good Customer? Who? Customer Address With? Get Order Check Customer Accept Order Reject Order Always! Bad Customer? Credit Card Information Worklists Workitem
© Frank Leymann 10 Workflow Execu>on Workitem Worklist WFMS
© Frank Leymann 11 Structure of Workflow-­‐Based Applica>on Business Process Models Service + … .EXE CICS MQ EJB Web Business Functions
WFMS Application Server © Frank Leymann 12 Key SWE Aspect of Workflow-­‐Based Applica>ons Application Data Independence Flow Independence DBMS DBMS
13 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
© Frank Leymann 14 1st Genera>on The Document Routing Age n Electronic document and folder rouJng (late 80s) n Document = image, folder,... n RouJng through enterprise's organizaJonal structure n User associated electronic basket is key n PotenJal flow of documents prescribed in advance n In "paper factories" (administraJon, insurance, banking,...) work mainly equates to processing documents, thus the term workflow has been used for rouJng documents between people
© Frank Leymann 15 2nd Genera>on The People-Facing Age n FuncJons performed by users in 1st generaJon WFMS are mainly retrieval, browsing, ediJng, archiving,... n But “cases” represented by documents were recognized to be only part of larger business processes n Not only execuJon of document management funcJons required but also usage of other funcJons provided by applicaJon systems supporJng the operaJon of an enterprise n WFMS extensions needed to invoke any kind of executable
© Frank Leymann 16 2nd Genera>on (cont.) n Launching executables requires parameter passing n Thus, data flow features complemented available control flows n In turn, control flows can now be expressed in terms of these new parameters ("business rules") n Data flow is used for integraJng applicaJons with long temporal delays between their iniJaJons n Parameters managed by data flow must be persistent
© Frank Leymann 17 3rd Genera>on The Dawn Of BPR n Being able to support large spectrum of business processes in compuJng environments made WFMS of strong interest for Business Process Reengineering (BPR) projects -­‐ early 90s n Goal of BPR is to speedup business processes and reduce their costs. ResulJng requirements: n Parallelism within workflows (à speedup) n Deadline processing (à speedup) n Monitor actual workflow status (à speedup) n AudiJng of significant events, i.e. processing history (à cost reducJon, compliance) n Maintain execuJon history for analysis (à cost reducJon, compliance) n Process acJviJes without human intervenJon (à speedup + cost reducJon)
© Frank Leymann 18 4th Genera>on The Production Age n Workflow-­‐based applicaJons become state-­‐of-­‐the-­‐art (mid 90s) n Strict separaJon of business process logic and business funcJons n Business processes implemented via workflow system n Business funcJons implemented "tradiJonally" (TP-­‐monitor, applicaJon server,...) n Enterprises become dependent on WFMS n Similar to TP-­‐Monitors and DBMS before n The term produc>on workflow has been coined to indicate that WFMS is driving operaJonal aspects of an enterprise (i.e. the “producJon line” of an enterprise) n Consequences: n WFMS had to provide quality of services known before from "producJon systems" like DBMS and TPM n High/conJnuous availability n Scalability n Robustness
© Frank Leymann 19 5th Genera>on The Automation Age n ApplicaJon integraJon becomes very important (end of 90s) n OrganizaJonal integraJon becomes more and more important n Interoperability of WFMS (building blocks), as well as Web access required n Workflows understood as business oriented "logical units of work" n Advanced transacJon management funcJons required n Forward recovery of workflows as well as workflow-­‐based applicaJons n Backward recovery (spheres of atomicity and compensaJon)
© Frank Leymann 20 6th Genera>on The Service Age n Web Services appeared about 2002 n Workflows needed to make use of Web Services n Interact with an ESB n Exploit human beings as Web services n Workflows have been considered early on as technology to aggregate services into new services n “Recursive aggregaJon model for Web services” n “OrchestraJon” n BPEL has been created to support all of this
© Frank Leymann 21 7th Genera>on The Model-Execution Age n Modeling of business processes gained a lot of a/enJon about 2005 n Domain experts became the immediate source of models n BPMN became predominant modeling language n Transforming models created by domain experts into something executable must not loose semanJcs of the original process n ExecuJng BPMN evolved as a requirement n …and BPMN 2.0 had been developed to support this
22 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
© Frank Leymann 23 Major Building Blocks of a WFMS Buildtime Modeling Tool (BPR, Workflows) Workflow Management System Runtime Workflow Database Process Model Applications, Tools
Data Modeling Tool Relational Algebra © Frank Leymann 24 ...And Their Correspondence In DBMS Buildtime Modeling Tool (BPR, Workflows) Workflow Management System Runtime Workflow Database Process Model Applications, Tools (Metamodel) SQL DDL Catalog User Data (tables, indexes,…) DBMS SQL DML StP, UDF,…
© Frank Leymann 25 The WfMC Reference Model Business Modeling Workflow Enactment Engine AdministraJon, AudiJng Workflow Enactment Engine Worklist Processor Worklist ApplicaJon ApplicaJon InvocaJon ApplicaJon
© Frank Leymann 26 Modern Terminology Process Modeling Tool Process (ExecuJon) Engine Management Tool Process Engine 2 Workitem Management Worklist ApplicaJon ApplicaJon InvocaJon ApplicaJon FuncJon
Input Container Output Container © Frank Leymann 27 Invoking Ac>vity Implementa>ons Worklist ... Workitem ... Activity Pgm 2 3 5 4 1
© Frank Leymann 28 Internal Component Flow Navigator MQM PES Invocation State & Metadata Pgm <OS Address Space> n WFMS Navigator determines program to be executed n "ExecuJon Messages" send to launching component called Program ExecuJon Server (PES) n "CompleJon Message" send back to Navigator when invoked program returns
© Frank Leymann 29 Program Execu>on Server Service Locator PES Info Extract Data n WFMS won't be able to support all mechanisms to launch executables n Thus, users should be able to build their own PESes, e.g. WFMS… n …provides interfaces between PES building blocks n ….defines required messages exchanged between navigator and PES (User-­‐provided PES (UPES)) n Specific metadata are needed by PES, e.g. security informaJon, mapping prescripJons etc. Mapping Program Invocation Invocation State & Metadata Program Data Format Pgm Operational Data PES J Yes, this is core ESB funcJonality!!!
© Frank Leymann 30 Architectural Impact Process Modeling Tool Management Orchestrator Tool Orchestrator 2 Workitem Management Worklist ApplicaJon Service Bus Service
Architectural Impact: High-­‐Level View n Work request no longer only created by WFMS n Thus, Workitem Manager is split from WFMS and becomes a separate component in SOA environment (“Task Manager”) Navigator © Frank Leymann 31 WFMS Workitem Manager WFMS Task Manager (aka Task Processor aka Human Task Infrastructure) Navigator TradiJonal Architecture Modern Architecture
© Frank Leymann 32 Architectural Impact Process Modeling Tool Process Engine Management Tool Process Engine 2 Task Manager Service Bus Task List Client Service
33 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
Process Management Stack Data Management Stack Conceptual Process Model © Frank Leymann 34 How People are Used to Model (BPMN) Transform Logical Process Model (BPEL) Deploy Process Engine Conceptual Data Model (e.g. Entity-Relationship) Transform Logical Data Model (e.g. SQL) Deploy DBMS
© Frank Leymann 35 Architectural Impact Process Modeling Tool Conceptual Process Model Logical Process Model Process Engine Management Tool ExecuJon Engine 2 Task Manager Service Bus Task List Client Service
© Frank Leymann 36 Workflow Language Genealogy WSFL FDML XPDL FDL BPEL XLANG BPMN 1.x (OMG) BPML WSCI BPSS WS-CDL (IBM) (IBM) (IBM) (Microsoft) (WfMC) (bpmi.org) (SUN, SAP, Oracle) (OASIS ebXML) (W3C) (IBM, Microsoft, BEA à OASIS) BPELJ GSFL … YAWL (Research Groups) BPEL4People BPEL-SPE ?…? GPEL Pi-Calculus++ (Microsoft) BPEL4Chor ✜-Calculus PM-Graphs BPMN 2.0 Petri-Nets (OMG)
© Frank Leymann 37 Other Languages n Data Flow oriented approaches n Especially used in scienJfic workflow community n Only data dependencies between acJviJes are modeled n As soon as all input data of an acJvity is available, start the acJvity n Examples: DAGMan, Kepler, Taverna, Triana n Research prototypes n DeclaraJve approaches n Define constraints of valid execuJon “sequences” instead of specifying all poten/al execuJon “sequences” n Based on some temporal logic (e.g. LTL) n Example: DECLARE n Research prototype n Rule-­‐based approaches n Mainly based on ECA rules n Example: Lotus Notes workflow ObservaJon: Products focus on control flow languages
The “mother” of all workflow languages IT Infractructure ("With") © Frank Leymann 38 Flow Defini>on Language (FDL): Example PROCESS 'Loan Process' PROGRAM_ACTIVITY 'Collect Credit Information' PROGRAM 'Credit Information Program' DONE_BY 'Loan Officer' END 'Collect Credit Information' PROGRAM_ACTIVITY 'Assess Risk' PROGRAM 'Risk Program' DONE_BY 'Financial Officer' END 'Assess Risk' CONTROL FROM 'Collect Credit Information' TO 'Assess Risk' END 'Loan Process' PROGRAM 'Credit Information Program' WINNT EXE PATH_AND_FILENAME 'CIP.EXE' END 'Credit Information Program' PROGRAM 'Risk Program' AIX EXE PATH_AND_FILENAME 'RP.EXE' END 'Risk Program' ROLE 'Loan Officer' RELATED_PERSON 'Leymann' END 'Loan Officer' ROLE 'Financial Officer' RELATED_PERSON 'Roller' END 'Financial Officer' PERSON 'Leymann' FIRST_NAME 'Frank' LAST_NAME 'Leymann' END 'Leymann PERSON 'Roller' FIRST_NAME 'Dieter' LAST_NAME 'Roller' END 'Roller' Process Logic ("What") Process Logistics ("Who")
© Frank Leymann 39 BPEL: Business Processes Between Web Services X Y Z pt3 o1 o2 pt1 o1 o3 o4 pt2 o2 o4
© Frank Leymann 40 BPEL: Business Processes As Web Services X Y Z pt o1 o2 pt* o7 o9 o8
© Frank Leymann 41 BPEL: Aggrega>ng Web Services X Y Z pt o1 o2 pt3 o1 o2 pt1 o1 o3 o4 pt2 o2 o4 P Q pt* o8 o9 Precisely: BPEL provides a recursive aggregation model for Web services
© Frank Leymann 42 Separa>ng Processes And Port Types Process A C B D E Application Deployment Descriptors Activity: Partner Role Port Type Operation ... Port Types
Process © Frank Leymann 43 Run>me: Use of Deployment Informa>on A C B D E Service Bus Application Deployment Descriptors Activity: Port Type Operation Qos ... Policy EPR Ports
Deployment Service © Frank Leymann 44 Programming Model Application Flow/Process/… Components/Services/… Workflow System Application Server Programming in the Large Programming in the Small Bus Deployment Descriptor pT pLink Locator
© Frank Leymann 45 BPEL: Example (The Obvious One J) TravelService orderTrip receiveItinarary getHotel getFlight chargeCC HotelService bookRoom AirlineService bookFlight CCService payBill Hotel Airline CCCompany TravelAgent overnight?
© Frank Leymann 46 The Process Header And Partners <process name=“TripBookingProcess" targetNamespace="http://fl.com/Travel/Booking" xmlns="http://schemas.xmlsoap.org/ws/2003/05/business-process" xmlns:tag="http://travel.org/wsdl/travelAgent"> <partnerLinks> <partnerLink name="Customer" partnerLinkType="tag:Traveler" myRole="TravelAgent"/> <partnerLink name="Hotel" partnerLinkType="tag:Hotel" partnerRole="HotelChain"/> <partnerLink name="Airline" partnerLinkType="tag:Airline" partnerRole="AirlineCompany"/> <partnerLink name="Billing" partnerLinkType="tag:CreditCard" partnerRole="CreditCardCompany"/> </partnerLinks>
© Frank Leymann 47 The Variables <variables> <variable name="Order" messageType=“tag:trip"/> <variable name="Hotel" messageType="tag:hotelBooking"/> <variable name="Flight" messageType="tag:flightBooking"/> <variable name="payment" messageType="tag:payments"/> </variables>
© Frank Leymann 48 The Ac>vi>es (1/5) <flow> <links> <link name="Itinerary-to-Hotel"/> <link name="Itinerary-to-Flight"/> <link name="Hotel-to-Charge"/> <link name="Flight-to-Charge"/> </links> <receive name=“receiveItinerary” partnerLink="Customer" portType="tag:TravelService" operation="orderTrip" variable="Order"> <source linkName="Itinerary-to-Hotel“ overnight? transitionCondition=“overnight=‘true’"/> <source linkName="Itinerary-to-Flight"/> </receive> .... receiveItinarary getHotel getFlight chargeCC
© Frank Leymann 49 The Ac>vi>es (2/5) .... <assign> <copy> <from variable="Order" part="itinerary" query="/rooms"/> <to variable="Hotel"/> </copy> </assign> <assign> <copy> <from variable="Order" part="itinerary" query="/flights"/> <to variable="Flight"/> </copy> </assign> ....
© Frank Leymann 50 The Ac>vi>es (3/5) ... <invoke name=“getHotel” partnerLink="Hotel" portType="tag:HotelService" operation="bookRoom" inputVariable="Hotel"> <target linkName="Itinerary-to-Hotel"/> <source linkName="Hotel-to-Charge"/> </invoke> <invoke name=“getFlight” partnerLink="Airline" portType="tag:AirlineService" operation="bookFlight" inputVariable="Flight"> <target linkName="Itinerary-to-Flight"/> <source linkName="Flight-to-Charge"/> </invoke> ... receiveItinarary overnight? getHotel getFlight chargeCC
© Frank Leymann 51 The Ac>vi>es (4/5) .... <assign> <copy> <from variable="Order" part="customerInfo"/> <to variable="Payment" part="customerInfo"/> </copy> <copy> <from variable="Hotel"/> <to variable="Payment" part="orders" query="/rooms"/> </copy> <copy> <from variable="Flight"/> <to variable="Payment" part="orders" query="/flights"/> </copy> </assign> ....
© Frank Leymann 52 The Ac>vi>es (5/5) ... <invoke name=“chargeCC” partnerLink="Billing" portType="tag:CreditCardService" operation="payBill" inputVariable="Payment“ joinCondition= overnight? "vprop:getLinkStatus(‘Hotel-to-Charge') or vprop:getLinkStatus(‘Flight-to-Charge')"> <target linkName="Hotel-to-Charge"/> <target linkName="Flight-to-Charge"/> </invoke> </flow> </process> receiveItinarary getHotel getFlight chargeCC
© Frank Leymann 53 BPMN: A Graphical Language
© Frank Leymann 54 Basic Order Process
© Frank Leymann 55 Order Process with Excep>on Paths
© Frank Leymann 56 Order Process with Swimlanes
© Frank Leymann 57 Subprocesses
© Frank Leymann 58 Parallel Split and Join
© Frank Leymann 59 Excep>on Handling
© Frank Leymann 60 Choreographies
61 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
KPIs Analysis © Frank Leymann 62 BPM Lifecycle Modeling IT Refinement Deployment ExecuJon Monitoring
BPM Lifecycle: Modeling KPIs Analysis © Frank Leymann 63 BPMN n Today, typically based on BPMN (2.0) n Done by domain experts n StaJc analysis used to “quickly” check obvious modeling errors n AnalyJcal simulaJon used to check saJsfacJon of KPIs Modeling IT Refinement Deployment ExecuJon Monitoring
BPM Lifecycle: IT Refinement KPIs Analysis © Frank Leymann 64 BPEL n Today, ocen generaJon of BPEL from BPMN n Web services have to be determined that perform the tasks of the processes n Done by IT experts Modeling IT Refinement Deployment ExecuJon Monitoring
BPM Lifecycle: IT Refinement 2.0 KPIs Analysis © Frank Leymann 65 BPMN 2.0 n If a BPMN 2.0 engine is used, no transformaJon is needed n As before, Web services have to be determined that perform the tasks of the processes n Done by IT experts Modeling IT Refinement Deployment ExecuJon Monitoring
BPM Lifecycle: Deployment KPIs Analysis © Frank Leymann 66 BPEL BPMN 2.0 n The Web services of the refined process model must be bound to endpoints n Well, task can have different implementaJons (like scripts, EJBs, REST APIs,…) n They must be bound too n Done by IT experts Modeling IT Refinement Deployment ExecuJon Monitoring
BPM Lifecycle: Execu>on KPIs Analysis © Frank Leymann 67 BPEL BPMN 2.0 n Either a BPEL engine executes the transformed BPMN model, or n …a BPMN 2.0 engine executes the BPMN 2.0 model n In any case the bound task implementaJons are invoked during navigaJng the process models Modeling IT Refinement Deployment ExecuJon Monitoring
KPIs Analysis © Frank Leymann 68 BPM Lifecycle: Monitoring n During execuJon the actual status of each running process is available n Individual processes can be inspected and depicted n CollecJons of processes can be defined, and their aggregated status can be depicted n The status of (aggregaJons of) processes can be enriched with other informaJon to enable deeper inside Modeling IT Refinement Deployment ExecuJon Monitoring
KPIs Analysis © Frank Leymann 69 BPM Lifecycle: Analysis n The history of already completed processes is maintained n This allows post mortem analysis of (collecJons of) processes n Used to improve models of processes n …to be/er saJsfy KPIs n Can be combined with data analysis to derive be/er models n Mining algorithms can be used n …to improve control flow n …to improve use of staff n … Modeling IT Refinement Deployment ExecuJon Monitoring
70 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
© Frank Leymann 71 Conclusion n Process knowledge is a key resource of a company n Workflow technology is managing this knowledge n The technology is mature and proven (≈25 years of evoluJon in pracJce) n WFMS architectures are compliant with a service-­‐ oriented environment n Two languages have been established in pracJce n BPMN (2.0) for modeling n BPEL for execuJon n Processes are managed in a lifecycle that typically use specialized technologies in an integrated manner
72 The End

More Related Content

PDF
BPMN on One Page
Mohamed Zakarya Abdelgawad
 
PPTX
Humans Are (Not) A Service - A journey towards Oracle BPM - OOW 2011 - OPITZ...
OPITZ CONSULTING Deutschland
 
PDF
Is project management worth the expense? How can you know?
Kolinger & Associates, LLC
 
PPTX
Scientific Workflows Systems :In Drug discovery informatics
Khaled Tumbi
 
PPT
Business Process Modeling
Sandy Kemsley
 
PDF
Introduction to Business Process Management
Alan McSweeney
 
PPTX
Importance of executable processes and BPMN
Alexander SAMARIN
 
PPTX
01-VSM-VSD-Training-Presentation-20140406-pptx.pptx
abdullahmohamed10900
 
BPMN on One Page
Mohamed Zakarya Abdelgawad
 
Humans Are (Not) A Service - A journey towards Oracle BPM - OOW 2011 - OPITZ...
OPITZ CONSULTING Deutschland
 
Is project management worth the expense? How can you know?
Kolinger & Associates, LLC
 
Scientific Workflows Systems :In Drug discovery informatics
Khaled Tumbi
 
Business Process Modeling
Sandy Kemsley
 
Introduction to Business Process Management
Alan McSweeney
 
Importance of executable processes and BPMN
Alexander SAMARIN
 
01-VSM-VSD-Training-Presentation-20140406-pptx.pptx
abdullahmohamed10900
 

Similar to Evolution of Workflow Technology: Usages, Architectures, Languages (20)

PDF
Leveraging Plm
Mandar Kotasthane
 
PPTX
business_process_management_introduction.pptx
DediIskandar56
 
PPS
A Business Process-Centric Approach To Financial Transactions
corbanmiferreira
 
PDF
Webinar: BPMN with camunda
camunda services GmbH
 
PDF
Workflow tecnologies
Riccardo Lemmi
 
PDF
2014 08 11_combionic_grc_introduction
Karl-Heinz Sternemann
 
PPTX
Oracle ACM Implementation - Best Practices
OPITZ CONSULTING Deutschland
 
PDF
Setup and Maintenance Factors of Adap3ve Case Management Systems - AdaptiveCM...
Thanh Tran
 
PPT
D1 3 200710 Poznan+Paris Bpm Arch
brutkowski
 
PDF
Not your grandfathers BPM
InfinIT - Innovationsnetværket for it
 
PDF
PLM_for_New_Normal_KK_Pres_May15
Siemens PLM Software
 
PDF
An Inside Look At Extreme Programming Essay
Sharon Roberts
 
PDF
Business Process Management - From Market Consolidation to Process Innovation
Michael zur Muehlen
 
PDF
Mathematical concepts applied to operations management
Rakesh Kariholoo
 
PPT
Process-Oriented Business Requirements
Dafna Levy
 
PPT
Analyzing Business Requirements in a Visible Enterprise
Dafna Levy
 
PDF
Agile pgm
Dr. Frank Stumpe
 
PDF
Re-Architect Your Legacy Environment To Enable An Agile, Future-Ready Enterprise
Dell World
 
PDF
Pivoting event streaming, from PROJECTS to a PLATFORM
confluent
 
PPTX
WF_in_retail_banking_enterprise_systems
Oleh Zheleznyak
 
Leveraging Plm
Mandar Kotasthane
 
business_process_management_introduction.pptx
DediIskandar56
 
A Business Process-Centric Approach To Financial Transactions
corbanmiferreira
 
Webinar: BPMN with camunda
camunda services GmbH
 
Workflow tecnologies
Riccardo Lemmi
 
2014 08 11_combionic_grc_introduction
Karl-Heinz Sternemann
 
Oracle ACM Implementation - Best Practices
OPITZ CONSULTING Deutschland
 
Setup and Maintenance Factors of Adap3ve Case Management Systems - AdaptiveCM...
Thanh Tran
 
D1 3 200710 Poznan+Paris Bpm Arch
brutkowski
 
Not your grandfathers BPM
InfinIT - Innovationsnetværket for it
 
PLM_for_New_Normal_KK_Pres_May15
Siemens PLM Software
 
An Inside Look At Extreme Programming Essay
Sharon Roberts
 
Business Process Management - From Market Consolidation to Process Innovation
Michael zur Muehlen
 
Mathematical concepts applied to operations management
Rakesh Kariholoo
 
Process-Oriented Business Requirements
Dafna Levy
 
Analyzing Business Requirements in a Visible Enterprise
Dafna Levy
 
Agile pgm
Dr. Frank Stumpe
 
Re-Architect Your Legacy Environment To Enable An Agile, Future-Ready Enterprise
Dell World
 
Pivoting event streaming, from PROJECTS to a PLATFORM
confluent
 
WF_in_retail_banking_enterprise_systems
Oleh Zheleznyak
 
Ad

More from WSO2 (20)

PDF
Demystifying CMS-0057-F - Compliance Made Seamless with WSO2
WSO2
 
PDF
Quantum Threats Are Closer Than You Think – Act Now to Stay Secure
WSO2
 
PDF
Modern Platform Engineering with Choreo - The AI-Native Internal Developer Pl...
WSO2
 
PDF
Application Modernization with Choreo - The AI-Native Internal Developer Plat...
WSO2
 
PDF
Build Smarter, Deliver Faster with Choreo - An AI Native Internal Developer P...
WSO2
 
PDF
Platformless Modernization with Choreo.pdf
WSO2
 
PDF
Application Modernization with Choreo for the BFSI Sector
WSO2
 
PDF
Choreo - The AI-Native Internal Developer Platform as a Service: Overview
WSO2
 
PDF
[Roundtable] Choreo - The AI-Native Internal Developer Platform as a Service
WSO2
 
PPTX
WSO2Con 2025 - Building AI Applications in the Enterprise (Part 1)
WSO2
 
PPTX
WSO2Con 2025 - Building Secure Business Customer and Partner Experience (B2B)...
WSO2
 
PPTX
WSO2Con 2025 - Building Secure Customer Experience Apps
WSO2
 
PPTX
WSO2Con 2025 - AI-Driven API Design, Development, and Consumption with Enhanc...
WSO2
 
PPTX
WSO2Con 2025 - AI-Driven API Design, Development, and Consumption with Enhanc...
WSO2
 
PPTX
WSO2Con 2025 - Unified Management of Ingress and Egress Across Multiple API G...
WSO2
 
PPTX
WSO2Con 2025 - How an Internal Developer Platform Lets Developers Focus on Code
WSO2
 
PPTX
WSO2Con 2025 - Architecting Cloud-Native Applications
WSO2
 
PDF
Mastering Intelligent Digital Experiences with Platformless Modernization
WSO2
 
PDF
Accelerate Enterprise Software Engineering with Platformless
WSO2
 
PDF
WSO2Con2024 - WSO2's IAM Vision: Identity-Led Digital Transformation
WSO2
 
Demystifying CMS-0057-F - Compliance Made Seamless with WSO2
WSO2
 
Quantum Threats Are Closer Than You Think – Act Now to Stay Secure
WSO2
 
Modern Platform Engineering with Choreo - The AI-Native Internal Developer Pl...
WSO2
 
Application Modernization with Choreo - The AI-Native Internal Developer Plat...
WSO2
 
Build Smarter, Deliver Faster with Choreo - An AI Native Internal Developer P...
WSO2
 
Platformless Modernization with Choreo.pdf
WSO2
 
Application Modernization with Choreo for the BFSI Sector
WSO2
 
Choreo - The AI-Native Internal Developer Platform as a Service: Overview
WSO2
 
[Roundtable] Choreo - The AI-Native Internal Developer Platform as a Service
WSO2
 
WSO2Con 2025 - Building AI Applications in the Enterprise (Part 1)
WSO2
 
WSO2Con 2025 - Building Secure Business Customer and Partner Experience (B2B)...
WSO2
 
WSO2Con 2025 - Building Secure Customer Experience Apps
WSO2
 
WSO2Con 2025 - AI-Driven API Design, Development, and Consumption with Enhanc...
WSO2
 
WSO2Con 2025 - AI-Driven API Design, Development, and Consumption with Enhanc...
WSO2
 
WSO2Con 2025 - Unified Management of Ingress and Egress Across Multiple API G...
WSO2
 
WSO2Con 2025 - How an Internal Developer Platform Lets Developers Focus on Code
WSO2
 
WSO2Con 2025 - Architecting Cloud-Native Applications
WSO2
 
Mastering Intelligent Digital Experiences with Platformless Modernization
WSO2
 
Accelerate Enterprise Software Engineering with Platformless
WSO2
 
WSO2Con2024 - WSO2's IAM Vision: Identity-Led Digital Transformation
WSO2
 
Ad

Recently uploaded (20)

PDF
Getting started with AI Agents and Multi-Agent Systems
Maxim Salnikov
 
PDF
NewMind AI Weekly Chronicles – August ’25 Week III
NewMind AI
 
PPTX
Chapter 5: Probability Theory and Statistics
RandyFin
 
PPT
Module 1.ppt Iot fundamentals and Architecture
nanditha7766
 
PDF
Hybrid model detection and classification of lung cancer
IAESIJAI
 
PPT
What is a Computer? Input Devices /output devices
GulJan8
 
PDF
Univ-Connecticut-ChatGPT-Presentaion.pdf
ry7r52mzb4
 
PPTX
O2C Customer Invoices to Receipt V15A.pptx
ssuserbfa915
 
PDF
sustainability-14-14877-v2.pddhzftheheeeee
VenkateshGovindaraja9
 
PPTX
MicrosoftCybserSecurityReferenceArchitecture-April-2025.pptx
SilvioHayashi
 
PPTX
Final SEM Unit 1 for mit wpu at pune .pptx
anishtilekar08
 
PDF
Enhancing emotion recognition model for a student engagement use case through...
IAESIJAI
 
PDF
ENT215_Completing-a-large-scale-migration-and-modernization-with-AWS.pdf
ssuser28425f
 
PPTX
Group 1 Presentation -Planning and Decision Making .pptx
MatthewLewis227954
 
PDF
Taming the Chaos: How to Turn Unstructured Data into Decisions
Safe Software
 
PDF
1 - Historical Antecedents, Social Consideration.pdf
tuazon2030627
 
PPTX
The various Industrial Revolutions .pptx
bandileshozi3
 
PDF
Video forgery: An extensive analysis of inter-and intra-frame manipulation al...
IAESIJAI
 
PDF
CloudStack 4.21: First Look Webinar slides
ShapeBlue
 
PDF
Hindi spoken digit analysis for native and non-native speakers
IAESIJAI
 
Getting started with AI Agents and Multi-Agent Systems
Maxim Salnikov
 
NewMind AI Weekly Chronicles – August ’25 Week III
NewMind AI
 
Chapter 5: Probability Theory and Statistics
RandyFin
 
Module 1.ppt Iot fundamentals and Architecture
nanditha7766
 
Hybrid model detection and classification of lung cancer
IAESIJAI
 
What is a Computer? Input Devices /output devices
GulJan8
 
Univ-Connecticut-ChatGPT-Presentaion.pdf
ry7r52mzb4
 
O2C Customer Invoices to Receipt V15A.pptx
ssuserbfa915
 
sustainability-14-14877-v2.pddhzftheheeeee
VenkateshGovindaraja9
 
MicrosoftCybserSecurityReferenceArchitecture-April-2025.pptx
SilvioHayashi
 
Final SEM Unit 1 for mit wpu at pune .pptx
anishtilekar08
 
Enhancing emotion recognition model for a student engagement use case through...
IAESIJAI
 
ENT215_Completing-a-large-scale-migration-and-modernization-with-AWS.pdf
ssuser28425f
 
Group 1 Presentation -Planning and Decision Making .pptx
MatthewLewis227954
 
Taming the Chaos: How to Turn Unstructured Data into Decisions
Safe Software
 
1 - Historical Antecedents, Social Consideration.pdf
tuazon2030627
 
The various Industrial Revolutions .pptx
bandileshozi3
 
Video forgery: An extensive analysis of inter-and intra-frame manipulation al...
IAESIJAI
 
CloudStack 4.21: First Look Webinar slides
ShapeBlue
 
Hindi spoken digit analysis for native and non-native speakers
IAESIJAI
 

Evolution of Workflow Technology: Usages, Architectures, Languages

  • 1. EvoluJon of Workflow Technology: Usages, Architectures, Languages University of Stu/gart Universitätsstr. 38 70569 Stu/gart Germany Phone +49-­‐711-­‐685 88470 Fax +49-­‐711-­‐685 88472 Prof. Dr. Frank Leymann InsJtute of Architecture of ApplicaJon Systems Leymann@iaas.uni-­‐stu/gart.de
  • 2. © Frank Leymann 2 A Caveat! n “Workflow”, “Business Process” or simply “Process” are used synonymous n Although someJmes people make a subtle difference: n a business process is what happens in the real world, n a workflow is the corresponding representaJon in an IT environment n Same is true for “Workflow Model”, “Business Process Model”, “Process Model” n SomeJmes, it’s ok to speak about “workflow” if “workflow model” is meant n …and “(business) process” vs “(business) process model” n It most ocen clear from the context what is meant
  • 3. 2010 2005 2000 1995 1990 © Frank Leymann Business Processes as a Service Modeling/ExecuJon Convergence Mega Programming 3 Brief History of Workflow Technology (no scien>fic rigor intended) WF AutomaJon People Facing Web Service ComposiJon WF use in EAI Document RouJng/Case Processing 1985 BPR ProducJon WF TransacJonal WF WF-­‐based Apps WF StandardizaJon Begins Graphical Modeling WF in eScience Office AutomaJon, Forms Processing,…
  • 4. 4 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
  • 5. 5 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
  • 6. © Frank Leymann 6 Why Care About Workflow Technology? n Companies use computers to support their business n The way to do business is prescribed via a business process n ApplicaJons support business processes and have to ensure compliance with business processes e Applica>on = Business Process + Business Func>ons n Changes in how to perform business must be reflected as soon as possible in applicaJons
  • 7. © Frank Leymann 7 But the Really Important Thing is… From most companies’ perspecJve: Product = Process Thus: n # of products produced, sold,… = # of processes executed n Cost of producing, selling,… = Cost of process execuJon n Time of producing, selling,… = Time of process execuJon n …and so on ⇒ Importance of Business Process Engineering (BPR) ⇒ Importance of enforcing to follow the process model ⇒ Importance of monitoring, analyzing, mining processes
  • 8. © Frank Leymann 8 Fundamental Metamodel Collect Credit InformaJon Assess Risk Request Approval Accept Credit Reject Credit risk = ‘low’ Layman’s View J salary < 1000 decision = ‘no’
  • 9. © Frank Leymann 9 Three Dimensions of Workflows What? Good Customer? Who? Customer Address With? Get Order Check Customer Accept Order Reject Order Always! Bad Customer? Credit Card Information Worklists Workitem
  • 10. © Frank Leymann 10 Workflow Execu>on Workitem Worklist WFMS
  • 11. © Frank Leymann 11 Structure of Workflow-­‐Based Applica>on Business Process Models Service + … .EXE CICS MQ EJB Web Business Functions
  • 12. WFMS Application Server © Frank Leymann 12 Key SWE Aspect of Workflow-­‐Based Applica>ons Application Data Independence Flow Independence DBMS DBMS
  • 13. 13 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
  • 14. © Frank Leymann 14 1st Genera>on The Document Routing Age n Electronic document and folder rouJng (late 80s) n Document = image, folder,... n RouJng through enterprise's organizaJonal structure n User associated electronic basket is key n PotenJal flow of documents prescribed in advance n In "paper factories" (administraJon, insurance, banking,...) work mainly equates to processing documents, thus the term workflow has been used for rouJng documents between people
  • 15. © Frank Leymann 15 2nd Genera>on The People-Facing Age n FuncJons performed by users in 1st generaJon WFMS are mainly retrieval, browsing, ediJng, archiving,... n But “cases” represented by documents were recognized to be only part of larger business processes n Not only execuJon of document management funcJons required but also usage of other funcJons provided by applicaJon systems supporJng the operaJon of an enterprise n WFMS extensions needed to invoke any kind of executable
  • 16. © Frank Leymann 16 2nd Genera>on (cont.) n Launching executables requires parameter passing n Thus, data flow features complemented available control flows n In turn, control flows can now be expressed in terms of these new parameters ("business rules") n Data flow is used for integraJng applicaJons with long temporal delays between their iniJaJons n Parameters managed by data flow must be persistent
  • 17. © Frank Leymann 17 3rd Genera>on The Dawn Of BPR n Being able to support large spectrum of business processes in compuJng environments made WFMS of strong interest for Business Process Reengineering (BPR) projects -­‐ early 90s n Goal of BPR is to speedup business processes and reduce their costs. ResulJng requirements: n Parallelism within workflows (à speedup) n Deadline processing (à speedup) n Monitor actual workflow status (à speedup) n AudiJng of significant events, i.e. processing history (à cost reducJon, compliance) n Maintain execuJon history for analysis (à cost reducJon, compliance) n Process acJviJes without human intervenJon (à speedup + cost reducJon)
  • 18. © Frank Leymann 18 4th Genera>on The Production Age n Workflow-­‐based applicaJons become state-­‐of-­‐the-­‐art (mid 90s) n Strict separaJon of business process logic and business funcJons n Business processes implemented via workflow system n Business funcJons implemented "tradiJonally" (TP-­‐monitor, applicaJon server,...) n Enterprises become dependent on WFMS n Similar to TP-­‐Monitors and DBMS before n The term produc>on workflow has been coined to indicate that WFMS is driving operaJonal aspects of an enterprise (i.e. the “producJon line” of an enterprise) n Consequences: n WFMS had to provide quality of services known before from "producJon systems" like DBMS and TPM n High/conJnuous availability n Scalability n Robustness
  • 19. © Frank Leymann 19 5th Genera>on The Automation Age n ApplicaJon integraJon becomes very important (end of 90s) n OrganizaJonal integraJon becomes more and more important n Interoperability of WFMS (building blocks), as well as Web access required n Workflows understood as business oriented "logical units of work" n Advanced transacJon management funcJons required n Forward recovery of workflows as well as workflow-­‐based applicaJons n Backward recovery (spheres of atomicity and compensaJon)
  • 20. © Frank Leymann 20 6th Genera>on The Service Age n Web Services appeared about 2002 n Workflows needed to make use of Web Services n Interact with an ESB n Exploit human beings as Web services n Workflows have been considered early on as technology to aggregate services into new services n “Recursive aggregaJon model for Web services” n “OrchestraJon” n BPEL has been created to support all of this
  • 21. © Frank Leymann 21 7th Genera>on The Model-Execution Age n Modeling of business processes gained a lot of a/enJon about 2005 n Domain experts became the immediate source of models n BPMN became predominant modeling language n Transforming models created by domain experts into something executable must not loose semanJcs of the original process n ExecuJng BPMN evolved as a requirement n …and BPMN 2.0 had been developed to support this
  • 22. 22 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
  • 23. © Frank Leymann 23 Major Building Blocks of a WFMS Buildtime Modeling Tool (BPR, Workflows) Workflow Management System Runtime Workflow Database Process Model Applications, Tools
  • 24. Data Modeling Tool Relational Algebra © Frank Leymann 24 ...And Their Correspondence In DBMS Buildtime Modeling Tool (BPR, Workflows) Workflow Management System Runtime Workflow Database Process Model Applications, Tools (Metamodel) SQL DDL Catalog User Data (tables, indexes,…) DBMS SQL DML StP, UDF,…
  • 25. © Frank Leymann 25 The WfMC Reference Model Business Modeling Workflow Enactment Engine AdministraJon, AudiJng Workflow Enactment Engine Worklist Processor Worklist ApplicaJon ApplicaJon InvocaJon ApplicaJon
  • 26. © Frank Leymann 26 Modern Terminology Process Modeling Tool Process (ExecuJon) Engine Management Tool Process Engine 2 Workitem Management Worklist ApplicaJon ApplicaJon InvocaJon ApplicaJon FuncJon
  • 27. Input Container Output Container © Frank Leymann 27 Invoking Ac>vity Implementa>ons Worklist ... Workitem ... Activity Pgm 2 3 5 4 1
  • 28. © Frank Leymann 28 Internal Component Flow Navigator MQM PES Invocation State & Metadata Pgm <OS Address Space> n WFMS Navigator determines program to be executed n "ExecuJon Messages" send to launching component called Program ExecuJon Server (PES) n "CompleJon Message" send back to Navigator when invoked program returns
  • 29. © Frank Leymann 29 Program Execu>on Server Service Locator PES Info Extract Data n WFMS won't be able to support all mechanisms to launch executables n Thus, users should be able to build their own PESes, e.g. WFMS… n …provides interfaces between PES building blocks n ….defines required messages exchanged between navigator and PES (User-­‐provided PES (UPES)) n Specific metadata are needed by PES, e.g. security informaJon, mapping prescripJons etc. Mapping Program Invocation Invocation State & Metadata Program Data Format Pgm Operational Data PES J Yes, this is core ESB funcJonality!!!
  • 30. © Frank Leymann 30 Architectural Impact Process Modeling Tool Management Orchestrator Tool Orchestrator 2 Workitem Management Worklist ApplicaJon Service Bus Service
  • 31. Architectural Impact: High-­‐Level View n Work request no longer only created by WFMS n Thus, Workitem Manager is split from WFMS and becomes a separate component in SOA environment (“Task Manager”) Navigator © Frank Leymann 31 WFMS Workitem Manager WFMS Task Manager (aka Task Processor aka Human Task Infrastructure) Navigator TradiJonal Architecture Modern Architecture
  • 32. © Frank Leymann 32 Architectural Impact Process Modeling Tool Process Engine Management Tool Process Engine 2 Task Manager Service Bus Task List Client Service
  • 33. 33 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
  • 34. Process Management Stack Data Management Stack Conceptual Process Model © Frank Leymann 34 How People are Used to Model (BPMN) Transform Logical Process Model (BPEL) Deploy Process Engine Conceptual Data Model (e.g. Entity-Relationship) Transform Logical Data Model (e.g. SQL) Deploy DBMS
  • 35. © Frank Leymann 35 Architectural Impact Process Modeling Tool Conceptual Process Model Logical Process Model Process Engine Management Tool ExecuJon Engine 2 Task Manager Service Bus Task List Client Service
  • 36. © Frank Leymann 36 Workflow Language Genealogy WSFL FDML XPDL FDL BPEL XLANG BPMN 1.x (OMG) BPML WSCI BPSS WS-CDL (IBM) (IBM) (IBM) (Microsoft) (WfMC) (bpmi.org) (SUN, SAP, Oracle) (OASIS ebXML) (W3C) (IBM, Microsoft, BEA à OASIS) BPELJ GSFL … YAWL (Research Groups) BPEL4People BPEL-SPE ?…? GPEL Pi-Calculus++ (Microsoft) BPEL4Chor ✜-Calculus PM-Graphs BPMN 2.0 Petri-Nets (OMG)
  • 37. © Frank Leymann 37 Other Languages n Data Flow oriented approaches n Especially used in scienJfic workflow community n Only data dependencies between acJviJes are modeled n As soon as all input data of an acJvity is available, start the acJvity n Examples: DAGMan, Kepler, Taverna, Triana n Research prototypes n DeclaraJve approaches n Define constraints of valid execuJon “sequences” instead of specifying all poten/al execuJon “sequences” n Based on some temporal logic (e.g. LTL) n Example: DECLARE n Research prototype n Rule-­‐based approaches n Mainly based on ECA rules n Example: Lotus Notes workflow ObservaJon: Products focus on control flow languages
  • 38. The “mother” of all workflow languages IT Infractructure ("With") © Frank Leymann 38 Flow Defini>on Language (FDL): Example PROCESS 'Loan Process' PROGRAM_ACTIVITY 'Collect Credit Information' PROGRAM 'Credit Information Program' DONE_BY 'Loan Officer' END 'Collect Credit Information' PROGRAM_ACTIVITY 'Assess Risk' PROGRAM 'Risk Program' DONE_BY 'Financial Officer' END 'Assess Risk' CONTROL FROM 'Collect Credit Information' TO 'Assess Risk' END 'Loan Process' PROGRAM 'Credit Information Program' WINNT EXE PATH_AND_FILENAME 'CIP.EXE' END 'Credit Information Program' PROGRAM 'Risk Program' AIX EXE PATH_AND_FILENAME 'RP.EXE' END 'Risk Program' ROLE 'Loan Officer' RELATED_PERSON 'Leymann' END 'Loan Officer' ROLE 'Financial Officer' RELATED_PERSON 'Roller' END 'Financial Officer' PERSON 'Leymann' FIRST_NAME 'Frank' LAST_NAME 'Leymann' END 'Leymann PERSON 'Roller' FIRST_NAME 'Dieter' LAST_NAME 'Roller' END 'Roller' Process Logic ("What") Process Logistics ("Who")
  • 39. © Frank Leymann 39 BPEL: Business Processes Between Web Services X Y Z pt3 o1 o2 pt1 o1 o3 o4 pt2 o2 o4
  • 40. © Frank Leymann 40 BPEL: Business Processes As Web Services X Y Z pt o1 o2 pt* o7 o9 o8
  • 41. © Frank Leymann 41 BPEL: Aggrega>ng Web Services X Y Z pt o1 o2 pt3 o1 o2 pt1 o1 o3 o4 pt2 o2 o4 P Q pt* o8 o9 Precisely: BPEL provides a recursive aggregation model for Web services
  • 42. © Frank Leymann 42 Separa>ng Processes And Port Types Process A C B D E Application Deployment Descriptors Activity: Partner Role Port Type Operation ... Port Types
  • 43. Process © Frank Leymann 43 Run>me: Use of Deployment Informa>on A C B D E Service Bus Application Deployment Descriptors Activity: Port Type Operation Qos ... Policy EPR Ports
  • 44. Deployment Service © Frank Leymann 44 Programming Model Application Flow/Process/… Components/Services/… Workflow System Application Server Programming in the Large Programming in the Small Bus Deployment Descriptor pT pLink Locator
  • 45. © Frank Leymann 45 BPEL: Example (The Obvious One J) TravelService orderTrip receiveItinarary getHotel getFlight chargeCC HotelService bookRoom AirlineService bookFlight CCService payBill Hotel Airline CCCompany TravelAgent overnight?
  • 46. © Frank Leymann 46 The Process Header And Partners <process name=“TripBookingProcess" targetNamespace="http://fl.com/Travel/Booking" xmlns="http://schemas.xmlsoap.org/ws/2003/05/business-process" xmlns:tag="http://travel.org/wsdl/travelAgent"> <partnerLinks> <partnerLink name="Customer" partnerLinkType="tag:Traveler" myRole="TravelAgent"/> <partnerLink name="Hotel" partnerLinkType="tag:Hotel" partnerRole="HotelChain"/> <partnerLink name="Airline" partnerLinkType="tag:Airline" partnerRole="AirlineCompany"/> <partnerLink name="Billing" partnerLinkType="tag:CreditCard" partnerRole="CreditCardCompany"/> </partnerLinks>
  • 47. © Frank Leymann 47 The Variables <variables> <variable name="Order" messageType=“tag:trip"/> <variable name="Hotel" messageType="tag:hotelBooking"/> <variable name="Flight" messageType="tag:flightBooking"/> <variable name="payment" messageType="tag:payments"/> </variables>
  • 48. © Frank Leymann 48 The Ac>vi>es (1/5) <flow> <links> <link name="Itinerary-to-Hotel"/> <link name="Itinerary-to-Flight"/> <link name="Hotel-to-Charge"/> <link name="Flight-to-Charge"/> </links> <receive name=“receiveItinerary” partnerLink="Customer" portType="tag:TravelService" operation="orderTrip" variable="Order"> <source linkName="Itinerary-to-Hotel“ overnight? transitionCondition=“overnight=‘true’"/> <source linkName="Itinerary-to-Flight"/> </receive> .... receiveItinarary getHotel getFlight chargeCC
  • 49. © Frank Leymann 49 The Ac>vi>es (2/5) .... <assign> <copy> <from variable="Order" part="itinerary" query="/rooms"/> <to variable="Hotel"/> </copy> </assign> <assign> <copy> <from variable="Order" part="itinerary" query="/flights"/> <to variable="Flight"/> </copy> </assign> ....
  • 50. © Frank Leymann 50 The Ac>vi>es (3/5) ... <invoke name=“getHotel” partnerLink="Hotel" portType="tag:HotelService" operation="bookRoom" inputVariable="Hotel"> <target linkName="Itinerary-to-Hotel"/> <source linkName="Hotel-to-Charge"/> </invoke> <invoke name=“getFlight” partnerLink="Airline" portType="tag:AirlineService" operation="bookFlight" inputVariable="Flight"> <target linkName="Itinerary-to-Flight"/> <source linkName="Flight-to-Charge"/> </invoke> ... receiveItinarary overnight? getHotel getFlight chargeCC
  • 51. © Frank Leymann 51 The Ac>vi>es (4/5) .... <assign> <copy> <from variable="Order" part="customerInfo"/> <to variable="Payment" part="customerInfo"/> </copy> <copy> <from variable="Hotel"/> <to variable="Payment" part="orders" query="/rooms"/> </copy> <copy> <from variable="Flight"/> <to variable="Payment" part="orders" query="/flights"/> </copy> </assign> ....
  • 52. © Frank Leymann 52 The Ac>vi>es (5/5) ... <invoke name=“chargeCC” partnerLink="Billing" portType="tag:CreditCardService" operation="payBill" inputVariable="Payment“ joinCondition= overnight? "vprop:getLinkStatus(‘Hotel-to-Charge') or vprop:getLinkStatus(‘Flight-to-Charge')"> <target linkName="Hotel-to-Charge"/> <target linkName="Flight-to-Charge"/> </invoke> </flow> </process> receiveItinarary getHotel getFlight chargeCC
  • 53. © Frank Leymann 53 BPMN: A Graphical Language
  • 54. © Frank Leymann 54 Basic Order Process
  • 55. © Frank Leymann 55 Order Process with Excep>on Paths
  • 56. © Frank Leymann 56 Order Process with Swimlanes
  • 57. © Frank Leymann 57 Subprocesses
  • 58. © Frank Leymann 58 Parallel Split and Join
  • 59. © Frank Leymann 59 Excep>on Handling
  • 60. © Frank Leymann 60 Choreographies
  • 61. 61 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
  • 62. KPIs Analysis © Frank Leymann 62 BPM Lifecycle Modeling IT Refinement Deployment ExecuJon Monitoring
  • 63. BPM Lifecycle: Modeling KPIs Analysis © Frank Leymann 63 BPMN n Today, typically based on BPMN (2.0) n Done by domain experts n StaJc analysis used to “quickly” check obvious modeling errors n AnalyJcal simulaJon used to check saJsfacJon of KPIs Modeling IT Refinement Deployment ExecuJon Monitoring
  • 64. BPM Lifecycle: IT Refinement KPIs Analysis © Frank Leymann 64 BPEL n Today, ocen generaJon of BPEL from BPMN n Web services have to be determined that perform the tasks of the processes n Done by IT experts Modeling IT Refinement Deployment ExecuJon Monitoring
  • 65. BPM Lifecycle: IT Refinement 2.0 KPIs Analysis © Frank Leymann 65 BPMN 2.0 n If a BPMN 2.0 engine is used, no transformaJon is needed n As before, Web services have to be determined that perform the tasks of the processes n Done by IT experts Modeling IT Refinement Deployment ExecuJon Monitoring
  • 66. BPM Lifecycle: Deployment KPIs Analysis © Frank Leymann 66 BPEL BPMN 2.0 n The Web services of the refined process model must be bound to endpoints n Well, task can have different implementaJons (like scripts, EJBs, REST APIs,…) n They must be bound too n Done by IT experts Modeling IT Refinement Deployment ExecuJon Monitoring
  • 67. BPM Lifecycle: Execu>on KPIs Analysis © Frank Leymann 67 BPEL BPMN 2.0 n Either a BPEL engine executes the transformed BPMN model, or n …a BPMN 2.0 engine executes the BPMN 2.0 model n In any case the bound task implementaJons are invoked during navigaJng the process models Modeling IT Refinement Deployment ExecuJon Monitoring
  • 68. KPIs Analysis © Frank Leymann 68 BPM Lifecycle: Monitoring n During execuJon the actual status of each running process is available n Individual processes can be inspected and depicted n CollecJons of processes can be defined, and their aggregated status can be depicted n The status of (aggregaJons of) processes can be enriched with other informaJon to enable deeper inside Modeling IT Refinement Deployment ExecuJon Monitoring
  • 69. KPIs Analysis © Frank Leymann 69 BPM Lifecycle: Analysis n The history of already completed processes is maintained n This allows post mortem analysis of (collecJons of) processes n Used to improve models of processes n …to be/er saJsfy KPIs n Can be combined with data analysis to derive be/er models n Mining algorithms can be used n …to improve control flow n …to improve use of staff n … Modeling IT Refinement Deployment ExecuJon Monitoring
  • 70. 70 Agenda Out of the Galaxy EvoluJon Architectures Languages BPM Lifecylce Summary
  • 71. © Frank Leymann 71 Conclusion n Process knowledge is a key resource of a company n Workflow technology is managing this knowledge n The technology is mature and proven (≈25 years of evoluJon in pracJce) n WFMS architectures are compliant with a service-­‐ oriented environment n Two languages have been established in pracJce n BPMN (2.0) for modeling n BPEL for execuJon n Processes are managed in a lifecycle that typically use specialized technologies in an integrated manner