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

F.2. INTEGRATION APPLICATION BASED ON SEMANTIC ANNOTATION 205
the shops are local shops, it usually takes less time to ship the products so that it
positively_satisfies Reduce Order Shipment Time.
After annotating the low level activity elements, the goal contributions can be calculated
to the upper level activities. Taking the example of the composite activity
"Check items", we have annotated its component activities with hard goals and soft
goals. "Check imported items" negatively satisfies Reduce Verification Costs and
"check consignment items" positively satisfies Reduce Verification Costs, so the effects
are counteracted for the composite activity "check items" if we apply the simple
contribution calculation rules. The hard goals "Sourced Products are Verified",
"Procurement Notification to Supplier" and "Product Quantity is Approved" which are
annotated to "check imported items", "check consignment items" and "check items from
local suppliers" are simply passed to "check items". Applying the same rules, the goals
related to the whole process model are specified through the goal annotation.
F.2 Integration Application Based On Semantic Annotation
An integration application in the exemplar studies is to integrate delivery processes of
Enterprise A and B. We deploy this application based on semantic annotation results
of process models.
The following steps have been undertaken for the integration application:
1. Running QRule-Activity-achievesHardGoal for RE2.4 to find process model
fragments achieving the integration goals.
2. Using ontology as semantic mediator, SWRL queries and rules are executed for
RE4 to find semantic relationships between Activity, Artifact and Actor-role
in those model fragments resulted from step 1.
3. Based on semantic relationships between model fragments, listing some possible
integration paths.
4. Applying SWRL queries and rules QRule-Activity-hasSucceedingActivities
and QRule-Activity-hasPrecedingActivities for RE1 and QRule-ActivityhasPrecedingActivities-hasSubActivity
for RE3.2 to rearrange the sequence
of integrating process model fragments.
5. Checking the results from step 4 with activity sequences in the SCOR domain
ontology.
6. Adjusting the sequence and hierarchy of integrating activities according to the
integration context.
7. Build output-input flow by checking Input and Output of activities through
running QRule-Activity-Input-mappedto and QRule-Activity-Outputmappedto
for RE2.2. The step can be used to find the missing activities and
also re-arrange the sequence of activities based on the output-input flow.