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

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

21.01.2014 Views

38 CHAPTER 3. STATE OF THE ART modeling language for execution languages, such as BPEL4WS [58] and BPML [11]. The BPMN specification provides a mapping between the graphics of the notation and the constructs of those formal languages. BPMN intends to provide businesses with the capability of understanding their internal business procedures in graphical notations and give organizations the ability to communicate these procedures in a standard manner. BPMN is initiated as a standard process modeling language for conventional business, B2B and services process modeling. Hence BPMN has the capabilities of handling B2B business process concepts, such as public and private processes and choreograhies, as well as advanced modeling concepts, such as exception handling and transaction compensation in addition to the traditional business process notations [12]. Private business processes are those internal processes to a organization and they are traditional business processes or workflows. Public processes are also called abstract processes or interface processes according to the BPMI terminology. They represents the interactions between a private business process and another process or participant. Choreographies represents collaboration processes. A collaboration process depicts a sequence of activities that represent the messages being sent between the entries involved. According to the BPMI terminology, the modeling constructs are the elements with corresponding notations. The main elements of BPMN Version 1.0 [12] are event, task, process/sub-process, sequence flow, message flow, pool, lanes, data object, fork (ANDsplit), join (AND-join), decision/branching point (OR-split), merging (OR-join), looping, etc. We refer those elements to the perspectives in the BPM systems paradigm. A sub-process is a compound activity included within a process. The collapsed/expanded sub-process can hide and show the details of the sub-process. Hereby, the structural perspective can be represented by BPMN through such a mechanism. Respectively, task, process/sub-process are elements for the operational/functional perspective. Tasks and processes are controlled through event, sequence flow, fork, join, decision, merging and looping. Resource can be represented by data object. Organizations are usually represented by lanes in the pool. The data transaction is specified through message flow together with data object. The details of the BPMN specifications from BPMI can refer Appendix A. The names and the notations of the BPMN elements used in this section are from the standard proposal. When a modeling tool implements a certain modeling language (e.g. BPMN), the names and the notations might be slightly changed to adjust the tool implementation. For example, task, process/subprocess are implemented as "Logical Process" in an enterprise modeling tool Metis [183]. 3.1.6 Categorizing the modeling constructs of process modeling languages The investigation of existing process modeling languages has shown the diversity of modeling constructs. The modeling constructs of the process modeling languages is categorized in Table 3.1 according to the six process perspectives defined in the paradigm of BPM systems.

3.2. SEMANTIC INTEROPERABILITY AND PROCESS ONTOLOGIES 39 3.2 Semantic Interoperability and Process Ontologies Semantic heterogeneity baffles the effective management of distributed knowledge, which relates to semantic interoperability under an extensive system exchange and integration situation. Semantic interoperability issue has been studied in different domains and applications such as schema and data integration of databases, meta-data interoperation among distributed digital libraries , agent-based Web services discovery and composition, enterprise integrations and so on. Research on semantic interoperability generally is categorized as: mapping and intermediary approach. The mapping approach can be sub-classified into point-to-point mapping and global mapping. Pointto-point mapping is the particular mapping built for two participating systems. Such a mapping can maximally preserve the original semantics of each system, but it is costly when a large number of systems need to interchange with each other or new unexpected system needs to participate. Global mapping attempts to construct mappings between participant systems and a global schema [24] [17] [66]. This requires to build a global schema which is designed to be dependent of particular schemas or applications [152]. The problem of this solution is not portable and does not adapt well to the addition of new systems. The intermediary approach is to make use of intermediary mechanisms to coordinate heterogeneous semantics. Domain-specific knowledge, mapping knowledge, or rules are modeled by the intermediary mechanisms such as mediators, agents, ontologies, etc. [132]. Generally, this approach uses a machine understandable definition of concepts and relationships between concepts so that there is a shared common understanding within a community. The knowledge or rules are domain specific, but independent of particular schemas and applications. However, one needs additional tools to actually capture and represent the knowledge (i.e., specifications and mappings) needed in order to resolve semantic conflicts. Semantic Web technology and some research results of ontology have initiated larger amount of research interests on the intermediary approach, especially applied in the applications of collaborative business (such as interoperation of enterprise processes, Web services, etc.). We apply the intermediary approach in this research work. Hence, the top-level ontology — process ontology for business process representation, and domain ontology for a given business domain are used as the intermediaries in our approach. The process ontology is used to reconcile the heterogeneous semantics of process modeling constructs (i.e. meta-model semantics) existing in different process modeling languages. It indicates that a process ontology should include a set of meta-concepts that are able to describe the semantics of process models. In this section we survey a number of process ontologies having different motivations: BWW ontology [204] for building a modeling fundamental of information systems, MIT process handbook [99] for organizing process knowledge, TOVE ontologies [31] for creating a set of ontologies to support enterpise modeling, PSL [120] for serving as an interlingua of all types of manufacturing processes, PIF [85] for exchanging business process models across different formats and schemas, OWL-S [198] for establishing a descriptive language of Web services, WSMO [209] for describing various aspects related to Semantic Web services, POP* [139] for providing a mapping mechanism between enterprise models and modeling tools, and UEML2 [140] for creating an intermediate language of various existing modeling languages. The process perspectives of the paradigm of BPM systems

38 CHAPTER 3. STATE OF THE ART<br />

modeling language <strong>for</strong> execution languages, such as BPEL4WS [58] and BPML [11].<br />

The BPMN specification provides a mapping between the graphics <strong>of</strong> the notation and<br />

the constructs <strong>of</strong> those <strong>for</strong>mal languages. BPMN intends to provide businesses with<br />

the capability <strong>of</strong> understanding their internal business procedures in graphical notations<br />

and give organizations the ability to communicate these procedures in a standard<br />

manner.<br />

BPMN is initiated as a standard process modeling language <strong>for</strong> conventional business,<br />

B2B and services process modeling. Hence BPMN has the capabilities <strong>of</strong> handling<br />

B2B business process concepts, such as public and private processes and choreograhies,<br />

as well as advanced modeling concepts, such as exception handling and transaction compensation<br />

in addition to the traditional business process notations [12]. Private business<br />

processes are those internal processes to a organization and they are traditional business<br />

processes or workflows. Public processes are also called abstract processes or interface<br />

processes according to the BPMI terminology. They represents the interactions between<br />

a private business process and another process or participant. Choreographies represents<br />

collaboration processes. A collaboration process depicts a sequence <strong>of</strong> activities<br />

that represent the messages being sent between the entries involved.<br />

According to the BPMI terminology, the modeling constructs are the elements with<br />

corresponding notations. The main elements <strong>of</strong> BPMN Version 1.0 [12] are event, task,<br />

process/sub-process, sequence flow, message flow, pool, lanes, data object, <strong>for</strong>k (ANDsplit),<br />

join (AND-join), decision/branching point (OR-split), merging (OR-join), looping,<br />

etc. We refer those elements to the perspectives in the BPM systems paradigm. A<br />

sub-process is a compound activity included within a process. The collapsed/expanded<br />

sub-process can hide and show the details <strong>of</strong> the sub-process. Hereby, the structural perspective<br />

can be represented by BPMN through such a mechanism. Respectively, task,<br />

process/sub-process are elements <strong>for</strong> the operational/functional perspective. Tasks and<br />

processes are controlled through event, sequence flow, <strong>for</strong>k, join, decision, merging and<br />

looping. Resource can be represented by data object. Organizations are usually represented<br />

by lanes in the pool. The data transaction is specified through message flow<br />

together with data object.<br />

The details <strong>of</strong> the BPMN specifications from BPMI can refer Appendix A. The<br />

names and the notations <strong>of</strong> the BPMN elements used in this section are from the<br />

standard proposal. When a modeling tool implements a certain modeling language<br />

(e.g. BPMN), the names and the notations might be slightly changed to adjust the tool<br />

implementation. For example, task, process/subprocess are implemented as "Logical<br />

<strong>Process</strong>" in an enterprise modeling tool Metis [183].<br />

3.1.6 Categorizing the modeling constructs <strong>of</strong> process modeling languages<br />

The investigation <strong>of</strong> existing process modeling languages has shown the diversity <strong>of</strong><br />

modeling constructs. The modeling constructs <strong>of</strong> the process modeling languages is categorized<br />

in Table 3.1 according to the six process perspectives defined in the paradigm<br />

<strong>of</strong> BPM systems.

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

Saved successfully!

Ooh no, something went wrong!