Embed Size (px)
DESCRIPTION
Slides from a webinar that I presented on June 9, 2010, as part of the Active Endpoints BPM Summer Camp series.
Citation preview
DON’T PANIC
Replay and slides will be available
Agenda
What’s all this BPMN stuff anyway? How much do we really need to
know? What advanced bits might come in
handy?
Recap from February: BPMN Is Simple...
Activity
Gateway
Event
Data
Source: http://bpmb.de/poster
The BPMN 2.0 Problem
More than 100 elements Unlikely to be fully understood by
most experts, much less users Unlikely to be fully supported by most
vendors Has led to rejection of BPMN in favor
of “simpler” modeling paradigms
The BPMN 2.0 Solution
Not everyone needs to learn everything
Group BPMN elements into sets used by different personasBusiness userBusiness analystArchitect/developer
Each level adds more detail to model
SIMPLE
sequenceFlowTask (none)subProcess(embed)exclusiveGatewayparallelGatewaystartEvent (none)endEvent (none)
DESCRIPTIVE
PoolLanemessageFlowuserTaskserviceTaskRe-Usable subProcessdataObjectdataInputdataOutputtextAnnotationAssociationdataAssociationdataStoremessageStartEventmessageEndEventtimerStartEventterminateEndEvent
DODAF
Plus 29 elements
COMPLETE
Plus 50 elements
BPMN 2.0 Subclasses:Early Version
Source: Workflow Management Coalition’s “Update on BPMN Release 2.0”
BPMN 2.0 Subclasses: Recent Version
DescriptiveVisible elements for high-level modelsUsed by business analysts
AnalyticAll of Descriptive plus elements for
DoDAF enterprise architecture models Commonexecutable
All of analytic plus elements for executable models
Descriptive Subclass
participant (pool) laneSet sequenceFlow (unconditional) messageFlow exclusiveGateway parallelGateway task (None) userTask serviceTask subProcess (expanded) subProcess (collapsed) callActivity
dataObject textAnnotation association/dataAssociation dataStoreReference startEvent (None) endEvent (None) messageStartEvent messageEndEvent timerStartEvent terminateEndEvent documentation group
Pool
Lane
MessageFlow
Message Start Event
Message End Event
UserTask
DataObject
Sub Process(Collapsed)
ServiceTask
DataAssociation
Call Activity(Collapsed)
TextAnnotation Association
Source: Workflow Management Coalition’s “Update on BPMN Release 2.0”
Descriptive Subclass Example
Source: Workflow Management Coalition’s “Update on BPMN Release 2.0”
DataStore
Descriptive Subclass Example
Analytic Subclass
sequenceFlow (conditional)
sequenceFlow (default)
sendTask receiveTask Looping Activity MultiInstance Activity exclusiveGateway inclusiveGateway
eventBasedGateway signalStartEvent signalEndEvent errorEndEvent message
Plus: Intermediate events
Analytic Subclass: Intermediate Events Catching message Throwing message Boundary message Non-interrupting
Boundary message Catching timer Boundary timer Non-interrupting
Boundary timer Boundary error Non-interrupting
Boundary escalation
Throwing escalation escalationEndEvent Catching signal Throwing signal Boundary signal Non-interrupting
Boundary signal condtionalStartEvent Catching conditional Boundary conditional Non-interrupting
Boundary conditional
The Analyst’s Dilemma
Descriptive is a manageable subset Analytic is too much, except for
serious process experts Some of the event concepts in
analytic subset are required for analysis and modeling
Oh Yeah...
...we left the business users out
What Do Business Users Really Need?
Smaller subset of elements (?)Depends on user skills/aptitude
Comprehension of BPMN without necessarily being able to model:Work with analysts to capture
processesReview and approve models, with a
cheat sheet or generous annotation
