Java Reference
In-Depth Information
<?xml
version
#
"1.0" encoding
#
"UTF-8"?>
<
WORKFLOW
ID
#
"StudentTest" NAME
#
"Student Test" VERSION
#
"1.1" CATEGORY
#
"TEST">
<DESCRIPTION>
This is a simple process used for test purposes.
It describes the process of assigning an exercise to a student.
</DESCRIPTION>
<!— Activities —>
<
ACTIVITY
ID
#
"define" NAME
#
"Define exercise">
<IMPLEMENTATION KIND
#
"NO" PERFORMER
#
"professor"/>
</ACTIVITY>
<
ACTIVITY
ID
#
"perform" NAME
#
"Perform exercise">
<IMPLEMENTATION KIND
#
"NO" PERFORMER
#
"student"/>
</ACTIVITY
>
<
ACTIVITY
ID
#
"correct" NAME
#
"Correct exercise">
<IMPLEMENTATION KIND
#
"NO" PERFORMER
#
"professor"/>
</ACTIVITY>
<
ACTIVITY
ID
#
"feedback" NAME
#
"See results">
<IMPLEMENTATION KIND
#
"NO" PERFORMER
#
"student"/>
</ACTIVITY>
<!— Transitions —>
<
TRANSITION
FROM
#
"define" TO
#
"perform"/>
<
TRANSITION
FROM
#
"perform" TO
#
"correct"/>
<
TRANSITION
FROM
#
"correct" TO
#
"feedback"/>
<!— Participants —>
<
PARTICIPANT
ID
#
"professor" NAME
#
"Professor"/>
<
PARTICIPANT
ID
#
"student" NAME
#
"Student"/>
</WORKFLOW>
Figure 21.7
XML process description example
represented by the
<TRANSITION>
tags. The process involves two par-
ticipants identified by the tag
<PARTICIPANT>
.
The activity attributes are the ID and the name, in addition there is a sub-
tag - implementation - that tells whether the activity is implemented by
some IT application. It specifies the role participant that should perform the
activity.
The transitions specify the source and destination activities, identified by
their ID. The participants identify the roles and are described by means of a
unique ID and a name. The workflow relevant data are characterized by an
ID, a meaningful name and the type.
21.4.2
Design
This component consists of a set of classes to represent a process model
described using XPDL, which was presented above. The main concern we
must address is the simplicity that enables seamless access to the process
models by the other components of the WfMS.
