Lecture 5: DCR Graphs I Flashcards
The Three Dimensions of Business Processes
- Complexity
- Predictability
- Repetitiveness
Complexity
What is the degree of difficulty incollaboration, decision-making and collaboration?
- Lowcomplexity: exchanging a personal email message, handling a travel request
- Highcomplexity: Payment of unemployment benefits, medical treatments
Predictability
How easy it is to predict how the process will execute, and the possible outcomes:
- Lowpredictability: Exchanging personal email messages. Payment of unemploymentbenefits
- Highpredictability: Handling travel requests, manufacturing product lines
Repetitiveness
How often do you run this process?
- Lowfrequency: Disaster mitigation
- Highfrequency Manufacturing product lines
BPM Systems
BPM systems support collaboration, coordination and decision-making in business processes
- Groupware systems support human collaboration and co-decisions
- Workflow management systems explicitly control ordering, coordination and execution of activitieswith little human intervention
Flexibility & Support
- Flexibility: To which degree theusers can take local decisions about how to execute the process
- Support: To which degree the system makes centralized decisions about how to execute the process
BPMS and Decision-making
INSERT TABLE
Trends in BPM
Imperative Modelling
- Traditional, repetitive processes
- E.g. flowcharts, activity diagrams
Declarative Modelling
-Knowledge-intensive, highly-variableprocesses· -E.g. constraints, DCR Graphs
Understanding a process
- What are the roles?
- What are the activities?
- What are the start and goal activities?
- What resources are necessary for activities?
- How are activities ordered?
Scenarios
- Positive:We should support this!
- Neutral: Wemight support this (partial trace)
- Negative:We want to avoid this!
Constraints in DCR Graphs
Much richer than the simple “precedence sequence flow” connector in imperative languages
Types of constraints
Conditions
Responses
Dynamic Inclusion
Dynamic Exclusion
Milestones
Conditions
Denote a simple precedence constraint. A => B expresses that B cannot be donebefore A is done.
Responses
Denotes anobligation constraint. A => B expresses that the execution of Awill result in execution of B being obligatory(must be done).
Will turn B into the pending state (!)
Dynamic Exclusions
Used to establish negation/inhibition. A =>% B expresses that the execution of A inhibits theexecution of B.
Dynamic Inclusions
Denotes anobligation constraint. A =>+ ifexecuting A makes B available for execution