Page 246 -

8 The Design Environment 239
A typical credit card application process begins when a customer submits an appli-
cation with a proposed amount of credit. Next, a credit clerk verifies the status of
the application. If the application is incomplete (e.g., the customer’s credit history is
missing), the clerk requests additional information and waits until the customer pro-
vides this information. However, if no information is received within a given period
of time (e.g., 3 days), a request is sent again. This is done at most 3 times, then the
process terminates assuming the customer is no longer interested in the applica-
tion. If a complete application is received on time, the clerk verifies the customer’s
income and credit history. Different checks need to be performed depending on the
amount of credit (e.g., more stringent requirements may apply to amounts greater
than $1,000). After this, the application is passed on to a manager who decides
whether to accept or reject it. In either case, the customer is notified of the decision
and the process finishes.

Exercise 6. Extend this workflow by allowing the possibility to cancel the appli-
cation process at any time after a complete application is received but before the
manager decides on the application.
Exercise 7. Apply the following change to the credit card application process:When
an approved application is notified, the customer is asked to choose any extra fea-
tures they may want to add. These include customized card, reward program, and
secondary cardholder(s).

Chapter Notes

In this chapter, we used the YAWL Editor version 2.0. The tool, along with the other
components of the YAWL System, can be downloaded from the YAWL project Web-
3
site hosted by SourceForge. Here the reader can find documentation on various
aspects of the Editor and consult the mailing lists and forums to learn the latest
news about the system.
The YAWL user manual is the complete reference documentation for the YAWL
user. It contains information on how to install YAWL and dedicated guides for the
Editor and the YAWL runtime environment. In addition, it includes the tutorial Get-
ting started with YAWL, which provides a brief overview for the reader interested in
experimenting with the Editor. On the other hand, the reader interested in advanced
data aspects can consult the section How to manipulate data in YAWL of this manual.
The development aspects behind the YAWL System are illustrated in the Techni-
cal manual. Finally, software bug reports and feature requests can be made through
the Google code project. 4

3 sourceforge.net/projects/yawl
4 code.google.com/p/yawl