Lecture 6: Process Constraint Mapping Flashcards
1
Q
Summary: Generality
A
Imperative models:
- Fast to outline, show some (few) ofthe possible flows of a process AS IS
- Describing a general solution goesat expenses of readability of the models, and might introduce errors in themodel
Declarative models:
- Show all the possible flows. Relationslimit the possible flows to what is allowed
- Are thought to be general.Imperative flows can be specified (but not advised to do so)
2
Q
Milestone
A
-Ensure that follow-up actions areperformed
- If an event A is a milestone for an event B, written A => B ,
then: whenever A is pending and a required response, B is not enabled
3
Q
Nesting
A
- More like syntactic sugar, itdecreases the number of connections (arrows) without affecting its semantics
- Whatever relation applied to anesting activity, applies to all nested activities
- Basically, allows for easierreadability
4
Q
Subprocesses
A
- A graph is a process
- A sub-process is a complex activityin the model that has underlying behavior which is instantiated when thesub-process is started and closed when the sub-process ends
- Sub-processes can be:
- Single-instance: only one instance of the sub-processwill be active at any time, or
- Multi-instance:multiple instances of the sub-processes
5
Q
Traces
A
- A trace denotes a run (sequences ofactivites executed) in a business process
- An accepting trace has achieved abusiness goal, otherwise is non-accepting
- Activities can be executed anynumber of times until disabled
- A trace is accepting, when there areno pending activities to be executed
6
Q
Process Constraint Mapping
A
A way to map the business process AS IS. Contains a combination of scenario-based testing, and language-based testing