Information Technology Reference
In-Depth Information
that is more specific than a given word - a name proposal is constructed using
the dominating element and the according holonym or hypernym. In case of the
Logical Conjunction, the subordinate elements are simply connected using the
logical operators and or or .
Another technique that builds on the identified dominating elements is Label
Repository . This technique uses the activities of other process models to build up
a label repository. If a dominating element was identified with the Dominating
Element Extraction technique, such a label repository can be consulted to find
a corresponding element which is likely to be connected with the dominating
element. As an example, consider the SAP process model Capacity Planning
containing the dominating business object Capacity . As this business object in
isolation is not a very comprehensive process name, the repository can be con-
sulted. By browsing the repository for labels containing Capacity , we obtain,
amongst others, the process name Capacity Planning which perfectly matches
the original process name.
The Event Extraction technique derives potentially useful names from start
and end events. Therefore, start and end events are inspected on their merit
to provide information about the model content. That decision is based on the
usage of particular signal terms given in the event label. For instance, it is not
very probable that the term was in the start event Asset was found indicates
what is to be performed in the process; rather, it represents a state that was
required for triggering the first activity. By contrast, the term is to be in the
start event Asset is to be created captures the necessity for the execution of a
subsequent action within the process of consideration. Hence, (1) the identified
start events are reduced to those where the signal term indicates that the event
actually contains information about what is going to happen and (2) the end
events are restricted to those that signal what has happened in the process.
Based on an extensive classification of these terms from the investigated process
model collections, this decision can be made in an automated fashion.
Referring to the main activity approach as briefly mentioned in Section 2.2,
we further introduce the Main Activity Extraction technique. The objective of
this technique is to automatically decide whether a considered activity repre-
sents a main activity for the given process model or not. In order to be able
to make this decision for an individual activity, it is necessary to automatically
derive the context of the process and subsequently decide about the role of the
activity. This approach utilizes the insight of our analysis that approximately
85% of the main activities are found either at the beginning or at the end of the
process. Accordingly, the main activity extraction presumes the existence of a
main activity in the first or last position and selects the according activity labels
as process name proposals.
In order to obtain an all-encompassing approach, we combined all techniques.
To some extent the order of executing the techniques is fixed as some depend
on the on the input of other, like the Lexical Conjunction . However, techniques
such as Main Activity Extraction can be executed independently from other
techniques and can be executed at any time.
 
Search WWH ::




Custom Search