21.01.2014 Views

Semantic Annotation for Process Models: - Department of Computer ...

Semantic Annotation for Process Models: - Department of Computer ...

Semantic Annotation for Process Models: - Department of Computer ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

136 CHAPTER 8. QUALITY EVALUATION OF THE METHOD<br />

concepts. For example, the meronym is represented by "phase_<strong>of</strong>" <strong>for</strong> Activity,<br />

"part_<strong>of</strong>" <strong>for</strong> Artifact and "member_<strong>of</strong>" <strong>for</strong>Actor-role.<br />

5. Tool appropriateness. PSAM is defined using a <strong>for</strong>mal syntax and modeled in<br />

OWL. OWL is XML-syntactic compilable and it can be parsed by available commercial<br />

or non-pr<strong>of</strong>it parsers. The semantics <strong>of</strong> GPO and PSAM are also <strong>for</strong>mally<br />

defined according to the OWL semantic definitions. The GPO concepts are modeled<br />

as owl:Class and the relations are modeled as owl:ObjectProperty and<br />

owl:DatatypeProperty. For our work, OWL DL is the basis <strong>of</strong> the annotation<br />

models. OWL DL was designed to support the existing Description Logic business<br />

segment and has desirable computational properties <strong>for</strong> reasoning systems [195].<br />

The Protégé-OWL API is integrated in the annotation tool so that the syntax<br />

and the semantics <strong>of</strong> GPO and PSAM can be interpreted by the tool.<br />

6. Organizational appropriateness. Due to the fair comprehensibility appropriateness<br />

and the application goals <strong>of</strong> this work, GPO and PSAM are theoretically<br />

easy to understand <strong>for</strong> audiences from different enterprise units. However, further<br />

empirical evidence is required to establish this claim.<br />

8.3.2 Quality analysis <strong>of</strong> the annotation model instances<br />

A specific annotation model is an instance <strong>of</strong> the PSAM model that is trans<strong>for</strong>med<br />

from the original process models and annotated with ontological concepts. The quality<br />

<strong>of</strong> GPO and PSAM will impact the quality <strong>of</strong> the PSAM models. The evaluation<br />

<strong>of</strong> the PSAM models concludes how the model quality relates to the usability <strong>of</strong> the<br />

annotation results.<br />

Physical Quality<br />

We first look at how the knowledge <strong>of</strong> the domain has been externalized by the annotation<br />

models. Such a goal could be achieved through the means <strong>of</strong> domain appropriateness,<br />

participant language knowledge appropriateness and knowledge externalizability<br />

appropriateness. As we have discussed in the quality analysis <strong>of</strong> those appropriateness<br />

above, the PSAM models can present most in<strong>for</strong>mation about the process and<br />

functional perspective. The EEML and BPMN models have presented the logistics<br />

processing comprehensively due to their expressiveness. Based on the meta-model annotation<br />

results, the original models are trans<strong>for</strong>med into the PSAM models. Ideally,<br />

the trans<strong>for</strong>mation should keep exactly the same in<strong>for</strong>mation as the original models. It<br />

is obvious that more one-to-one mappings in the meta-model annotation, more knowledge<br />

represented in the modeling elements can be preserved after the trans<strong>for</strong>mation.<br />

In the exemplar studies, five one-to-one mappings are in the annotation <strong>of</strong> BPMN and<br />

three are in the annotation <strong>of</strong> EEML. In EEML, different resources are specified and<br />

they all could be mapped to the GPO concepts Artifact and Actor-role respectively.<br />

Thus, the PSAM models <strong>of</strong> PM A should have better physical quality than the ones <strong>of</strong><br />

PM B . Fortunately, those specific resources are not much applied in the original EEML<br />

models PM B . That is, not much domain knowledge is lost because <strong>of</strong> the meta-model

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!