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

7.4. ANNOTATION OF PROCESS MODELS WITH PRO-SEAT 115
Figure 7.14: SCOR soft goal Improve Supplier Delivery Performance in Protégé-OWL
editor
Table 7.2: Mapping the EEML and BPMN meta-model elements to the GPO concepts
GPO concepts EEML elements in METIS 5.2.2 BPMN elements in METIS 5.2.2
Activity Task Logical Process
Actor-role Organization, Person Swimlane including Horizontal Swimlane
and Vertical Swimlane
Artifact
Resource, Role, Information Object, Data Object, property ’Data’ in Event
Software Tool, Manual Tool, Material
Tool, Location
Input Input Port Input
Output Output Port Output
WorkflowPattern
Combination of Flow, Milestone and
Decision Point
Combination of Event (including
Start Event, Intermediate Event, End
Event), Sequence Flow, Gateway
Precondition Milestone, Decision Point Event (including Start Event, Intermediate
Event), Gateway
Postcondition Milestone, Decision Point Event (including End Event, Intermediate
Event), Gateway
Exception Decision Point Event (when event type is error) together
with Sequence Flow
ities with the properties has_precedingActivities and has_succedingActivities
of Activity. Moreover, mapping the same meta-model element to two different GPO
concepts is not supported, because it produces the identical instances of different OWL
Classes ( e.g. a same milestone in the EEML model will be the instance of Precondition
and the instance of Postcondition at the same time). This violates the OWL
modeling principle that instances of different OWL Classes should be unique. A solution
of the implementation of Pro-SEAT is to modify the GPO ontology by inserting
an abstract concept Condition as the super-Class of Precondition and Postcondition.
The mapping between the modeling elements and Precondition/Postcondition is
therefore transferred to the mapping between the modeling elements and Condition.
The distinction of Precondition and Postcondition ( i.e. which model element is the
instance of Precondition and which model element is the instance of Postcondition) can
be specified in the model annotation phase through the properties has_Precondition
and has_Postcondition of an Activity.