Information Technology Reference
In-Depth Information
Table 1. Activities of the candidature process
Activity
Role
Temporal constraints
Preconditions
Frequency
Priority
1. register in the appli-
cation
Applicant
From January, 20
th
to
March, 25
th
Valid INE number
Web connection
1 time
Mandatory
2. consult a choice
Applicant
From January, 20
th
to
March, 25
th
Connected state
indifferent
Optional
3. add a choice
Applicant
From January, 20
th
to
March, 25
th
Connected state
From 1 to 36
choice
Mandatory
4. validate a choice
Applicant
From January, 20
th
to
March, 25
th
Connected state
From 1 to 36
choice
Mandatory
5. order a choice
Applicant
From January, 20
th
to
March, 25
th
Connected state
1 time for a choice Mandatory
6. delate a choice
Applicant
From January, 20
th
to
March, 25
th
Connected state
1 time for a choice Optional
7. print choice file
Applicant
From January, 20
th
to
March, 25
th
Connected state
1 time for a choice Mandatory
8. prepare and send fold-
ers
Applicant
Until April, 4
th
Selective choice
1 time for a choice Mandatory
9. check reception of
folders
Applicant
From May, 8
th
to 12
th
Connected state
indifferent
Mandatory
10. send missing pieces
Applicant
Institutions precise
dates
1 time for an in-
complete folder
Mandatory
11. change choices order
Applicant
From March, 25
th
to
May, 31
st
Connected state
indifferent
Optional
12. reply to a poposition
Applicant
3 phases of 72 hours
from June, 3
rd
to 19
th
Connected state
1 time for a phase Mandatory
step we must identify scenarios of activities. The
scenario must contain actions composing the activ-
ity, events and interactions. Control flows order
the elements of the activity in time. Sometimes
they do not correspond to a simple succession.
Then they must be associated with workflow pat-
terns which are defined by White (2004). These
workflow patterns when identified in a process
must be assigned to a gateway (see figure 5) and
described by a sentence in the main scenario.
Below, we present an example of two scenarios
constructed from information collected from the
academic web application. Figure 8 corresponds to
an activity executed by the applicant. Extensions
in a scenario correspond to possible exceptions.
After identifying activities and their sce-
narios, the previous two steps must be repeated
to identify sub-processes and their scenarios and
detailed processes and their scenarios (Figure 9).
Then the steps must be repeated until defining
the complete structure of the studied global pro-
cess. The structure of every global process may
be saved in a functional tree containing all the
components of the process (not shown here, but
combined with intentional data in the next step in
an object diagram represented by the Figure 11).
The scenarios should be modeled with a business
process modeling language. BPMN models in-
corporate the behavioral, interactional, functional
and organizational views. The different forms
of data restructured in this phase (the scenarios,
the functional tree, and the roles) must be used
to construct business process models. Figure 10
depicts the BPMN diagram of the detailed process
described by the Figure 9 and an activity of this
process described by the Figure 8.
Search WWH ::
Custom Search