Semantic Annotation for Process Models: - Department of Computer ...
Semantic Annotation for Process Models: - Department of Computer ...
Semantic Annotation for Process Models: - Department of Computer ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Appendix F<br />
Analysis <strong>of</strong> the <strong>Annotation</strong> and<br />
the Integration Application in<br />
Exemplar Studies<br />
In this chapter, we provide analysis details <strong>of</strong> exemplar studies. Section F.1 describes<br />
how SCOR ontology is annotated to PM A , PM B1 and PM B2 with our semantic annotation<br />
approach. Based on the annotation results, an analysis <strong>of</strong> the integration<br />
application <strong>for</strong> the applicability <strong>of</strong> the semantic annotation approach is depicted in<br />
section F.2.<br />
F.1 <strong>Semantic</strong> <strong>Annotation</strong> with SCOR ontology<br />
Parts <strong>of</strong> the annotation results <strong>of</strong> the exemplar studies are displayed in Table 7.3, Table<br />
7.4 and Table 7.5. Ten representive Activities out <strong>of</strong> 33 instances in PM A are listed in<br />
Table 7.4. For the model annotation, same_as is applied when the Activity instance<br />
undertakes the same task as the SCOR process element. "Transportation planning" in<br />
PM A does actually accomplish the carriers selection and shipments rating (D1.7), no<br />
more and no less work than that. When one Activity instance specifies the way <strong>of</strong><br />
doing <strong>of</strong> a certain SCOR process element, kind_<strong>of</strong> can be used. "Credit control" is<br />
one way <strong>of</strong> managing the deliver capital assets (ED.5) in the context <strong>of</strong> PM A . Usually<br />
the granularity <strong>of</strong> the Activity instances is smaller than the SCOR level 3 process<br />
element, i.e. they are decomposed parts <strong>of</strong> SCOR process elements. Those Activities<br />
are there<strong>for</strong>e phase_<strong>of</strong> the reference ontology concepts. Both "Client RFQ processing"<br />
and "Client quotation processing" are two phases <strong>of</strong> D1.1 <strong>Process</strong> Inquiry<br />
and Quote. As the goal annotation results, they are not obvious to see the inherent<br />
link between the Activity instance and the goal ontology in the table. The automatic<br />
goal annotation algorithm deduces the optional goal ontology concepts which<br />
have the features relevant to the model fragment <strong>of</strong> the Activity instance. But it does<br />
not mean that all the deduced goals are fulfilled by the Activity, the options are returned<br />
with the weights. Generally the higher weight indicates that the returned goal<br />
is more relevant to the Activity instance. Besides, the annotator will make the choices<br />
based on the context <strong>of</strong> process models and manual annotation is also necessary in<br />
203