Page 74 -

2 The Language: Rationale and Fundamentals 61
organise
visa(s)

lodge archive
travel paperwork
request book check
accomm-
costings
odation
estimate bookings
cost complete
book
travel
Fig. 2.22 YAWL control-flow example: 2

schedule
written practical practical issue file
test test licence application
test

organise confirm
car insurance
Fig. 2.23 YAWL control-flow example: 3

collect evaluate report
responses findings
results
Fig. 2.24 YAWL control-flow example: 4

OR-joins associated with the bookings complete and archive paperwork tasks ensure
that they do not commence until all active preceding tasks have been completed.
Figure 2.23 depicts a driving license examination process. First there is a written
test task. If the applicant passes this, they are then able to progress to the schedule
practical test task. If not, the application is deemed to be unsuccessful and it is
filed and the test process for the applicant concludes. The schedule practical test
task is composite in form and consists of a subprocess with two tasks: organize
car and confirm insurance. Once it is complete, the practical test task can occur.
Depending on its outcome, if it is successful, the issue license task is triggered, and
if it is unsuccessful, the applicant can attempt a subsequent practical test (on up to
two subsequent occasions, after this the application is deemed unsuccessful and is
finalized) and the thread of execution is routed back to the schedule practical test
task again. After the license is issued, the file application task completes the process.
Figure 2.24 provides a simple example of the use of the multiple instance task. It
shows a medical review process consisting of three tasks. First the collect responses
task gathers the details of the medical cases being investigated from patients. Then
a distinct evaluate results task executes concurrently for each patient case being
examined. The number of these tasks depends on the data provided by the collect