Information Technology Reference
In-Depth Information
transformation of the text segments into a short form. The second step includes the
generalization of the paraphrases towards a specified level of abstraction (aggregation
of tasks). A second generalization can be done in order to subsume related activities
to process fragments (aggregation of activities).
3.6 Identification of Process Specifications
The identification of process elements is appropriate in the paraphrasing step. In this
step the unit of analysis is reduced to its key essence. The key essence of a To-do is
the performed task or activity, and is captured in the code by a meaningful noun and a
verb [12]. The labels serve as labels of the tasks and activities in the process model.
Reference points important for process view aggregation are listed in the following.
We suggest adding reference points as variables to the cases.
Variables specify the
properties associated with the case.
•
Hints to data transfer (data_input and data_output) or events (e.g. eMail, Mail,
PhoneCall) between two or more process participants (connection).
E.g. To-do of
the AdministrativeCooperator: “Mail lecturing contract to lecturer”. To-do of a
Lecturer: “Receipt of the lecturing contract in my post office box”.
•
Hints to group tasks and activities (participation).
E.g. To-do of the Lecturers and
the TeachingCoordinators: “Participation in coordination meeting”.
Hints to decisions.
E.g. To-do of a Lecturer: “Either I contact the Administrative-
Cooperator if I want to topic the lecture hall X or I contact the Secretary if I want
to topic the lab.”
•
•
Hints to delegation. It can be assumed that the To-do's are performed by the proc-
ess member who listed the To-do's. Otherwise a hint to another person is given.
E.g. To-do of a ModuleCoordinator: “A lecturer of our lecturer team topics a lec-
ture hall for all of us”.
Hints to tools used. It might be the case that process participants rather mention the
particular tool name (e.g. Fronter) than the general term (e.g. learning platform).
E.g. To-do of a Lecturer: “Then I enter the grades of the students into iswi.”
•
•
Hints to reoccurring activities.
E.g. To-do of a Lecturer: “Reoccurring task: con-
duction of the units”.
•
Time notes. We assume that To-do list already reflect a sequential order of the To-
do's. The first To-do mentioned in the list is the first To-do that is performed by the
person in the process under investigation. Explicitly mentioned time notes may be
vague but support the designer to sequentially order tasks and activities when sub-
suming all tasks and activities of the various process members.
E.g. To-do of a Lec-
turer: “At the day of the unit I print the attendance list.”, or “Before the semester
starts I plan the course”.
•
Name of the agent. The name of the process member is captured as well.
Furthermore, process members may mention comments that refer to activities per-
formed by other process members or to the general process.
E.g. Mentioned by a
Lecturer: “The AdministrativeCooperator topics the lecture hall in the system”.
Such information might be important for the designer when he or she composes the
