Semantic Annotation for Process Models: - Department of Computer ...
Semantic Annotation for Process Models: - Department of Computer ...
Semantic Annotation for Process Models: - Department of Computer ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
2.2. MODELING BASIS 15<br />
meta-model <strong>of</strong> the modeling language. Thus, we conclude that model semantics are<br />
interpreted according to the system’s context and the modeling language applied in the<br />
solution.<br />
2.2.3 Ontology-driven and domain-specific<br />
Modeling at the conceptual level trends to be seemingly independent <strong>of</strong> the computer<br />
world in the development <strong>of</strong> modeling methodologies. Researchers turn to philosophy<br />
and linguistics to try to find the inherent principles in the concepts <strong>of</strong> real world domains.<br />
And the boundary between the conceptual modeling and knowledge modeling<br />
becomes gradually fuzzy.<br />
For example, Ontology-Driven Conceptual Modeling draws fundamental notions<br />
from <strong>for</strong>mal ontology and establishes a minimal top-level ontology to drive conceptual<br />
modeling [47]. Thesaurus Conceptual Model uses the Knowledge/Data Model<br />
(KDM) [137] that incorporates an object-oriented view <strong>of</strong> data, together with knowledge<br />
regarding its usage [68]. Ontologies are used <strong>for</strong> the development <strong>of</strong> conceptual<br />
schemas <strong>of</strong> in<strong>for</strong>mation systems by pruning irrelevant concepts in the ontologies [18].<br />
On the other hand, domain model framework and meta-model make reuse and<br />
flexibility <strong>of</strong> models possible. A s<strong>of</strong>tware system can never be finished, new and changed<br />
domain concepts will always be appearing, <strong>for</strong>cing continuous rebuilding, testing and redeployment<br />
<strong>of</strong> systems [8]. The main idea <strong>of</strong> the approach proposed in [8] is the removal<br />
<strong>of</strong> domain concepts from concrete s<strong>of</strong>tware and database models, into standardized<br />
vocabularies and libraries <strong>of</strong> domain concept models. Re-engineering s<strong>of</strong>tware and<br />
database is done using a generic reference object model (ROM) system architecture<br />
in [8]. Reference models are used in [160] to combine "<strong>for</strong>mal driven" and "content<br />
driven" approaches in a new way to develop in<strong>for</strong>mation systems. The <strong>for</strong>mal driven<br />
approach aims to develop and implementing a technical correct running system. The<br />
goal <strong>of</strong> the content driven approach is developing and implementing an organizational<br />
correct running system. Goals <strong>of</strong> content and technology are concerned in reference<br />
models, which are regarded as "blue prints" <strong>for</strong> business engineering and can be used<br />
to model and optimize business processes. Domain-specific methods implemented with<br />
metaCASE technology [67] use meta-modeling languages to develop a domain metamodel<br />
mapped to combinations <strong>of</strong> components in order to generate a product.<br />
All these approaches address the process <strong>of</strong> modeling, and the ideas can be analogically<br />
applied on the results <strong>of</strong> modeling — models. In an ontology-based semantic<br />
annotation method, the utility <strong>of</strong> an ontology and domain knowledge is applied after<br />
modeling. The additional semantic treatment is still necessary <strong>for</strong> the exchange<br />
or reuse <strong>of</strong> models across different organizations, because a modeling process usually<br />
is not centralized and local ontologies and local domain/reference models applied in<br />
the modeling are still various from different organizations. In this work, consensual<br />
ontologies and domain reference models are there<strong>for</strong>e needed to be determined in an<br />
annotation phase based on the requirements on interoperability and applications.