Information Technology Reference
In-Depth Information
Future
Material Price
must be
activated
Start Event
Activate Future
Material Price
Conjunction
Activate and Change
Material Price
Activate Future
Material Price
Dominating Element
Material Price
Batch input
has been
created for
price change
Change in
Material Price
Main Activity
Change Material Price
V
Revaluation
Document
has been
created
Material price
has been
changed
End Event
Create Revaluation
Document
End Event
Change Material Price
Fig. 1. Potential sources of process names for model Change in Material Price
to the business object material price , in respective connection with the actions
activate and change , which therefore could be used as central elements of the
overall name. Another option would be to look at the names of the end events
since they refer to what is actually accomplished by executing the process. Hence,
the creation of the revaluation document may represent another naming option.
This discussion aims to emphasize that there are many options, and they are
dicult to rank without prior domain knowledge. In the following part, we aim
to systematically identify different strategies for choosing a name for a process.
2.2 Classification of Naming Strategies
We collected an extensive set of process models from practice in order to iden-
tify naming strategies. We used three different model collections, aiming in this
respect for broad diversity in the underlying domains. First, we had access to
the SAP Reference Model [7, pp. 145-164], a collection containing 604 EPCs
organized in 29 functional branches of an enterprise such as sales, accounting
and other areas, with a total number of 2,433 activity labels. Second, we have
used a model collection from a European utility vehicle manufacturer consisting
of one main procurement process with nine sub-processes and altogether 115
activity labels. Third, we inspected a model collection containing the incident
management process from an international IT service provider . The process is
captured as an EPC on three abstraction layers, containing 88 sub-processes and
293 activity labels.
We analyzed the names in the model sets by first identifying action and business
objects in the name of the process model. Then, we used a self-developed tool that
identified linguistic relations between the name parts and the activity and event
Search WWH ::




Custom Search