252 Data Interaction Support There are two facilities for transferring data

252 data interaction support there are two facilities

This preview shows page 77 - 80 out of 664 pages.

2.5.2 Data Interaction Support There are two facilities for transferring data elements to and from tasks in YAWL. Simple parameters can be used to transfer the value of a data element between a net
Image of page 77
2 The Language: Rationale and Fundamentals 65 Fig. 2.26 Variable specification and parameter passing in YAWL variable and a given task. The task can be of any form: atomic, composite, multiple instance, or composite multiple instance; however, in all cases, the parameter oper- ates on every instance of the task to which it applies. Each task may have multiple simple parameters associated with it. There are two types of simple parameter: Input parameters involve the application of an XQuery function to a net variable in the block surrounding a task and placing the resultant value in a nominated task variable. Output parameters involve the application of an XQuery function to a task vari- able and placing the resultant value in a nominated net variable in the surrounding block. Figure 2.27 illustrates the use of simple parameters in the Driving Test Process shown earlier. In this example, they are used to map data values between the net variable ApplicantStatus and the task variable iApplicantStatus . In each case, the parameter is specified in the form of an XQuery expression. The usage descriptor for the iApplicantStatus task variable is Input & Output, denoting that the value of the variable is passed in at task commencement and passed out at its conclusion. The situation is essentially the same whether the parameter is transferring a data element to/from an atomic task or a composite task, except that the target variable is identified as both a task variable in the composite task and as a net variable in the associated decomposition. Figure 2.28 illustrates the situation where the task being targeted is composite in form and has an associated decomposition specified in the form of a subprocess. In this situation, the net variable ApplicantStatus is passed to the variable iApplicantStatus that appears as both a task variable for the Schedule Practical Test task and is also a net variable in the Practical Test Scheduling subpro-
Image of page 78
66 N. Russell and A. ter Hofstede Fig. 2.27 Data passing using simple parameters in YAWL cess. Both variables share the same name: iApplicantStatus . The XQuery expression that identifies the parameter mapping is also shown in this figure. Multiple instance parameters operate on multiple instance tasks. Unlike simple parameters that result in the application of the XQuery to every instance of the task with which they are associated, multiple instance parameters are used to partition net variables containing record-based data across individual instances of a multiple instance task or to coalesce variables in instances of a given multiple instance task into a nominated net variable. Only one set of multiple instance parameters can be associated with a specific multiple instance task. The multiple instance parameter set is comprised of four distinct components as illustrated in Fig. 2.29.
Image of page 79
Image of page 80

You've reached the end of your free preview.

Want to read all 664 pages?

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

Stuck? We have tutors online 24/7 who can help you get unstuck.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes