<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Validating Process Refinement with Ontologies</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Yuan</forename><surname>Ren</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">University of Aberdeen</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Gerd</forename><surname>Groener</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">University of Koblenz-Landau</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Jens</forename><surname>Lemcke</surname></persName>
							<affiliation key="aff2">
								<orgName type="department">SAP AG</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Tirdad</forename><surname>Rahmani</surname></persName>
							<affiliation key="aff2">
								<orgName type="department">SAP AG</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Andreas</forename><surname>Friesen</surname></persName>
							<affiliation key="aff2">
								<orgName type="department">SAP AG</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Yuting</forename><surname>Zhao</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">University of Aberdeen</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Jeff</forename><forename type="middle">Z</forename><surname>Pan</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">University of Aberdeen</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Steffen</forename><surname>Staab</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">University of Koblenz-Landau</orgName>
							</affiliation>
						</author>
						<title level="a" type="main">Validating Process Refinement with Ontologies</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">F2B40BFC7BAFF1E9E31FFA1DA1675378</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-23T23:20+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>A crucial task in process management is the validation of process refinements. A process refinement is a process description in a more fine-grained representation. The refinement is either with respect to an abstract model or with respect to component's principle behaviour model. We define process refinement based on the execution set semantics. Predecessor and successor relations of the activities are described in an ontology in which the refinement is represented and validated by concept satisfiability checking.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>The refinement of processes is a common task in process development. A generic process describes the core functionality of an application. A refinement is a transformation of a process into a more specific process description which is developed for a more concrete application and based on more detailed process behaviour knowledge. A key question is whether a process refinement is valid, i.e. the refined process refers to the intended behaviour of the abstract process.</p><p>We distinguish between horizontal and vertical refinement. A horizontal refinement is a transformation from an abstract to a more specific model. A vertical refinement is a transformation from a principle behaviour model of a software component to a concrete process model of business. Once a refined process model describes a concrete application process, the relationship to the original generic process is not always obvious due to a number of possibly complex refinement steps. A refinement step includes customisation, extensions and compositions of processes. Therefore it is quite difficult to validate the refinement of a process with respect to an abstract process model.</p><p>The validation of a process refinement consists of checking model constraints like execution order constraints. Modelling constraints for the refined process has to cover the constraints of the generic process behaviour and also constraints which emerged during the refinement steps.</p><p>In this paper, we use execution set semantics to analyse process refinements. This set-based formalism accounts for a comparison of the process executions of different processes. The comparison of process execution sets is then reduced to the comparison of finite sets of predecessor and successor relations which is realized by subsumption checking. We further use ALC ontologies to model processes and process constraints, concerning the execution order conditions and binding of tasks. Finally the refinement checking is reduced to concept satisfiability checking.</p><p>In Section 2 we define the problem of process refinement with its graphical syntax, semantics and mathematical foundation. The modelling of processes with the corresponding execution constraints is demonstrated in Section 3, followed by the refinement validation.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Process Refinement</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1">Execution Set Semantics</head><p>A process is a non-simple directed graph without multiple edges between two vertices. A vertex is either an activity, a gateway, a start, or an end event. As a graphical process syntax, we use the business process modelling notation (BPMN)<ref type="foot" target="#foot_0">1</ref> due to its wide industry adoption. As an example, in Fig. <ref type="figure" target="#fig_6">1, (</ref> Thus in this work we consider only pairwise gateways to comply such convention. Also, we assume all the process models are valid by their own.</p><p>As a prerequisite to validating, we define the correctness of process refinement based on the execution set semantics <ref type="bibr" target="#b13">[14]</ref>. Briefly, the execution set of a process P , denoted by ES P , is made up of all the valid paths between the Start and the End in P . ES Abstract in Fig. <ref type="figure" target="#fig_6">1a</ref>   <ref type="figure" target="#fig_6">1c</ref>). Consequently, enumerating the execution set is infeasible.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2">Process Refinement</head><p>Fig. <ref type="figure" target="#fig_2">1</ref> shows a refinement horizontally from abstract to specific while vertically complying with the components' principle behaviour. In our example scenario, Fig. <ref type="figure" target="#fig_6">1a</ref> is drawn by a line of business manager to sketch a new hiring process. Fig. <ref type="figure" target="#fig_6">1b</ref> is drawn by a process architect who incrementally implements the sketched process. Fig. <ref type="figure" target="#fig_6">1c and d</ref> are the principle behaviour models of different components. The challenge is to verify whether the refinement is consistent with the more abstract horizontal and vertical processes. Correct horizontal refinement. We say that a process Q is a correct horizontal refinement of a process P if ES Q ⊆ ES P after the following transformations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>1.</head><p>Renaming. Replace all activities in each execution of ES Q by their originators (function hori()). Renaming the execution set As <ref type="figure" target="#fig_6">1b</ref> is a wrong horizontal refinement of Fig. <ref type="figure" target="#fig_6">1a</ref>. The cause is the potentially inverted order of AB by b 1 a 2 or b 2 a 2 in Fig. <ref type="figure" target="#fig_6">1b</ref> and that a 3 can be the last activity in Fig. <ref type="figure" target="#fig_6">1b</ref>, whereas A must always be followed by B in Fig. <ref type="figure" target="#fig_6">1a</ref>.</p><formula xml:id="formula_0">{[a 1 a 2 b 1 b 2 ], [a 1 b 1 b 2 a 2 ], [a 1 b 1 a 2 b 2 ], [a 1 a 3 ]} of</formula><formula xml:id="formula_1">{[AB]} ⊇ {[AB], [ABA], [ABAB], [A]}, Fig.</formula><p>Correct vertical refinement. We say that a process Q is a correct vertical refinement of a process P if ES Q ⊆ ES P after the following transformations. As</p><formula xml:id="formula_2">{[C], [D], [CC], [CD], [DC], [DD], . . .} ⊇ {[DC], [CD], [D]} and {[EF], [E]} ⊇ {[EF],</formula><p>[E]}, Fig. <ref type="figure" target="#fig_6">1b</ref> is a correct vertical refinement of both Component 1 and 2.</p><p>As enumerating the execution sets for validation is infeasible, our solution works with descriptions in ontology instead of using the execution sets themselves.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Validation with Ontologies</head><p>In this section, we present our solution of validating process refinement with ontologies in detail. We accomplish the transformations from the last section by reductions on the process diagram and execution sets, represent the refinement with an ontology, and validate the refinement by concept satisfiability checking.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Refinement reduction</head><p>Because the execution set may contain infinite number of executions, e.g. ES component1 , it's difficult to directly compare them. Therefore we reduce the subsumption between infinitely large execution sets into subsumption between finite predecessor and successor sets that are also obtained from the process diagram and show that the transformations on the execution sets are equivalent to transformations on the process diagrams or the predecessor and successor sets.</p><p>As we can see from ES Specif ic , the execution ordering relations between branches of a parallel gateway are implicit in the original process. In order to make them explicit, we first reduce a process diagram by the following operation:</p><p>A parallel gateway ([</p><formula xml:id="formula_3">B 1 |P 1 ], . . . , [B n |P n ]) is reduced to an exclusive gateway B 1 (P 1 , [B 2 |P 2 ], . . . , [B n |P n ]) , . . . , B n ([B 1 |P 1 ], . . . , [B n−1 |P n−1 ], P n )</formula><p>, where the notation [B|P ] represents a path with B the head and a subpath P the tail.</p><p>We repeatedly apply above operation until there's no parallel gateway in the diagram. Such an iteration will always terminate due to the finite size of the process. The resulting BPMN graph is called the Execution Diagram of P , denoted by ED P (see Fig. <ref type="figure" target="#fig_4">2</ref>). An activity a ∈ P may have multiple appearance in ED P . We use one more subscript j to differentiate them, i.e. a 2 1, a 2 2 w.r.t. a 2 . This transformation may increase the size of the process model exponentially, e.g. a pair of parallel gateways containing n branches of one activity will be transformed into a pair of exclusive gateway containing n! branches of n activity.</p><p>Obviously, given a process P , its execution set ES P is the set of all routes between Start and End in its execution diagram ED P after replacing duplicated activities with their original names. We further reduce ED P from a local perspective. For each activity appearance a in ED P , its Predecessor Set P S P (a) is the set of all the activities going to a through a direct link or a sequence containing only gateways. And its Successor Set SS P (a) is the set of all the activities going from a through a direct link or a sequence containing only gateways.</p><p>Obviously, according to the definition, for each x, y such that x ∈ P S P (a j ), y ∈ SS P (a j ), [x, a j , y] is a valid subpath of activities in ED P and thus [x, a, y] is a valid subpath of activities in P . Because the ED P is finite, P S P (a j ) and SS P (a j ) are also finite for any a j ∈ P . Follow our example, P S(a 31 ) = {a 11 } and SS(a 31 ) = {End}.</p><p>By obtaining these two sets for all the activities, the relation between two execution sets can be characterised by the following theorem: (2) For the ← direction the rhs holds and we demonstrate that ES Q ⊆ ES P follows. Consider an execution s ∈ ES Q , s = a 1 , . . . , a n . Activity a i−1 is predecessor of a i . For i = 2, . . . , n the following implication holds:</p><formula xml:id="formula_4">Theorem 1. ES Q ⊆ ES P iff ∀a ∈ Q, P S Q (a</formula><formula xml:id="formula_5">P S Q (a i ) ⊆ P S P (a i ) ⇒ [a i−1 , a i ] is a subpath of some X ∈ ES P . For i = 1, . . . , n − 1 the following im- plication holds: SS Q (a i ) ⊆ SS P (a i ) ⇒ [a i , a i+1</formula><p>] is a subpath of some Y ∈ ES P , therefore sequentially connect the subpathes [a 1 , . . . , a n ] ∈ ES P holds. Therefore, we reduce the process refinement w.r.t. execution set semantics into the subsumption checking of finite predecessor and successor sets. We then show that the transformation operations of execution sets can be equivalently performed on the original process diagrams and the predecessor and successor sets obtained from them:</p><p>-Reduction on the process diagrams has the same effect on the execution sets. That means, given a component model P and a process model Q, if we reduce Q into Q by removing all the activities that do not appear in P , and link their predecessors and successors directly, the resulting ES Q will be the same as the reduction of ES Q with respect to P . -Renaming can also be directly performed on the process diagram, i.e.</p><p>ES P [a → A] = ES P [a→A] . Thus, the renaming can be performed on the predecessor and successor sets as well, i.e. P S P (x)[a → A] = P S P [a→A] (x)</p><formula xml:id="formula_6">(SS P (x)[a → A] = SS P [a→A] (x)).</formula><p>-Decomposition can be done on the predecessor and successor sets as well.</p><p>Particularly, ES Q ⊆ ES P , where ES Q is ES Q after decomposition of all the sequential x grouped into a single x, iff ∀a = x, P S Q (a) ⊆ P S P (a), SS Q (a) ⊆ SS P (a) and ∀x, P S Q (x) ∪ {x} ⊆ P S P (x) and SS Q (x) ∪ {x} ⊆ SS P (x). This interprets the decomposition as, any x that should be grouped, can go not only from predecessors of x, but also another appearance of x, and can go not only to successors of x, but also another appearance of x.</p><p>Thus, above analysis implies that:</p><p>-For horizontal refinement, we can first obtain the predecessor and successor sets of activities, and then perform the Renaming and Decomposition on these sets, and then check the validity.</p><p>-For vertical refinement, we can first perform the Reduction on processes, then obtain the predecessor and successor sets and perform the Renaming on these sets, and finally check the validity.</p><p>In this paper, we perform Reduction directly on the process diagram and obtain the predecessor and successor sets from its execution diagram, then perform Renaming and Decomposition with ontologies and check the validity with reasoning.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2">Refinement representation</head><p>In this section we represent the predecessor and successor sets of activities with ontologies. In such ontologies, activities are represented by concepts. The predecessors and successors relations are described by two roles from and to, respectively. Composition of activities in horizontal refinement is described by role compose. Grounding of activities in vertical refinement is described by role groundedTo. The last two don't have essential logic difference in the problem of process refinement but have different semantics in the process model, so that we distinguish between them. Then, for a set S containing predecessors or successors, we define four operators for translations as follows: The effect of the above operators in refinement checking can be characterised by the following theorem:</p><formula xml:id="formula_7">Theorem 2. P S Q (a) ⊆ P S P (a) iff Disjoint(x|x ∈ P ∪ Q) infers that Pr f rom (P S P (a)) Ps f rom (P S Q (a)) is satisfi- able. SS Q (a) ⊆ SS P (a) iff Disjoint(x|x ∈ P ∪ Q) infers that Pr to (SS P (a)) Ps to (SS Q (a)) is satisfiable.</formula><p>For sake of a shorter presentation, we only prove the first part of the theorem. The proof for the second part is appropriate to the first part.</p><p>Proof. (1) We demonstrate → direction with a proof by contraposition. The disjointness of activities holds. Supposed the rhs is unsatisfiable, i.e. Pr f rom (P S P (a)) Ps f rom (P S Q (a)) is unsatisfiable. Obviously, both concept definitions on its own are satisfiable, since Pr f rom (P S P (a)) is just a definition with one all-quantified role followed by a union of (disjoint) concepts. The concept definition behind this expression is ∀f rom. x∈P S P (a) x which restricts the range of f rom to all concepts (activities) of P S P (a). Ps f rom (P S Q (a)) is a concept intersection which only consists of existential quantifiers and the same f rom role. This definition is also satisfiable. Therefore the unsatisfiability is caused by the intersection of both definitions. In Ps f rom (P S Q (a)) the same role f rom is used and the range is restricted by Pr f rom (P S P (a)). Therefore the contradiction is caused by one activity b ∈ P S Q (a) which is not in P S P (a), but this is a contradiction to the precondition P S Q (a) ⊆ P S P (a).</p><p>(2) For the ← direction we assume that the rhs Disjoint(x|x ∈ P ∪ Q) infers that Pr f rom (P S P (a)) Ps f rom (P S Q (a)) is satisfiable. For each activity b ∈ P S Q (a) we show that b is also in P S P (a): b ∈ P S Q (a) and Ps f rom (P S Q (a)) is satisfiable, the intersection contains the term ∃f rom.b. Since Pr f rom (P S P (a)) is satisfiable and is also the range restriction of f rom, it follows that b ∈ P S P (a). This theorem indicates that the refinement checking of processes can be reduced to the satisfiability checking of concepts in an ontology. In the following, we present the representation of horizontal refinement and vertical refinement.</p><p>Horizontal Refinement For conciseness of presentation, we always have a pre-refinement process and a post-refinement process and we refine one activity in each step (this activity may have multiple appearance after conversion to the execution diagram). We assume P the pre-refinement process, Q the post-refinement process and z the activity being refined. For each z j we define component z j ≡ ∃compose.z j . The simultaneous refinement of multiple activities can be done in a similar manner of single refinement. Then we construct an ontology O P →Q with following axioms:</p><p>1. for each activity a ∈ Q and hori(a) = z j , a ∃compose.z j These axioms represent the composition of activities with concept subsumptions, which realise Renaming in horizontal refinement. For example, b 11 ∃compose.B and a 31 ∃compose.A. 2. for each a ∈ Q and a is not refined from any z j a Pr f rom (P</p><formula xml:id="formula_8">S P (a))[z j → component z j ], a Pr to (SS P (a))[z j → componennt z j ],</formula><p>These axioms represent the predecessor and successor sets of all the unrefined activities in the pre-refinement process. Because in the post-refinement process, any activity refined from z j will be considered as a subconcept of component z j , we replace the appearance of each z j by corresponding component z j . For example, Start ∀to.component A.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">for each</head><formula xml:id="formula_9">z j ∈ P , component z j Pr f rom (P S P (z j ) ∪ {component z j })[z j → componennt z j ], component z j Pr to (SS P (z j ) ∪ {component z j })[z j → componennt z j ],</formula><p>These axioms represent the predecessor and successor sets of all the refined activities in the pre-refinement process. Due to the mechanism of Decomposing, we add the corresponding component z j to their predecessor and successor sets, and replace the z j with component z j for the same reason as before. These axioms represent the uniqueness of all the sibling activities refined from the same z j . For example, Disjoint(a 11 , a 21 , a 22 , a 23 , a 31 ). 6. Disjoint( all the activity in P , and all the component z j ).</p><p>This axiom represents the uniqueness of all the activities before refinement. For example, Disjoint(Start, End, A, B, component A, component B).</p><p>With above axioms, ontology O P →Q is a representation of the horizontal refinement from P to Q by describing the predecessor and successor sets of corresponding activities with axioms.</p><p>Vertical Refinement Similar as horizontal refinement, assume we have principle behaviour model P and a concrete process model Q, which is reduced w.r.t P to eliminate ungrounded activities. Any activity in Q can be grounded to some activity in P . Thus, after reduction, ∀a ∈ P, ∃b ∈ Q that b is grounded to a, and vice versa. Therefore for each x j ∈ P , we define grounded x j ≡ ∃groundedT o.x j .Then we construct an ontology O P →Q with following axioms:</p><p>1. for each activity a ∈ Q and vert(a) = x j , a ∃groundedT o.x j These axioms represent the grounding of activities by concept subsumptions, which realise the Renaming in vertical refinement. For example, a 11 ∃groundedT o.E, b 11 ∃groundedT o.F . 2. for each a ∈ P grounded a Pr f rom (P S P (a))[x j → grounded x j ], grounded a Pr to (SS P (a))[x j → grounded x j ], These axioms represent the predecessor and successor sets of all the activities in the pre-refinement process. Due the mechanism of Renaming we replace all the x j ∈ P by grounded x j . Because Decomposition is not needed in vertical refinement, we stick to the original predecessor and successor sets. These axioms become the constraints on the activities in Q. For example, grounded E ∀f rom.Start, grounded E ∀to.(grounded F End). 3. for each a ∈ Q, a Ps f rom (P S Q (a)) and a Ps to (SS Q (a)),</p><p>These axioms represent the predecessor and successor sets of all the activities in the post-refinement process. For example, a 11 ∃f rom.Start, a 11 ∃to.b 11 ∃to.End. Notice that the ungrounded activities such as a 31 have been removed from the process so that End becomes a directed successor of a 11 after reduction. 4. for each x j ∈ P , Disjoint(a|a ∈ Q and vert(a) = x j )</p><p>These axioms represent the uniqueness of all the sibling activities refined from the same x j . 5. Disjoint(all the grounded x j ).</p><p>This axiom represents the uniqueness of all the activities before refinement. For example, Disjoint(Start, End, grounded E, grounded F ).</p><p>Both the horizontal and vertical refinement can be represented in DL in a linear complexity. The language is ALC. It's worth to mention that f rom and to do not need to be inverse roles because the unsatisfiability of activities is caused by the contradiction of universal and existential restrictions.</p><p>With above axioms, ontology O P →Q is a representation of the refinement from P to Q by describing the predecessor and successor sets of corresponding activities with axioms.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.3">Concept satisfiability checking</head><p>Follow from the theorems and definitions presented before, the relation between the ontology O P →Q and the validity of the refinement from P to Q is characterised by the following theorem: Theorem 3. The route contains activity a in Q is invalid in the refinement from P to Q, iff O P →Q |= a ⊥.</p><p>Proof. For each a in Q the ontology O P →Q contains the axioms a Ps f rom (P S Q (a)) and a Ps to (SS Q (a)). The axioms a Pr f rom (P S Q (a)) and a Pr to (SS Q (a)) are derived from the axioms (item 1,2). Depending on the refinement either the axioms a ∃groundedT o.x j and grounded x j ≡ ∃groundedT o.x j or a ∃compose.z j and component z j ≡ ∃compose.z j are in the ontology. (1) For the → direction the lhs holds, we demonstrate that a is unsatisfiable. Since a is invalid either P S Q (a) ⊆ P S P (a) or SS Q (a) ⊆ SS P (a). From Theorem 3 it follows that either Pr f rom (P S P (a)) Ps f rom (P S Q (a)) or Pr to (SS P (a)) Ps to (SS Q (a)) is unsatisfiable and therefore a is unsatisfiable since a is subsumed. (2) The ← direction is proved by contraposition. Given a is unsatisfiable in O P →Q . Assumed a is valid in the refinement then P S Q (a) ⊆ P S P (a) and SS Q (a) ⊆ SS P (a) holds. From Theorem 3 the satisfiability of Pr to (SS P (a)), Pr f rom (P S P (a)), Ps f rom (P S Q (a)) and Ps to (SS Q (a)) follows which leads to a contradiction to the satisfiability of a.</p><p>This theorem has two implications:</p><p>1. The validity of a refinement can be checked by the satisfiability of all the name concepts in an ontology; 2. The activities represented by unsatisfiable concepts in the ontology are the source of the invalid refinement.</p><p>The complexity of such concept satisfiability checking is, according to the expressive power, ExpTime. we check the satisfiability of the concepts to validate the process refinement. Every unsatisfiable concept is either an invalid refinement or relating to an invalid refinement.</p><p>For While in the vertical refinement ontology, it's easy to infer that all the concepts are satisfiable. Therefore, the process model does comply to the principle behaviour models.</p><p>Helped by our analysis, the line of business manager and process architect remodel their processes (Fig. <ref type="figure" target="#fig_9">3</ref>). Now, the execution set of Fig. <ref type="figure" target="#fig_9">3a</ref> </p><formula xml:id="formula_10">is {[AB], [A]}. Renaming of Fig. 3b's execution set {[a 1 a 2 b 1 b 2 ], [a 1 a 3 ]} yields {[AABB], [AA]}.</formula><p>After decomposition, we conclude that Fig. <ref type="figure" target="#fig_9">3b</ref> correctly refines the process in Fig. <ref type="figure" target="#fig_9">3a</ref>  </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Related Works and Conclusion</head><p>Annotations to process models for service behaviour and interaction is described in <ref type="bibr" target="#b3">[4,</ref><ref type="bibr" target="#b11">12,</ref><ref type="bibr" target="#b10">11]</ref>. However, process refinement and model validation is not considered. Other models use mathematical formalisms to describe and compare concurrent system behaviour. In <ref type="bibr" target="#b2">[3]</ref> a process algebra is described in order to analyse equivalence. The analysed equivalence (trace equivalence) does not distinguish between deterministic and non-deterministic choices. Semantics for BPMN models in process algebra and process refinements are outlined in <ref type="bibr" target="#b12">[13]</ref>. The refinement is validated with model checker.</p><p>Calculus of communication systems and transition systems is used in other works like in <ref type="bibr" target="#b6">[7,</ref><ref type="bibr" target="#b7">8]</ref>. The π-calculus is a first order calculus for concurrent systems. The bisimulation (equivalence relationship between transition systems) for the π-calculus is described in <ref type="bibr" target="#b8">[9]</ref> and in <ref type="bibr" target="#b9">[10]</ref> higher-order process calculus is used to analyse bisimulation. Some of these approaches also apply the execution set semantics from <ref type="bibr" target="#b13">[14]</ref>, but without refinement validation.</p><p>In <ref type="bibr" target="#b4">[5]</ref> actions and services are described in DL. Actions contain pre-and post-conditions. As inference problems, the realizability of a service, subsumption relation between services and service effect checking is analysed. Services are also described with DL in <ref type="bibr" target="#b1">[2]</ref>. The reasoning tasks are checking of pre-and post-conditions. The focus of this work is the reasoning complexity.</p><p>The DL DLR is extended with temporal operators in <ref type="bibr" target="#b0">[1]</ref>. Based on this extension, query containment for specified (temporal) properties is analysed. In <ref type="bibr" target="#b5">[6]</ref> the DL ALC is extended with the temporal logics LTL and CTL. Still, neither of them considers process modelling and refinements.</p><p>In this paper, we have devised a method to checking process refinement w.r.t. execution set semantics. We restricted our solution to a commonly used subset of BPMN <ref type="bibr" target="#b14">[15]</ref>, which we may extend in the future. We perform a topological transformation of process models and translate them into ALC ontologies. The refinement checking can be reduced to concept unsatisfiability checking. In the future, we will implement and evaluate our approach, and extend it to deal with more constraints.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head></head><label></label><figDesc>a) shows a BPMN diagram of a simple flow which consists of two activities between the Start and End nodes; (b) shows the usage of exclusive gateway ( ) indicating that the flow can go through one and only one of its branches, and parallel gateway ( ) indicating that the flow should go through all of its branches; (c) shows the usage of a loop indicating that the flow can go back to previous gateways or activities. In block-based process modelling, gateways always appear in pairs.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head></head><label></label><figDesc>is {[AB]}: first A, then B. Any two branches behind an exclusive gateway ( ) cannot occur together in the same path, thus ES Component2 is {[E], [EF]} (see Fig. 1d). When they are behind a parallel gateway ( ), any ordering between activities of the branches are valid, thus [a 1 a 2 b 1 b 2 ], [a 1 b 1 a 2 b 2 ] and [a 1 b 1 b 2 a 2 ] ∈ ES Specif ic (see Fig. 1b). The execution set of a process containing a loop is infinite, e. g., ES Component1 = {[C], [CDCD], . . .} (see Fig.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. Wrong process refinement</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head></head><label></label><figDesc>Fig. 1b yields {[AABB], [ABBA], [ABAB], [AA]}. 2. Decomposition. Replace all pairs of duplicate activities by a single activity in each execution of ES Q . For Fig. 1b this yields {[AB], [ABA], [ABAB], [A]}.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. Execution diagram for Fig. 1b</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head></head><label></label><figDesc>) ⊆ P S P (a) and SS Q (a) ⊆ SS P (a). Proof. (1) For the → direction the lhs ES Q ⊆ ES P holds. Given a ∈ Q and b ∈ P S Q (a), we demonstrate that b ∈ P S P (a) holds: [b, a] is a subpath of some X ∈ ES Q , from precondition it follows [b, a] is a subpath of X ∈ ES P and the definition of P S leads to b ∈ P S P (a). Correspondingly for c ∈ SS Q (a), it follows from definition [a, c] is a subpath of some Y ∈ ES Q and from precondition follows [a, c] is a subpath of Y ∈ ES P . The definition of SS leads to c ∈ SS P (a).</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_6"><head>Definition 1 .</head><label>1</label><figDesc>: Pre-refinement-from operator Pr f rom (S) = ∀f rom. x∈S x Pre-refinement-to operator Pr to (S) = ∀to. y∈S y Post-refinement-from operator Ps f rom (S) = x∈S ∃f rom.x Post-refinement-to operator Ps to (S) = y∈S ∃to.y</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_7"><head></head><label></label><figDesc>For example, component A ∀f rom.(Start component A), component A ∀to.(component B component A), component B ∀f rom.(component A component B) and component B ∀to.(End component B). 4. for each a ∈ Q, a Ps f rom (P S Q (a)) and a Ps to (SS Q (a)), These axioms represent the predecessor and successor sets of all the activities in the post-refinement process. For example, a 31 ∃to.End, b 11 ∃to.a 21 ∃to.b 22 5. for each z j ∈ P , Disjoint(a|a ∈ Q and Hori(a) = z j )</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_8"><head></head><label></label><figDesc>because {[AB], [A]} ⊇ {[AB], [A]}. As for comparing with the component models, renaming yields {[EDFC], [ED]}. After reduction with respect to C 1 and C 2 , we conclude that Fig. 3b correctly grounds on C 1 and C 2 because {[C], [D], [CC], [CD], [DC], [DD], . . .} ⊇ {[DC], [D]} and {[EF], [E]} ⊇ {[EF], [E]}.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_9"><head>Fig. 3 .</head><label>3</label><figDesc>Fig. 3. Correct process refinement</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>1 .</head><label>1</label><figDesc>Renaming. Replace all activities in each execution of ES Q by their grounds (function vert()). Renaming the execution set {[a 1 a 2 b 1 b 2 ], [a 1 b 1 b 2 a</figDesc><table><row><cell>2 ],</cell></row><row><cell>[a 1 b 1 a 2 b 2 ], [a 1 a 3 ]} of Fig. 1b yields {[EDFC], [EFCD], [EFDC], [ED]}.</cell></row><row><cell>2. Reduction. Remove all activities in each execution of ES Q that do not</cell></row><row><cell>appear in P . For our example, reduction with respect to Component 1 yields</cell></row><row><cell>{[DC], [CD], [D]}. Reduction with respect to Component 2 yields {[EF], [E]}.</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head></head><label></label><figDesc>example, in the horizontal refinement ontology, a 31 ∃compose.A, component A ≡ ∃compose.A and component A ∀to.(component B component A) implies that a 31 ∀to.(component B component A). However a 31 ∃to.End, and Disjoint(End, component A, component B) indicates that a 31 is unsatisfiable. Therefore the top route [a11, a31] in the specific process model is invalid, so as the entire refinement.</figDesc><table /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">http://www.bpmn.org/</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgements</head><p>This work has been supported by the European Project Marrying Ontologies and Software Technologies (MOST ICT 2008-216691).</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">A Temporal Description Logic for Reasoning over Conceptual Schemas and Queries</title>
		<author>
			<persName><forename type="first">A</forename><surname>Artale</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Franconi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Wolter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Zakharyaschev</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="s">Lecture notes in computer science</title>
		<imprint>
			<biblScope unit="page" from="98" to="110" />
			<date type="published" when="2002">2002</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">A Description Logic Based Approach to Reasoning about Web Services</title>
		<author>
			<persName><forename type="first">F</forename><surname>Baader</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Lutz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Milicic</surname></persName>
		</author>
		<author>
			<persName><forename type="first">U</forename><surname>Sattler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Wolter</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the WWW 2005 Workshop on Web Service Semantics (WSS2005)</title>
				<meeting>the WWW 2005 Workshop on Web Service Semantics (WSS2005)<address><addrLine>Chiba City, Japan</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<title level="m" type="main">The Modelling of Temporal Properties in a Process Algebra Framework</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">J</forename><surname>Cowie</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1999">1999</date>
		</imprint>
		<respStmt>
			<orgName>University of South Australia</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">PhD thesis</note>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Expressing semantic Web service behavior with description logics</title>
		<author>
			<persName><forename type="first">Markus</forename><surname>Fronk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Jens</forename><surname>Lemcke</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Semantics for Business Process Management Workshop at ESWC</title>
				<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">A Proposal for Describing Services with DLs</title>
		<author>
			<persName><forename type="first">C</forename><surname>Lutz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">U</forename><surname>Sattler</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 2002 International Workshop on Description Logics</title>
				<meeting>the 2002 International Workshop on Description Logics</meeting>
		<imprint>
			<date type="published" when="2002">2002</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Temporal description logics: A survey. In Temporal Representation and Reasoning</title>
		<author>
			<persName><forename type="first">C</forename><surname>Lutz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Wolter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Zakharyaschev</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">TIME&apos;08. 15th International Symposium on</title>
				<imprint>
			<date type="published" when="2008">2008. 2008</date>
			<biblScope unit="page" from="3" to="14" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">A Calculus of Communicating Systems</title>
		<author>
			<persName><forename type="first">R</forename><surname>Milner</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Springer LNCS</title>
		<imprint>
			<date type="published" when="1980">1980</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<title level="m" type="main">Communication and Concurrency</title>
		<author>
			<persName><forename type="first">R</forename><surname>Milner</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1989">1989</date>
			<publisher>Prentice Hall</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">A Calculus of Mobile Processes</title>
		<author>
			<persName><forename type="first">R</forename><surname>Milner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Parrow</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Walker</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Information and Computation</title>
				<imprint>
			<date type="published" when="1992">1992</date>
			<biblScope unit="page" from="41" to="77" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Bisimulation for Higher-Order Process Calculi</title>
		<author>
			<persName><forename type="first">Davide</forename><surname>Sangiorgi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Information and Computation</title>
		<imprint>
			<biblScope unit="volume">131</biblScope>
			<biblScope unit="page" from="141" to="178" />
			<date type="published" when="1996">1996</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Semantic Business Process Validation</title>
		<author>
			<persName><forename type="first">I</forename><surname>Weber</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Hoffmann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Mendling</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of International workshop on Semantic Business Process Management</title>
				<meeting>of International workshop on Semantic Business ess Management</meeting>
		<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Beyond Soundness: On the Correctness of Executable Process Models</title>
		<author>
			<persName><forename type="first">I</forename><surname>Weber</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Joerg</forename><surname>Hoffmann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Jan</forename><surname>Mendling</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of European Conference on Web Services (ECOWS)</title>
				<meeting>of European Conference on Web Services (ECOWS)</meeting>
		<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">A process-algebraic approach to workflow specification and refinement</title>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">Y H</forename><surname>Wong</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Gibbons</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Lecture Notes in Computer Science</title>
		<imprint>
			<biblScope unit="volume">4829</biblScope>
			<biblScope unit="page">51</biblScope>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Defining specialization for process models</title>
		<author>
			<persName><forename type="first">George</forename><forename type="middle">M</forename><surname>Wyner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Jintae</forename><surname>Lee</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Organizing Business Knowledge: The MIT Process Handbook</title>
				<imprint>
			<publisher>MIT Press</publisher>
			<date type="published" when="2003">2003</date>
			<biblScope unit="volume">5</biblScope>
			<biblScope unit="page" from="131" to="174" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">How much language is enough? Theoretical and practical use of the Business Process Modeling Notation</title>
		<author>
			<persName><forename type="first">Jan</forename><surname>Michael Zur Muehlen</surname></persName>
		</author>
		<author>
			<persName><surname>Recker</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CAiSE</title>
		<title level="s">Lecture Notes in Computer Science</title>
		<editor>
			<persName><forename type="first">Zohra</forename><surname>Bellahsene</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Michel</forename><surname>Léonard</surname></persName>
		</editor>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2008">2008</date>
			<biblScope unit="volume">5074</biblScope>
			<biblScope unit="page" from="465" to="479" />
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
