Describe various ways in which repetitive tasks or subprocessed can be

Describe various ways in which repetitive tasks or

This preview shows page 9 - 11 out of 12 pages.

Describe various ways in which repetitive tasks or subprocessed can be specified in a process Examples: structured loop, arbitrary cycles, recursion Multiple instance patterns Characterize situations where multiple concurrent instances of a task or subprocess execute simultaneously and may need to be synchronized upon completion Examples: static join, cancelling partial join Concurrency patterns Reflect situations where restrictions are imposed on the extent of concurrent execution within a process Examples: sequence, interleaved parallel routing pattern, interleaved routing, critical section, milestone Trigger patterns Identify constructs that allow the execution in a process past a specified point to be made contingent on the receipt of a signal from the operating environment Examples: persistent trigger, transient trigger Cancelation and completion patterns Categorize the various cancellation scenarios that may arise in a business process Examples: cancel task, cancel case, cancel multiple instance task, complete MI task, cancel region Termination patterns Address the issue of when the execution of a process can be considered to be finished Examples: implicit termination, explicit termination Cancellation region Reset nets are able to explicitly depict notions of cancelation within a process definition Reset nets are made up of the same constructs as standard Petri nets with the addition of a rest arc. Like normal input arcs, reset arcs connect places to transitions but operate in a different way
Image of page 9
Identify main YAWL split and join operators, model each of these in terms of Petri Nets. Split operators AND-split diverges thread of control in a given branch into one of several possible outgoing branches on the basis of an execution decision made at runtime XOR-split routes thread of control in a given branch into one of several possible outgoing branches on the basis of an execution decision made at runtime OR-split routes thread of control in given branch into one, several, or all outgoing branches on the basis of an execution decision made at runtime Thread-split diverges the thread of control in a given branch into multiple concurrent execution threads in the same branch Join operators AND-join XOR-join OR-join Thread-join Resource patterns and resourcing Life cycle of work item (states and actions) Work items comes into existence in the created state. This indicates that the preconditions required for its enablement have been satisfied and is capable of being executed States Created Work item has come into existence but no resources are yet aware of it Offered to a single person Opportunity to undertake work item rests with a single resource and that the resource has not yet committed to undertaking it Offered to multiple resources Several resources have been offered the opportunity to undertake the work item but none have decided to do so yet. Once one of them does commit to executing the item, the offers received by other resources are withdrawn Allocated
Image of page 10
Image of page 11

You've reached the end of your free preview.

Want to read all 12 pages?

  • Summer '19
  • Business, Management, Business process modeling, Petri net, Petri Nets

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture