Upload
others
View
6
Download
0
Embed Size (px)
Citation preview
Business Process Management: Workflow Models and Architectures
Prof. Kwanghoon Pio Kim Collaboration Technology Research Lab.
Department of Computer Science, Kyonggi University
January 29th, 2018
Information Technology Institute, Vietnam National University, Hanoi, Vietnam
ContentsI. WorkflowBasicsII. WorkflowDependenciesIII. ScientificWorkflowModelsIV.ScientificWorkflowArchitecturesV. Q&A
CTRL,CollaborationTechnologyResearchLab.
A. WoToWiTo since 1998• Publications : Over 350 Workflow-related Research Papers• Major Research Projects
• Hanuri/Tflow: Transactional Workflow Admin/Monitoring System Development1998~2000 with ETRI, ICU, KwangjooKAIST, POSDATA
• Multimedia Web Call Center Solution Development, 2000 with ETRI• Workflow Monitoring System Development, 2001 with POSDATA• Workflow-Based e-Logistics System for Postal Services, 2001 ~ 2003 with ETRI• EJB-Based Workflow Management System for e-Commerce, 2002 ~ 2003 Funded by
KOSEF• Cooperative Swimlane Workflow Modeling System, 2002 Funded by KRF• Workflow Warehousing and Mining Architecture, 2003 ~ 2004 Funded by MIC• ebXML Based Business Process Management System, 2002 ~ 2004 Funded by ETRI• Enterprise Grid Workflow Architectures and Systems, 2009 ~ 2010 Funded by NRF• Smart-space Based Collaboration Technologies, 2010 ~ 2016 Funded by GRRC Gyeonggi• Intelligent SCM Process Modeling Methodologies, 2010 ~ 2013 Funded by ETRI• Workflow-Supported Social Networks, 2013 ~ 2015 Funded by NRF, GRRC Gyeonggi• BPM-Supported Enterprise Social Network Intelligence Frameworks, 2017 ~ 2020 Funded by
NRFB. Contact Information
Cell +82-10-2059-8522 Phone +82-31-249-9679 Fax +82-31-249-9673E-Mail : [email protected]: http://ctrl.kyonggi.ac.kr
A HISTORIC VIEW OF WFMS
BPM System
Appl2 Appl3 Appl4 Appl5
File System Appl1 Appl6
DB System
Appl2
Appl3 Appl4 Appl5
File System Appl1 Appl6
Appl2
Appl3 Appl4 Appl5
File System
Appl1 Appl6
DB System
WfM System
2000s
1980s
1960s
DB System
WfM System
2020s File System
CLOUD CE
Appl2 Appl3 Appl4 Appl5
Appl1 Appl6
Distributed CE
Appl2
Appl3 Appl4 Appl5
Mainframe Appl1 Appl6
Appl2
Appl3 Appl4 Appl5
Mainframe
Appl1 Appl6
Distributed CE
GRID/P2P CE
2000s
1980s
1960s
Distributed CE
GRID/P2P CE
2020s Mainframe
Mainframe
Enterprise
Social Networks & Stochastic ICN Theories
Social/ Affiliation/Diffusion
Network Discovery & Rediscovery Theories
Social Network Analysis Process-driven Web Services & Social Networks
전사적 응용프로그램 통합(EAI) Enterprise Applications
Integration Solution 전사적 자원 관리(ERP) Enterprise Resource Planning
소프트웨어서비스 SaaS: Software as a Service
비피엠지식 발견/재발견 BPM Knowledge Discovery/Rediscovery
스마트 엔터프라이즈 Smart Enterprise Workflows
FROM OFFICE AUTOMATION TO WORKFLOW MANAGEMENT
STANDARD: WFMC - WORKFLOW MANAGEMENT COALITION
Workflow API and Interchange Formats
Workflow Enactment Service
Workflow Engine(s)
Workflow Definition Tool(s)
Administration & Monitoring Tool(s)
Workflow Runtime Client
Invoked Applications
Other Workflow Enactment Services
Workflow Engine(s)
INTERFACE - 1
INTERFACE - 2 INTERFACE - 3
INTERFACE - 5
INTERFACE - 4
WfMC’s Workflow Standardization Reference Model
VARIOUS COMPONENTS OF A WORKFLOW MANAGEMENT SYSTEM
Workflow Engine(s)
Analytical Tool
Resource Classification Tool
Workflow Definition Tool
Operational Management Tool
Recording & Reporting Tool
analysis data
resource classifications
process definitions
operational management
data
historical data
standard worklist handler
integreated worklist handler automatic
applications
interactive applications
application data
internal data
logistical management data
TRIGGERS
OTHER WORKFLOW SYSTEMS
APPLICATIONS AND ROLES ON WFMS
Workflow Management System
Application Application Application Application
administrator
application designer
application programmer
database designer
database programmer
process analyst
workflow designer
employee
manager
워크플로우 관리 시스템과 응용프로그램과의 관계 그리고 사용자의 유형 The Workflow Designer: The Workflow Designer uses the Process Definition Tools. In other words, the process
definition tool, the resource classification tool and the analysis tools. This designer works on the structure of the workflow.
The Administrator: The Administrator uses the operational management tool. His/her typical activities include adding employees, issuing and withdrawing authorizations, implementing new processes, monitoring workflows and solving problems and bottlenecks.
The Process Analyst: The Process Analyst uses the recording and reporting tool to inform the management about the performance of the workflows. By aggregating detailed data into performance indicators, it is possible to provide insight into the operation of the business processes which are supported by the workflow management system.
The Employee: The execution of work is carried out by employees. In this book, they are also referred to as resources. Such resources are the scarce means of production which need to be employed in the best way possible.
AN ARCHITECTURAL VIEW OF A WORKFLOW MANAGEMENT SYSTEM
Business Process Definition Tool
User Interface Worklist Handler
Generates Process Definition
References
Manipulate
Interact via
Invokes
Requests Svc Web Service(s)
May reference
External service/program/data Software component System control data
Processes’ Application Data
BPM Engine(s)
Application(s)
maintain
use
update
may refer to
(Supervisor) Administration & Control
Organization/ Role Model
Process Control Data
Data
Process Relevant Data
Business Process Registry & Enactment
Technology
Interpreted by
Business Process Modeling Technology: WPDL, XPDL, BPML, BPMN, BPEL, …
Work List
Business Process Client (User Agent)
Technology
Business Process Applications & Web Services Technology
(Users)
Reply Svc
Workflow Basics
Workflow Models - Information Control Nets - Petri Nets Workflow Dependencies Workflow Architectures
WorkflowManagementSystemsWorkflow Management System
Modeling Component Enacting Component
Workflow Models
Workflow Languages
Modeling Tools • Editor • Browser • Compiler • Simulator • Animator • Debugger • Administrator
Workflow Architectures
Enacting Tools • Work-list Handler • End User Tools • Monitor • Analyzer • Administrator • Configuration Tools • Process Mining Tools
syntax semantics
So far, several types of workflow models have been introduced in the literature. Almost all of the currently available workflow management systems are based upon the following types of workflow model: Communication-based Model [7] This model stems from Winograd/Flores’ ”Conversation for Action Model”. It assumes that the objective of office procedure reengineering
is to improve customer satisfaction. It reduces every action in a workflow for four phases based on communication between a customer and a performer: Preparation, Negotiation, Performance, and Acceptance phase. But this model is not appropriate for modeling and supporting the development of workflow implementations which have some objectives such as minimizing information system cost(not customer satisfaction), because it has some limitations in supporting the development of workflow management; For example, it is not able to indicate which activities can occur in parallel, in conditional, or in alternative.
Activity-based Model [6–8] This model focuses on modeling the work instead of modeling the commitments among humans. Unlike communication-based model, activity-based model does not capture objectives such as customer satisfaction. Many commercial workflow management systems provide activity-based workflow models. The ICN-based workflow model, which is the major part of this chapter, is one of the activity-based models. Also, there are several extensions such as procedure-based model, document-based model, goal-based model, and object-oriented model. Especially, the goal- based model is a typical example that combines the communication-based model and the activity- based model.
Perspective-based Model [34] The model supports the specification of workflows through several perspectives: the functional(the functional units of workflow processing), the behavior (the control flow of workflow), the information(the data flow of workflow), the operational(the applications deployed in workflow), and the organizational (the organizational structure and actors who perform the work- flow) perspective. This model focuses on the open aspects to support the integration of additional perspectives such as the history perspective and transactional perspective.
Transactional Model [34] This model involves the specification of the extended transaction management that consists of a set of constituent transactions corresponding to the workflow activities, and a set of transaction dependencies between them corresponding to the workflow structure and correct- ness criterion. Thus, the model focuses on the system-oriented workflows, not the human-oriented workflows. The system-oriented workflow involves computer systems that perform computation- intensive operations and specialized software tasks. That is, while the human-oriented workflow often controls an coordinates human tasks, the system-oriented workflow controls and coordinates software tasks.
WorkflowModelingComponents
ACTOR ROLE ACTIVITY Invoked Application
Computer Program Web Service
Programming language with APIs
Script
WORKFLOW PROCEDURE Transition Condition Job Organization
Group
Computing Facility
Relevant Data
Input Output
is player of
is player of is member of
is involved in own
is associated with
have precedence use
have is state of is consisting of
is a is a
is a is a is a is a
A workflow procedure is defined by a predefined or intended set of tasks or steps, called activities, and their temporal ordering of executions. A workflow management system helps to organize, control, and execute such defined workflow procedures. Conclusively, a workflow procedure can be described by a temporal order of the associated activities through the combinations of sequential logics, conjunctive logics (after activity A, do activities B and C), disjunctive logics (after activity A, do activity B or C), and loop logics.
An activity is a conceptual entity of the basic unit of work (task or step), and the activities in a workflow procedure have precedence relationships, each other, in terms of their execution sequences. Also, the activity can be precisely specified by one of the three entity types—compound activity, elementary activity and gateway activity. The compound activity represents an activity containing another workflow procedure, which is called sub-workflow. The elementary activity is an activity that can be realized by a computer program, such as application program, transaction, script, or web service. And the gateway activity implies an activity that is used to controlling execution sequences of elementary/compound activities. The types of gateway activities consist of conjunctive gateway (after activity A, do activities B and C), disjunctive gateway (after activity A, do activity B or C), and loop gateway. Particularly, both the disjunctive gateway and the loop gateway need to be set some specific transition conditions in order to select one of the possible transition pathes during the execution time. The transition condition itself can be defined by using the input/output relevant data on the repository. Additionally, each activity has to be associated with a real performer, such as organizational staff (role, participant) and system, who possesses all ownerships over that activity.
A role, as an logical unit of the organizational structure, is a named designator for one or more participants, which conveniently acts as the basis for participating works, skills, access controls, execution controls, authority, and responsibility over the associated activity.
An actor is a person, program, or entity that can fulfill roles to execute, to be responsible for, or to be associated in some way with activities and workflow procedures. Multiple instances of a workflow procedure may be in various stages of execution. Thus, the workflow procedure can be considered as a class (in object oriented terminology), and each
execution, called a workcase, can be considered an instance. A workcase is thus defined as the locus of control for a particular execution of a workflow procedure. An invoked application program that automatically performs the associated activity, or provides automated assistance within hybrid activities are called scripts. If an activity is executed
in automatic or hybrid mode, this means that whole/part of the invoked application program associated with the activity is automatically launched by an workflow enactment service.
Finally, a repository (relevant data) is a set of input and output relevant data of an activity. Eventually, the repository provides a communication channel between the workflow enactment domain and the invoked application programs domain. That is, the input and the output repositories are used to realizing the input parameters and the output parameters of the associated invoked application program, respectively.
work item task activity
case
ICN,InformationControlNetsControl-FlowandData-Flow
α1
α2
α3
α4
α5
α6
α7
α8
α17
α18
α19
α21
α22
α20
αI
αF Termination
Apply Activity New Applicant Info(Database) Activity
Education Checkup Activity Medical Screening Activity
Security Checkup Activity Employment Checkup Activity
Hiring Activity
Decision Activity
Request Compensation Activity
Offer Letter Activity
Review Report Activity
Database Update Activity
Initiation
Rejecting Activity
Database Update Activity
(Control Flow)
Decision (γ2 ) == “No”
Decision (γ2 ) == “Yes”
α9
α13
α10
α14
α11
α15
α12
α16
α23
α24
α25
α26
α27
α28
α29
α30
Education Review Activity Medical Review Activity
Employment Review Activity Security Review Activity
α1
α2
α3
α4
α5
α6
α7
α8
α17
α18
α19
α21
α22
α20
αI
αF Termination
Initiation
γ1 : Applicant Information
(Relevant Data Flow)
γ2 : Decision Result
γ4 : Checkup Results
γ5 : Review Results
α9
α13
α10
α14
α11
α15
α12
α16
α23
α24
α25
α26
α27
α28
α29
α30
γ3 : Checkup Done
ICN,InformationControlNetsRoleandPerformerAssignments
α1
α2
α3
α4
α5
α6
α7
α8
α17
α18
α19
α20
αI
αF Termination
Apply Activity (η1 : Applicant)
New Applicant Info(Database) Activity (η2 : Hiring Clerk)
Hiring Activity (η2 : Hiring Clerk)
Decision Activity (η3 : Hiring Manager)
Request Compensation Activity (η2 : Hiring Clerk)
Offer Letter Activity (η2 : Hiring Clerk)
Review Results Activity (η2 : Hiring Clerk)
Database Update Activity (η10 : Computer)
Initiation
Rejecting Activity (η2 : Hiring Clerk)
Database Update Activity (η10: Computer)
(Role Assignment) (Performer Assignment)
α1
α2
α3
α4
α5
α6
α7
α8
α17
α18
α19
α21
α22
α20
αI
αF
η1 (ο1)
η2 (ο2, ο3, ο4)
η3 (ο5)
η2 (ο2, ο3 , ο4)
η10 (ο17)
η10 (ο17)
Decision (γ2 ) == “No”
Decision (γ2 ) == “Yes”
α21
α22
α9
α13
α10
α14
α11
α15
α12
α16
α23
α24
α25
α26
α27
α28
α29
α30
Education Review Activity (η7: Personal Manager)
Medical Review Activity (η8 : Medical Manager)
Employment Review Activity (η9 : Security Manager)
Security Review Activity (η7: Personal Manager)
Education Checkup Activity (η4 : Personal Clerk)
Medical Screening Activity (η6 : Medical Clerk)
Security Checkup Activity (η5 : Security Clear)
Employment Checkup Activity (η4 : Personal Clerk)
α9
α13
α10
α14
α11
α15
α12
α16
α23
α24
α25
α26
α27
α28
α29
α30
η2 (ο5, ο6)
η2 (ο7, ο8 , ο9)
η2 (ο2, ο3 , ο4)
η2 (ο2, ο3 , ο4)
η4 (ο10 , ο11)
η5 (ο12)
η6 (ο13)
η4 (ο10 , ο11)
η7 (ο14)
η9 (ο16)
η8 (ο15)
η7 (ο14)
PetriNets
start
contact client positive
assess
end
send letter
record
pay
contact department
collect negative
file
CASE 5
CASE 4 CASE 3
CASE 2 CASE 1
contact client
record
contact department
collect
start
positive
assess
end
send letter
pay
negative
file
PetriNets-RoutingPatterns Sequential routing
Parallel routing
Selective routing
c1 task2 task1 c3 c2
task1 t1
task2
t2 c1 c4 c2
c5 c3
c6
task1
task2
c4 c2
c5 c3
t11 t21 c1 c6
t12 t22
OR-split OR-join
c6
task1 c1
task2
OR-split OR-join
Selective routing
Iterative routing
task1
t1 task2
c1 c2
c3
c6
OR-split
OR-join
Decision rule
c3
t11 c1 c6
OR-split
task1
task2
OR-join
c2
t12
Preconditions
c1 task2 task1 c3
c2
task3
t c6 c4
c1 task1 c2 task3
t c6 c4
task2 c3 OR, AND, and AND/OR Gateway Notations
t OR-split
t OR-join
t AND-split
t
AND-join
t AND/OR-split
WorkflowDependencies
Activity Dependent Model
Control Dependency Information
Workflow Optimization
The Workflow Dependency Analyses
Framework
Control Dependency Analysis
ICN-based Workflow
Models
ICN Graphical Representation Of Workflow
ICN Formal Representation Of Workflow
Role Dependency Analysis
Actor Dependency Analysis
Data Dependency Analysis
Data Dependent Model
Role Dependent Model
Actor Dependent Model
Data
Dependency Information
Role
Dependency Information
Actor
Dependency Information
Workflow Architectures
WorkflowData-FlowDependencies
α1
α2
α3
α4 α5 α6 α7 α8
(Data Flow Dependency Model)
α9
α13
α10
α14
α11
α15
α12
α16
α17
α9
α13
α10
α14
α11
α15
α12
α16
α17
α18
γ1 : Applicant Information
γ2 : Decision Result
γ3 : Checkup Done
γ4 : Checkup Results
γ5 : Review Results
α1
α2
α3
α4
α5
α6
α7
α8
α17
α18
α19
α21
α22
α20
αI
αF
υd = {γ1}; υu = {∅}
α9
α13
α10
α14
α11
α15
α12
α16
α23
α24
α25
α26
α27
α28
α29
α30
υd = {∅}; υu = {γ1}
υd = {γ2}; υu = {∅}
υd = {∅}; υu = {γ1 , γ2}
υd = {γ4}; υu = {γ1, γ3}
υd = {γ3}; υu = {γ4}
υd = {γ5}; υu = {γ4}
υd = {∅}; υu = {γ5}
υd = {∅}; υu = {γ1}
υd = {∅}; υu = {γ1, γ2}
υd = {∅}; υu = {γ1}
υd = {γ3}; υu = {γ1}
υd = {γ3}; υu = {γ4}
υd = {γ4}; υu = {γ1 , γ3}
υd = {γ3}; υu = {γ4}υd = {γ3}; υu = {γ4}
υd = {γ4}; υu = {γ1, γ3}υd = {γ4}; υu = {γ1, γ3}
(Data Definition-Use Model)
α4 α6
α9 α10 α11 α12
α8
XPDL,WorkflowPackageMeta-Model
Process(W. Process)
Package[Business
Process Diagram (BPD)]
Type Declaration
ApplicationParticipant
Pool
Lane
Data Field
ExternalPackage
0..1
0..10..1
0..1
0..1
0..1
*
*
*
*
*
*
**
MessageFlow
Association
Artifact
sourcetarget
sourcetarget
Activity
targetsource
sourcesource
targettarget
Resource Repository or Organizational
Model
System and environmental data
W. Relevant Data
Data Object
Group
Annotation
XPDL,WorkflowProcessMeta-ModelProcess
(W. Process)Type
Declaration
Application
ActivitySet(Embedded Sub-Process)
Data Field(Property)
Participant Activity Transition (Sequence Flow)
tofrom
performer
performer
usesuses
uses
uses
Pool Lane BlockActivityTask/Tool
SubFlow
Event
Route
Reference
Resource Repository or Organizational
ModelSystem and
environmental data
W. Relevant Data
Gateway
Activities Conversations
Events
Gateways
Conversation Diagram
None: Untyped events, indicate start point, state changes or final states.
Message: Receiving and sending messages.
Timer: Cyclic timer events, points in time, time spans or timeouts.
Error: Catching or throwing named errors.
Cancel: Reacting to cancelled transactions or triggering cancellation.
Compensation: Handling or triggering compensation.
Conditional: Reacting to changed business conditions or integrating business rules.
Signal: Signalling across differ-ent processes. A signal thrown can be caught multiple times.
Multiple: Catching one out of a set of events. Throwing all events defined
Link: Off-page connectors. Two corresponding link events equal a sequence flow.
Terminate: Triggering the immediate termination of a process.
Escalation: Escalating to an higher level of responsibility.
Parallel Multiple: Catching all out of a set of parallel events.
Start EndIntermediate
Catc
hing
Thro
win
g
Even
t Su
b-Pr
oces
sIn
terr
upti
ng
Stan
dard
Even
t Su
b-Pr
oces
sN
on-I
nter
rupt
ing
Boun
dary
In
terr
upti
ng
Boun
dary
Non
-In
terr
upti
ng
Sequence Flow
defines the execution order of activities.
Conditional Flow
has a condition assigned that defines whether or not the flow is used.
Default Flow
is the default branchto be chosen if all other conditions evaluate to false.
Task
A Task is a unit of work, the job to be performed. When marked with a symbol it indicates a Sub-Process, an activity that can be refined.
TransactionA Transaction is a set of activities that logically belong together; it might follow a specified transaction protocol.
Event Sub-Process
An Event Sub-Process is placed into a Process or Sub-Process. It is activated when its start event gets triggered and can interrupt the higher level process context or run in parallel (non-interrupting) depending on the start event.
Call ActivityA Call Activity is a wrapper for a globally defined Task or Process reused in the current Process. A call to a Process is marked with a symbol.
Task TypesTypes specify the nature of the action to be performed:
Send Task
Receive Task
User Task
Manual Task
Business Rule Task
Service Task
Script Task
Markers indicate execution behavior of activities:
Activity Markers
Sub-Process Marker
Loop Marker
Parallel MI Marker
Sequential MI Marker
~ Ad Hoc Marker
Compensation Marker
A Conversation defines a set of logically related message exchanges.When marked with a symbol it indicates a Sub-Conversation, a compound conversation element.
A Conversation Link connects Conversations and Participants.
Inclusive GatewayWhen splitting, one or more branches are activated. All active incoming branches must complete before merging.
Complex GatewayComplex merging and branching behavior that is not captured by other gateways.
Exclusive Event-based Gateway (instantiate)Each occurrence of a subsequent event starts a new process instance.
Parallel Event-based Gateway (instantiate)The occurrence of all subsequent events starts a new process instance.
Multi Instance Pool (Black Box)
Conversation
Sub-Conversation
Pool (Black Box)
Participant B
The order of message exchanges can be specified by combining message flow and sequence flow.
Pool
Pool
Pools (Participants) and Lanes represent responsibilities for activities in a process. A pool or a lane can be an organization, a role, or a system. Lanes subdivide pools or other lanes hierarchically.
Lane Task
Lane Task
Pool
Message Flow symbolizes information flow across organizational boundaries. Message flow can be attached to pools, activities, or message events. The Message Flow can be decorated with an envelope depicting the content of the message.
Data
Out-put
Data Store
A Data Object represents information flowing through the process, such as business documents, e-mails, or letters.
A Data Store is a place where the process can read or write data, e.g., a database or a filing cabinet. It persists beyond the lifetime of the process instance.
A Data Input is an external input for the entire process.A kind of input parameter.
A Collection Data Object represents a collection of information, e.g., a list of order items.
Collaboration Diagram
Pool
(W
hite
Box
)
Lane
Lane
Choreographies
Choreography Diagram
A Choreography Task represents an Interaction (Message Exchange) between two Participants.
ChoreographyTask
Participant A
Participant B
A Sub-Choreography contains a refined choreography with several Interactions.
Multiple Participants Marker
Swimlanes
BPMN 2.0 - Business Process Model and Notation
Collection
Ad-hoc Subprocess
Task
Task
~
MessageStart Event
Message Flow
Data Object
CollapsedSubprocess
Event-basedGateway
Escalation End Event
TimerIntermediate
Event
Receive Task
Attached Intermediate Timer Event
Link Intermediate
Event
Manual Task
EndEvent
Data Store
Link Intermediate
Event
Parallel Multiple
Intermediate Event
Text Annotation
Group
Multi Instance Task (Parallel)
MessageEnd Event
Send Task
ParallelGateway
ExclusiveGateway
Attached Intermediate Error Event
SignalEnd Event
Call Activity
Subprocess
Event Subprocess
ConditionalStart Event
Error End Event
StartEvent
EndEvent
Looped Subprocess
condition
http://bpmb.de/poster
Participant A
Participant CParticipant B
Choreography Task
Participant A
Participant B
Choreography Task
Participant A
Participant C
InitiatingMessage (decorator)
ResponseMessage (decorator)
Choreography Task
Participant B
Participant A
When splitting, it routes the sequence flow to exactly one of the outgoing branches. When merging, it awaits one incoming branch to complete before triggering the outgoing flow.
Exclusive Gateway
Is always followed by catching events or receive tasks. Sequence flow is routed to the subsequent event/task which happens first.
Event-based Gateway
When used to split the sequence flow, all outgoing branches are activated simultaneously. When merging parallel branches it waits for all incoming branches to complete before triggering the outgoing flow.
Parallel Gateway
A Call Conversation is a wrapper for a globally defined Conversation or Sub-Conversation. A call to a Sub-conversation is marked with a symbol.
Sub-Choreography
Participant A
Participant CParticipant B
Call Choreography
Participant A
Participant B
A Call Choreography is a wrapper for a globally defined Choreography Task or Sub-Choreography. A call to a Sub-Choreography is marked with a symbol.
Input
A Data Output is data result of the entire process. A kind of output parameter.
A Data Association is used to associate data elements to Activities, Processes and Global Tasks.
denotes a set of Participants of the same kind.
Message
a decorator depicting the content of the message. It can only be attached to Choreography Tasks.
Pool
(Bla
ck
Box) Pool (Black Box)
Pool (Black Box)
© 2011
Stan
dard
BUSINESS PROCESS MODELS BY BPMN
WorkflowManagementArchitectures
Workflow Client
Transform reference
interact via
Workflow Modeling System
Programs & Scripts
External product/data
Software component System control data
Application Services
WfM Engine
use use
Workflow Enactment
Service
(Supervisor)
Administration & Control
Organization/ Role Model
Workflow Control & Rel.
Data Data
interpreted by
Workflow Process Model
Web Services
Workitem List
(Workflow Users)
Databases
reference
Workflow Applications Arena
Workflow Enactment
Arena
Web Service Engine
ATraditionalServer-ClientWorkflowArchitecture
DBS
DB
WFS
DBC
PEC
RTC
RTC
PEC
APP
APP
WFS
DBC
PEC
RTC
RTC
PEC
APP
APP
WFS
DBC
PEC
RTC
RTC
PEC
APP
APP
DBS: Database Server WFS: Workflow Server DBC: Database Client RTC: Runtime Client PEC: Prog. Exec. Client
APerspective-OrientedWorkflowArchitecture
History Server
Policy Server
Notify Server
Synchronization Server
Application Server
Control Server
Data Server
Kernel
Workflow Applications
User’s Workspace
AnActivity-OrientedDistributedWorkflowArchitecture
Monitoring Service
Sche.
AM1
Task1
Sche.
AM3
Task3
Sche.
AM2
Task2
Sche.
AM4
Task4
Sche.
AM5
Task5
A1
A4 A2
A3
A5
Diagnosis Workflow ICN Model
A1
A4 A2
A3
A5
Diagnosis Workflow ICN Model
Node1
Node2
Node4
Node3
Activity3 Thread
Node Manager2
Process Thread
Activity2 Thread
Instance Table
Process Table
Queue
Node Manager3
Process Thread
Activity2 Thread
Instance Table
Process Table
Queue
Node Manager4
Process Thread
Activity2 Thread
Instance Table
Process Table
Queue
Node Manager1
Process Thread
Activity2 Thread
Instance Table
Process Table
Queue
TheWorkflowArchitecturalOperationConcept
Modeling Manager
Workcase Process
1
2
3
Workflow Procedure
Monitoring Manager
Actor Process Actor
Process Actor
Process Actor
Process Activity Thread
Worklist Worklist Worklist Worklist Dispatcher Thread
6 5
4
7
• Load Balancing Mechanism: Process Migration
• Concurrent Control(Synchronization) Mechanism • Thread Scheduling(Enactment Control) Mechanism
• Role Scheduling Mechanism • Actor Scheduling Mechanism
• Coupling Mechanism
• Physical Connections: Peer-to-Peer • Logical Connections: Client-Server Paradigm
Ataglance,theFutureoftheCTRL
�
2/� MHI CH�
�
�
�
�
0 (�0 )�0 � 0 �
B � MHI C�0 � 0 �
� MHI C�
�
0 (�
0 )� 0 �
0 �
B � MHI C�
0 � 0 �
0 (�
0 )� 0 �0 �
B � MHI C�
0 � 0 �
� MHI C�
�
/� MHI C�
��
�H�
-& �
& �
� MHI CH�
�
/� MHI CH�
��
�H� B � MHI CH�
�����
�2GE HH L G �
- 0 - - �2 -/ 0 �
�
� �
�
�
�
�
0 (�0 )�0 � 0 �
0 � 0 �
HIG I � �
�
0 (�
0 )� 0 �
0 �
/ D G C �
0 � 0 �
0 (�
0 )� 0 �
0 �
/ D G C �
0 � 0 �
HIG I � ��
- 2 2� �
��
�H�
-& �
& �
HIG I � ��
- 2 2� �
��
�H�/ D G C �
/ D G C �
�
�
E B�0 ILEGA� D BMH H�8 I A D A � A �:A D A � �:I D � AMPI E �
W � ST� 305 �3 MA D A�0 D MDI �5 MA MDI �:I NMDI �
W � �R 398 �3 MA D A�9A IN A�8 D �
eb USX�: :/�:IBMP A� � �:A D A�
R dcUSX�: : 8 : 5 :�
FI � H �/ D C DI�8 I A 0P A� I EB IP�6 AGA M�: MAG �
2GE HH L G �- � �
2GE HH L G �-0 0 �
�-0 �
aeR NfOW�T�P a�
3 MA D A : DA MDBD �154�20 0�
BPM1 BPM2 BPM3 BPM4
BPM-Supported Enterprise Social Network Intelligence Frameworks
Social Nets Affiliation Nets Diffusion Nets
The Eventual Goal of the Frameworks: � BPM-supported Enterprise Business Process Intelligence & Analytics Solution Suite � The Biggest ROI with real competitive advantages
Discove.. Analyze. Visualize. Build.
Stochastic ICNsA
C U
U’
initial cost analysis
(p9, p10, p11)
I
C’
P
G
D
T
Z
book request (p1, p2)
initiate utility analysis (p5, p6, p7, p8)
terminate utility analysis (p4)
terminate cost analysis
(p3)
R
acquisition inquisition (p12, p13)
book purchased (p14, p15)
rejected (p16, p17)
book cataloged (p10, p11)
classification reviewed (p9)
book in circulation (p1, p2, p3)
final disposition recorded (p16, p17)
A
C U
U’
I
C’z
P
G
D
T
Z
R
0.25
0.15
0.25
0.35
0.20
0.80
p1
p2 p5
p6
p7
p8 1.00 p4
1.00
p3
0.25
0.55
0.20
p9
p11
p10
0.50
0.50
p12
p13
0.40
0.60
p16
p17
0.30
0.70
p14
p15
0.35
0.65
p10
p11
1.00
0.50
0.50
p16
p17
0.33
0.33
0.34
p1
p3
p2
p9
0.20 0.80
0.50
0.50
0.90
0.10
Q & A
Thank You Very Much!