Design and Verification of Information Systems (DVIS) lectures 3-4

1. Design and Verification of Information Systems (DVIS) lectures 3-4 Two problems with current WFMS Five perspectives on WFMS Reference nets - nets with reference semantics Introduction to Renew Enacting Inter-organizational Workflows Using Nets in Nets

2. Five Perspectives on WFMS • 1. The control flow (routing) perspective • 2. The resource (organization) perspective • 3. The data (information) perspective • 4. The task (function) perspective • 5. The operation (application) perspective

3. Five Perspectives on WFMS, ctnd. • WFMS should support the five perspectives • the build-time part of the WFMS allows for the specification of five perspectives • the run-time part of WFMS takes care of the actual enactment • the fact that the control flow perspective dominates all other perspectives restricts the reuse of parts of the workflow definition and limits the extensibility of the WFMS with additional perspectives

4. Five Perspectives on WFMS, ctnd. • Since all perspectives are intertwined, it is impossible to exchange cases, resources, data, tasks, or operations between workflow enactment services in different organizations • E-commerce - exchange information between business partners and suppliers and inside of companies • Inter-OWS - workflows crossing boundaries between corporations in an E-commerce setting • Intra-OWS - workflows involving multiple business units within one corporation

5. Five Perspectives on WFMS, ctnd. • Commercial WFMS use a centralized enactment service both the build-time and run-time - problems with IOWS

6. Reference Nets - “nets in nets paradigm” • Definition of Reference Nets - Petri Nets where the tokens can be references to other Petri nets • Reference Nets are used for specifying and enacting IOWF; they model mobility of a business object like a workflow instance, a resource, a data element, a task, or an operation • object-nets - token of system net correspond to marked PNs on a lower level, called object-nets • since object-nets actually reside in the system-net, we call this the value semantics approach

7. Reference Nets - “nets in nets paradigm” • Reference nets use a different approach - the object-nets do not actually reside in the system net, but tokens are references to object-nets; this means that multiple tokens can reference the same object-net - this is called reference semantics

8. Two Problems with Current WFMS • 1. Unclear mixture of perspectives in the current generation of WFMS making workflow specifications incomplete and difficult to interpret. • 2. Absence of tools to describe and enact the mobility of business objects required for IOWF.

9. Introduction to Reference Nets and Renew • Renew - The Reference Net Workshop • Renew - the only tool supporting execution of any kind of nets in nets, and it uses reference semantics • all five perspectives on WFMS are modeled in terms of reference nets • an instance of each perspective corresponds to one marked object-net • the system-net joins all perspectives and can be seen as the enactment service of WFMS

10. Introduction to Reference Nets and Renew, ctnd. • Since every aspect is modeled in a separate object-net, it is not necessary to intertwine all aspects • the system-net is generic, i.e., independent of actual workflows and organization • one can think of the system-net as an architectural model and the object-nets as the actual content - the workflow designer only creates object-nets