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

26 CHAPTER 2. PROBLEM SETTING modifying existing models rather than recreating it from scratch [9]. A process model fragment is a part of a business process model which is designed and managed to be reusable. Generally, reuse of pre-existing model fragments can facilitate and speed-up the construction of a new model. As reusable knowledge, process models can be discovered and reused in a goal-driven approach through matching process models to the desired goals. Goals lead to the exploration and consideration of alternatives, decision spaces, tradeoffs and decisions. Goals have been used as an important mechanism for connecting requirements to design and supporting reuse [213]. Goal-driven search of design components [54] and goaldriven discovery of services [90] use such kind of mechanism, where the components or services are selected based on capability to fulfill the desired goals (requirements). A process model represents how to do things not why to do things. Although a process must achieve certain goals, the relationships between goals and processes are not explicitly represented in many process models because few process modeling languages and modeling tools offer such mechanism. With few process modeling languages, goals can be modeled and linked to elements of process models, e.g. EEML process and goal models [77]. Some goal modeling methods for requirement engineering such as KAOS [21], i*/GRL [55], GBRAM [56] need to be adapted for process modeling. However, the representations of the goals and processes are various in different models. 2.6 Process Knowledge Management 2.6.1 Knowledge and process knowledge Knowledge is information that comes laden with experience, judgment, intention and values, in short, knowledge is information that is digested and internalized by human beings [169]. However, a simply collection of information is not knowledge. In [185], information and knowledge is distinguished as follows. Information only tells what it is, with great dependence on context for its meaning and with little implication for the future. Pattern [6] has the potential to represent knowledge when one is able to realize and understand the patterns and their implications. For example, the information — interest rate 5% — is the factor used by the bank to compute interest on the principal. Based on the information, there is a pattern that for $100 in a savings account the bank pays 5% interest yearly and then at the end of one year the principal in the account will be $105. Such pattern represents knowledge of the amount of the interest will be earned depends on the interest rate, the amount of the principle in the account and the period of the saving. Therefore, a pattern tends to create its own context rather than being context dependent to the same extent that information is. Pattern also serves as an Archetype [165] with both an implied repeatability and predictability. Understanding the pattern knows one what is knowledge. Process knowledge is also known as process-related knowledge. Taking the pattern view of knowledge, process knowledge is the pattern about processes which are understandable, repeatable and predictable. Another way to specify process knowledge is to ask the question "Where is the knowledge in processes?". The answers are provided in [112] such as:

2.6. PROCESS KNOWLEDGE MANAGEMENT 27 • Inputs and Outputs. One place knowledge comes into play in a process is as a production input, which is to be operated upon and transformed into an output. • Controllers. Another place where knowledge comes into play in a process is in the form of controls. In this case, knowledge can be regarded to be "embedded" in the process. • Processors. The "Processor" performs the actions needed to produce a result from the process. This kind of knowledge is "encoded" in the process. • Design. A lot of knowledge is "embedded" in the processes in the form of specifications for the outputs, the inputs, the routines and the requirements. The knowledge in the process makes itself felt through what is done, when, how, by whom and to what standards. The first three answers concern the process automation and execution. The last one is associated with process models in the analysis and design phases. Our research objects are business process models at the conceptual level. In [122], Olivé visions a goal of automating IS building by a conceptual schema-centric development (CSCD). A conceptual schema provides general knowledge about the IS domain and about the functions the IS has to perform. With such a vision, the main purpose of the activity of business process modeling is to elicit the process knowledge of the corresponding IS. Hence, we take the fourth answer to specify that the process knowledge in our research context is embedded in business process models. This statement is also reflected in [79] with "process models are carriers of process knowledge, knowledge of how to do things". 2.6.2 Knowledge representation Nonaka and Takeuchi [114] argued that a successful knowledge management program needs to, on the one hand, convert internalized tacit knowledge into explicit codified knowledge in order to share it, but also on the other hand for individuals and groups to internalize and make personally meaningful codified knowledge once it is retrieved from the knowledge management system. A crucial fact is knowledge representation. Although process knowledge is embedded in process models, it does not mean all process models are process knowledge, that is, not every process modeling representation is knowledge representation. Knowledge representation can be various in terms of the distinct roles it plays, each crucial to the task at hand [22]: • A knowledge representation (KR) is most fundamentally a surrogate, a substitute for the thing itself, used to enable an entity to determine consequences by thinking rather than acting, i.e., by reasoning about the world rather than taking action in it. • It is a set of ontological commitments, i.e., an answer to the question: In what terms should we think about the world? • It is a fragmentary theory of intelligent reasoning, expressed in terms of three components: (i) the representation’s fundamental conception of intelligent reasoning; (ii) the set of inferences the representation sanctions; and (iii) the set of inferences it recommends.

26 CHAPTER 2. PROBLEM SETTING<br />

modifying existing models rather than recreating it from scratch [9]. A process model<br />

fragment is a part <strong>of</strong> a business process model which is designed and managed to be<br />

reusable. Generally, reuse <strong>of</strong> pre-existing model fragments can facilitate and speed-up<br />

the construction <strong>of</strong> a new model.<br />

As reusable knowledge, process models can be discovered and reused in a goal-driven<br />

approach through matching process models to the desired goals. Goals lead to the<br />

exploration and consideration <strong>of</strong> alternatives, decision spaces, trade<strong>of</strong>fs and decisions.<br />

Goals have been used as an important mechanism <strong>for</strong> connecting requirements to design<br />

and supporting reuse [213]. Goal-driven search <strong>of</strong> design components [54] and goaldriven<br />

discovery <strong>of</strong> services [90] use such kind <strong>of</strong> mechanism, where the components or<br />

services are selected based on capability to fulfill the desired goals (requirements).<br />

A process model represents how to do things not why to do things. Although a<br />

process must achieve certain goals, the relationships between goals and processes are not<br />

explicitly represented in many process models because few process modeling languages<br />

and modeling tools <strong>of</strong>fer such mechanism. With few process modeling languages, goals<br />

can be modeled and linked to elements <strong>of</strong> process models, e.g. EEML process and goal<br />

models [77]. Some goal modeling methods <strong>for</strong> requirement engineering such as KAOS<br />

[21], i*/GRL [55], GBRAM [56] need to be adapted <strong>for</strong> process modeling. However,<br />

the representations <strong>of</strong> the goals and processes are various in different models.<br />

2.6 <strong>Process</strong> Knowledge Management<br />

2.6.1 Knowledge and process knowledge<br />

Knowledge is in<strong>for</strong>mation that comes laden with experience, judgment, intention and<br />

values, in short, knowledge is in<strong>for</strong>mation that is digested and internalized by human<br />

beings [169]. However, a simply collection <strong>of</strong> in<strong>for</strong>mation is not knowledge. In [185],<br />

in<strong>for</strong>mation and knowledge is distinguished as follows. In<strong>for</strong>mation only tells what it<br />

is, with great dependence on context <strong>for</strong> its meaning and with little implication <strong>for</strong> the<br />

future. Pattern [6] has the potential to represent knowledge when one is able to realize<br />

and understand the patterns and their implications. For example, the in<strong>for</strong>mation —<br />

interest rate 5% — is the factor used by the bank to compute interest on the principal.<br />

Based on the in<strong>for</strong>mation, there is a pattern that <strong>for</strong> $100 in a savings account the bank<br />

pays 5% interest yearly and then at the end <strong>of</strong> one year the principal in the account will<br />

be $105. Such pattern represents knowledge <strong>of</strong> the amount <strong>of</strong> the interest will be earned<br />

depends on the interest rate, the amount <strong>of</strong> the principle in the account and the period<br />

<strong>of</strong> the saving. There<strong>for</strong>e, a pattern tends to create its own context rather than being<br />

context dependent to the same extent that in<strong>for</strong>mation is. Pattern also serves as an<br />

Archetype [165] with both an implied repeatability and predictability. Understanding<br />

the pattern knows one what is knowledge.<br />

<strong>Process</strong> knowledge is also known as process-related knowledge. Taking the pattern<br />

view <strong>of</strong> knowledge, process knowledge is the pattern about processes which are understandable,<br />

repeatable and predictable. Another way to specify process knowledge is to<br />

ask the question "Where is the knowledge in processes?". The answers are provided<br />

in [112] such as:

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

Saved successfully!

Ooh no, something went wrong!