<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Exploring the Dynamic Costs of Process-aware Information Systems through Simulation</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Information Systems Group, University of Twente</institution>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Introducing process-aware information systems (PAIS) in enterprises (e.g., workflow management systems, case handling systems) is associated with high costs. Though cost evaluation has received considerable attention in software engineering for many years, it is difficult to apply existing evaluation approaches to PAIS. This difficulty particularly stems from the inability of these techniques to deal with the complex interplay of the many technological, organizational and project-driven factors which emerge in the context of PAIS engineering projects. In response to this problem this paper proposes an approach which utilizes simulation models for investigating costs related to PAIS engineering projects. We motivate the need for simulation, discuss the design and execution of simulation models, and give an illustrating example.</p>
      </abstract>
      <kwd-group>
        <kwd>Cost Modeling</kwd>
        <kwd>Simulation Models</kwd>
        <kwd>Method Engineering</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        Process-aware information systems (PAIS) separate process logic from application code
and orchestrate business processes according to their defined logic during run-time
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. To enable the realization of PAIS, a variety of process support paradigms (e.g.,
workflow management, service flows, case handling), process modeling standards (e.g.,
BPEL4WS, BPML), and process management tools (e.g., ARIS Toolset, Staffware)
have been introduced [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        While the benefits of PAIS are typically justified by improved business process
performance [
        <xref ref-type="bibr" rid="ref3 ref4 ref5">3–5</xref>
        ] and cheaper process implementation [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], there exist no approaches for
systematically analyzing related costs. In particular, existing cost evaluation techniques
are unable to cope with the numerous technological, organizational and project-driven
factors to be considered in the context of a PAIS (and which do only partly exist in
projects developing data- or function-centered information systems) [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. As an
example, consider costs for analyzing and redesigning business processes. Another challenge
results from the many causal dependencies between evaluation factors. Activities
related to business process redesign, for example, can be influenced by impact factors like
available process knowledge or end user fears. These dependencies result in dynamic
economic effects which can influence the overall costs of a PAIS engineering project
significantly. Existing approaches are typically not able to deal with such effects as they
rely on static models based upon snapshots of the analyzed software system.
What is needed is a comprehensive approach that enables system engineers to model
the complex interplay between the cost and impact factors that arise in the context of
PAIS, and to investigate resulting effects. In response to this need we have introduced
the notion of evaluation models in [
        <xref ref-type="bibr" rid="ref8 ref9">8, 9</xref>
        ]. This paper deals with the simulation of the
dynamic costs of PAIS engineering projects. Section 2 describes background information
necessary for understanding the paper. Section 3 deals with simulation as envisioned in
our approach. Section 4 concludes with a summary.
2
      </p>
      <p>
        The EcoPOST Evaluation Framework
In [
        <xref ref-type="bibr" rid="ref8 ref9">8, 9</xref>
        ] we have introduced a model-based approach for systematically investigating
the complex cost structures of PAIS engineering projects. This approach distinguishes
between different kinds of evaluation factors to be considered when dealing with the
costs of PAIS engineering projects.
      </p>
      <p>Terminology. A Static Cost Factors (SCF) represent costs whose value does not
change during a PAIS engineering project (except for its time value, which is not
further considered in this paper). As typical examples of SCF consider software license
costs, hardware costs, or costs for external consultants. Dynamic Cost Factors (DCF),
in turn, represent costs that are determined by activities related to a PAIS engineering
project. These activities cause measurable efforts, which, in turn, vary due to the
influence of impact factors. The (re)design of business processes prior to the introduction of
PAIS, for example, constitutes such an activity. The DCF ”Costs for Business Process
Redesign”, for instance, may be influenced by an intangible factor ”Willingness of Staff
Members to support Redesign Activities”. Obviously, if staff members do not contribute
to a redesign project by providing needed information (e.g., about process details), any
redesign effort will be ineffective and will increase costs. If staff willingness is
additionally varying during the redesign activity (e.g., due to a changing communication
policy), the DCF will be subject to more complex effects.</p>
      <p>In the EcoPOST framework, intangible factors like ”Willingness of Staff Members
to support Redesign Activities” are represented by Impact Factors (ImF). They are
intangible evaluation factors that influence DCF (or more precisely, the activities
underlying a DCF). ImF cause the value of a DCF to change, making the evaluation of DCF
a difficult task to accomplish. As examples consider factors such as ”End User Fears”,
”Availability of Process Knowledge”, or ”Ability to redesign Business Processes”.
Opposed to SCF and DCF, the values of ImF are not quantified in monetary terms, but
are based on qualitative scales describing the degree of an ImF (ranging from ”low” to
”high”). ImF can be further classified into static and dynamic ImF. The value of a static
ImF does not change. The value of a dynamic ImF, by contrast, may change (due to the
influence of other ImF).</p>
      <p>
        Evaluation Models. To better understand the evolution of DCF as well as DCF
interference through ImF, we use evaluation models. In particular, each DCF is
represented and analyzed by exactly one evaluation model. These models are specified using
the System Dynamics (SD) [
        <xref ref-type="bibr" rid="ref10 ref11 ref12">10–12</xref>
        ] notation (cf. Fig. 1A) [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. SCF, DCF, and ImF are
represented by different types of variables. State variables, for example, are used to
represent dynamic factors, i.e., to capture changing values of DCF (e.g., the ”Costs for
Business Process Redesign”; cf. Fig. 1B) and dynamic ImF (e.g., degree of ”Process
Knowledge”). A state variable is graphically denoted as rectangle (cf. Fig. 1B), and its
value at time t is determined by the accumulated changes of this variable from starting
point t0 to present moment t (t &gt; t0); similar to a bathtub which accumulates – at a
defined moment t – the amount of water which has been poured into it in the past. Each
state variable needs to be connected to at least one source or sink. Both sources and
sinks are graphically denoted as cloud-like symbols.
      </p>
      <sec id="sec-1-1">
        <title>A) Notation</title>
        <p>Dynamic Cost Factors
Dynamic Impact Factors
Static Cost Factor [Text]
Static Impact Factor [Text]
Sources and Sinks
Rate Variables
Auxiliary Variables [Text]
Links [+|-]
Flows</p>
      </sec>
      <sec id="sec-1-2">
        <title>B) State Variables &amp; Flows</title>
        <p>IncCroesatse BCuossitnsefsosr DeCcroesatse</p>
        <sec id="sec-1-2-1">
          <title>Process</title>
        </sec>
        <sec id="sec-1-2-2">
          <title>Redesign</title>
          <p>thCeonItnrfollosw DCFthCeonOturtofllsow</p>
        </sec>
        <sec id="sec-1-2-3">
          <title>Water Tap</title>
        </sec>
        <sec id="sec-1-2-4">
          <title>Water</title>
        </sec>
        <sec id="sec-1-2-5">
          <title>Drain</title>
        </sec>
      </sec>
      <sec id="sec-1-3">
        <title>C) Using Auxiliary Variables as Intermediate Variables</title>
        <p>KnPorowcleesdsge - APnrCoaoclysestssiss
SCF1</p>
        <sec id="sec-1-3-1">
          <title>Process Modeling</title>
        </sec>
        <sec id="sec-1-3-2">
          <title>Costs</title>
          <p>AbiliBtyutsoinreesdsesign SCF2</p>
        </sec>
      </sec>
      <sec id="sec-1-4">
        <title>Processes ImFS</title>
        <p>Process +</p>
        <sec id="sec-1-4-1">
          <title>Definition</title>
          <p>- Costs
+</p>
        </sec>
        <sec id="sec-1-4-2">
          <title>Cost Increase</title>
        </sec>
        <sec id="sec-1-4-3">
          <title>Business Process</title>
        </sec>
        <sec id="sec-1-4-4">
          <title>Redesign Costs</title>
        </sec>
        <sec id="sec-1-4-5">
          <title>Cost Decrease</title>
          <p>+
+ Auxiliary
-Variable</p>
          <p>Values of state variables change through inflows and outflows. Graphically, both flow
types are depicted by twin-arrows which either point to (in the case of an inflow) or
out of (in the case of an outflow) the state variable (cf. Fig. 1B). Picking up the bathtub
image, an inflow is a pipe that adds water to the bathtub, i.e., inflows increase the value
of a state variable. An outflow, by contrast, is a pipe that purges water from the
bathtub, i.e., outflows decrease the value of a state variable. The DCF ”Costs for Business
Process Redesign” as shown in Fig. 1C, for example, increases through its inflow ”Cost
Increase” and decreases through its outflow ”Cost Decrease”. Returning to the bathtub
image, we further need ”water taps” to control the amount of water flowing into the
bathtub, and ”drains” to specify the amount of water flowing out. For this purpose, a
rate variable is assigned to each flow (graphically depicted by a valve; cf. Fig. 1B).</p>
          <p>In addition to state variables representing DCF and dynamic ImF, evaluation models
comprise constants and auxiliary variables (which are both graphically represented by
their name). Constants are used to represent static evaluation factors, i.e., SCF and static
ImF in our context. As an example for a SCF consider license costs. As an example for
a static ImF consider a given degree of ”Process Complexity”. Auxiliary variables, in
turn, represent intermediate variables. As an example consider the auxiliary variable
”Process Definition Costs” in Fig. 1C. Both constants and auxiliary variables are
embedded in an evaluation model with links (not flows), i.e., labeled arrows. A positive
link (labeled with ”+”) between x and y (with y as dependent variable) indicates that
y will tend in the same direction if a change occurs in x. A negative link (labeled with
”-”) expresses that the dependent variable y will tend in the opposite direction.</p>
          <p>Illustrating Example. Fig. 2 shows a model which describes the influence of the
dynamic ImF ”End User Fears” on the DCF ”Costs for Business Process Redesign”.
More specifically, this model reflects the assumption that the introduction of a PAIS
may cause end user fears, e.g., due to a high degree of job redesign and due to changed
social clues. Such end user fears can lead to emotional user resistance. This, in turn,
results in a decreasing ability to acquire process knowledge. Reason is that an
increasing emotional resistance makes profound process analysis (e.g., based on interviews
with process participants) a difficult task to accomplish. A decreasing ability to acquire
process knowledge results in a decreasing ability to redesign business processes.</p>
          <p>Degree of Job</p>
          <p>Redesign</p>
          <p>Impact due to</p>
          <p>J+ob Redesign
Impact due to Changes
concerning Social Clue
and Interactions</p>
          <p>+</p>
          <p>Change of
Social Clue and
Interactions</p>
          <p>Illustrating Example: The Impact of „End User Fears“ on „Costs for Business Process Redesign“</p>
          <p>Ability to redesign</p>
          <p>Business Processes
+
+ +</p>
          <p>Fear
Growth</p>
          <p>Rate
End User
Fears
+ GRreoswistthanRcaete
Emotional
Resistance</p>
          <p>Decreasing Ability to
redesign Business
+ Processes</p>
          <p>Ability to acquire</p>
          <p>Process
Knowledge</p>
          <p>Notation
Dynamic Cost Factors
Dynamic Impact Factors</p>
          <p>Static Cost Factor [Text]
- ItPKnorncoaorcceweqalseussiidrngegeAbility SSARtuoaaxutteiirlcciaVeIramsyrpiaVaanabcdlrteiaSsFbianleckstsor [[TTeexxtt]]</p>
          <p>Links [+|-]
Flows
FearRRaetdeuction
+</p>
          <p>+
Cost Rate</p>
          <p>Costs for Business
Process Redesign</p>
          <p>Communication</p>
          <p>Growth Rate</p>
          <p>Communication
3 Simulating EcoPOST Evaluation Models
Evaluation models, like the one depicted in Fig. 2, are very useful for PAIS engineers.
However, the evolution of DCF and dynamic ImF is difficult to comprehend. For this
reason, we add components for analyzing this evolution to our overall evaluation
framework. More precisely, this section describes how evaluation models can be simulated in
order to unfold their dynamic effects.
3.1</p>
          <p>
            Understanding PAIS Engineering Projects as Feedback Systems
As mentioned, we use System Dynamics (SD) for defining evaluation models. SD is a
formalism for studying and modeling complex feedback systems, as they can be found,
for example, in biological, environmental, industrial, business, and social systems [
            <xref ref-type="bibr" rid="ref10 ref11">10,
11</xref>
            ]. Its underlying assumption is that human mind is excellent in observing the
elementary forces and actions out of which a system is composed (e.g., fears, delays, resistance
to change), but unable to understand dynamic implications resulting from these forces
and actions. In PAIS engineering projects we have the same situation. Such projects
are characterized by a strong nexus of organizational, technological, and project-driven
factors. Thereby, the identification of these factors constitutes one main problem. Far
more difficult is to understand causal dependencies between factors and resulting
effects. Only by considering PAIS engineering projects as feedback system we are able
to unfold the dynamic effects caused by these dependencies and the different
organizational, technological, and project-driven system parts.
          </p>
          <p>”Feedback” refers to situations in which a factor X (e.g., user fears) affects another
factor Y (e.g., emotional resistance of end users), and factor Y, in turn, affects X (either
directly or indirectly). SD denotes such causal structures (or cyclic chains of causes and
effects) as ”feedback loops” (see below). It assumes that it is not possible to study the
causal dependency between X and Y without considering the entire system.</p>
          <p>
            There are other formalisms that can be used to model complex systems of
interacting factors. Causal Bayesian Networks (BN) [
            <xref ref-type="bibr" rid="ref14">14</xref>
            ], for example, promise to be a useful
approach in this context as well. BN deal with (un)certainty and focus on
determining probabilities of events. A BN is a directed acyclic graph which represents
independencies embodied in a given joint probability distribution over a set of variables.
Variables can be measurable or intangible parameters or random variables (which form
the ”Bayesian” aspect of a BN). In our context, we are interested in the interplay of
the parts (components) of a system and the effects resulting from this interplay. BN do
not allow to model feedback loops as cycles in BN would allow infinite feedbacks and
oscillations that would prevent stable parameters of the probability distribution.
          </p>
          <p>
            Agent-based modeling provides another promising approach. Resulting models
comprise a set of reactive, intentional, or social agents encapsulating the behavior of the
various variables that make up a system [
            <xref ref-type="bibr" rid="ref15">15</xref>
            ]. During simulation, the behavior of these
agents is emulated according to defined rules [
            <xref ref-type="bibr" rid="ref16">16</xref>
            ]. System-level information (e.g., about
intangible factors being effective in a PAIS engineering project) is thereby not further
considered. However, as system-level information is an important aspect in our
approach, we have not further considered the use of agent-based modeling.
3.2
          </p>
          <p>
            Feedback Loops
Changes of DCF and dynamic ImF are caused by the interplay of the different elements
of an evaluation model, i.e., the complex interdependencies between dynamic and static
evaluation factors, flows and links. In this context, feedback loops are of particular
importance. A feedback loop is a closed cycle of causes and effects. Within this cycle, past
events (like the change of a DCF or dynamic ImF) are utilized to control future actions
(like another change of the same evaluation factor). In other words, if a change occurs
in a model variable, which is part of a feedback loop, this change will be propagated
around the loop [
            <xref ref-type="bibr" rid="ref12">12</xref>
            ].
          </p>
          <p>As an example consider the feedback loop depicted in Fig. 2. Basic to this model
is a cyclic structure connecting the four dynamic ImF ”End User Fears”, ”Emotional
Resistance”, ”Ability to acquire Process Knowledge”, and ”Ability to redesign Business
Processes”. As aforementioned, it reflects the assumption that the introduction of a
PAIS may cause end user fears, e.g., due to a high degree of job redesign. Such end
user fears lead to increased emotional resistance. This, in turn, decreases the ability
to get support from end users during process redesign and thus decreases the ability
to effectively redesign business processes. Finally, a lower ability to redesign business
processes results in decreased end user fears. Reason is that the end users will be less
afraid of change if the ability to redesign processes decreases.</p>
          <p>We distinguish between two kinds of loop polarities. Positive loops generate growth
of DCF and dynamic ImF (cf. Fig. 3A). Negative loops, in turn, counteract and oppose
growth (cf. Fig. 3B). If evaluation models contain both positive and negative feedback
loops, more complex effects will result (cf. Fig. 3 C-E).</p>
          <p>The polarity of a feedback loop is equivalent to the sign of the open loop gain.
”Gain” refers to the strength of the change returned by a loop and ”open loop” means
sso
t
C
sso
t
C</p>
          <p>Evolution
of a DCF
Evolution
of a DCF</p>
          <p>time
A) Exponential Growth</p>
          <p>B) Goal-seeking Behavior
time
E) Overshoot and Collapse</p>
          <p>F
m
fI
o
e
e
r
g
e
D</p>
          <p>Maximum Degree</p>
          <p>Evolution of
a dynamic ImF</p>
          <p>time
F) Calculating the „Open Loop Gain“ of a Feedback Loop
21)) TBrraecaek tthhee eloffoepctaonfaancyhpaoningte around the loop x1
Polarity = SGN(∂x1O /∂x1I)
∂x1O /∂x1I = (∂x1O /∂x4)(∂x4 /∂x3)(∂x3 /∂x2)(∂x2 /∂x1I)</p>
          <p>x3
C)xOIscillation
1</p>
          <p>Evolution
of a DCF
sso
t
C
x2</p>
          <p>D) S-shaped Growth
sso
t</p>
          <p>C
time
x4
x2
x1I x1O
x3</p>
          <p>
            Evolution
of a DCF
time
x4
that the gain is calculated for just one feedback cycle by opening the closed loop at
some point [
            <xref ref-type="bibr" rid="ref12">12</xref>
            ]. Consider Fig. 3F which shows a closed feedback loop consisting of
four variables x1, ..., x4. Assume that we open the loop at x1. This splits x1 into an input
variable (x1I) and an output variable (x1O). The open loop gain is then defined as the
(partial) derivative of x1O with respect to x1I; i.e., the feedback effect of a change in
a variable as it is propagated around a loop. Thus, loop polarity can be calculated as
SGN(δx1O/δx1I), where SGN() is the sign function, returning +1 in case of positive loop
polarity, and -1 otherwise (if the open loop gain is zero, there will be no loop).
          </p>
          <p>
            It is important to mention that dynamic effects caused by feedback loops are not
easy to understand [
            <xref ref-type="bibr" rid="ref11 ref17">11, 17</xref>
            ]. In order to systematically investigate their effects in detail,
we simulate our evaluation models.
In the EcoPOST framework, simulation is based on a step-by-step numerical solution
of algebraic equations, which specify how to perform a simulation from an initial
condition and how to compute succeeding conditions [
            <xref ref-type="bibr" rid="ref11">11</xref>
            ]. In other words, the equations
define how the variables of an evaluation model change over time.
          </p>
          <p>Illustrating Example. Consider Fig. 4 which depicts the simulation of two dynamic
evaluation factors: a DCF and a dynamic ImF. The condition at time t0 has been
calculated and the condition at time t1 is now being evaluated. DT stands for ”Difference in
Time” and denotes the length of the time interval between two conditions. DCF.t0 and
ImF.t0 designate the two values of DCF and ImF at time t0 (cf. Fig. 4A). R1.[t0,t1[ is a
rate variable specifying the inflow of DCF within the time interval [t0,t1[. Similarly, the
rate variables R2.[t0,t1[ and R3.[t0,t1[ specify the inflow respectively outflow of ImF
within the time interval [t0,t1[. Therewith, all information needed to compute the new
values of DCF and ImF is available.</p>
          <p>Within the time interval [t0,t1[, the rate variables act on DCF and ImF and cause
them to change. The new values of DCF and ImF at time t1 are calculated by adding
and subtracting the changes represented by these rates (cf. Fig. 4B). Finishing the
com</p>
          <p>ImF.t0 R3.[t0,t1[</p>
          <p>R2.[t0,t1[</p>
          <p>R1.[t0,t1[
DCF.t0</p>
          <p>DT
t0
t1</p>
          <p>B) At time t1...</p>
          <p>ImF.t0
DCF.t0</p>
          <p>DT
t0
t1</p>
          <p>ImF.t1
DCF.t1</p>
          <p>C) Next Rates taking Effect...</p>
          <p>R2.[t1,t2[
ImF.t1
DCF.t1 R1.[t1,t2[</p>
          <p>DT
t2
time
t2
time
t0
t1
t2
time
putation creates the situation shown in Fig. 4B. In the following, only these values are
needed to compute the forthcoming rates for the [t1,t2[ interval (cf. Fig. 4C).</p>
          <p>Sensitivity Analysis. Note that the numerical solution of equations does not allow
to determine an arbitrary future condition during a simulation without first computing
through all previous conditions. Each step-by-step numerical solution represents one
simulation run with one final condition. In order to determine another condition, an
additional step-by-step computation has to be conducted. Therewith, it becomes possible
to conduct behavioral ”experiments” based on a series of simulation runs. During these
simulation runs equations are manipulated in a controlled manner to systematically
investigate the effects of changed simulation parameters. Therewith, it becomes possible
to accomplish sensitivity analysis, i.e., to investigate how the output of a simulation will
vary if the initial condition of a simulation is changed.
In the EcoPOST framework, a simulation model consists of a number of algebraic
equations – one for each model variable (i.e., dynamic and static evaluation factors as well
as rate variables and auxiliary variables). We use different types of algebraic equations
for the different variables of an evaluation model (cf. Fig. 5A).</p>
          <p>
            Elements of a Simulation Model. Static evaluation factors (i.e., SCF and static ImF)
are specified based on numerical values in constant equations (e.g., ”Process Redesign
Costs = 1000 $/Week”). Dynamic evaluation factors (i.e., DCF and dynamic ImF), in
turn, are specified by integral equations [
            <xref ref-type="bibr" rid="ref11">11</xref>
            ]. Such equations specify the accumulation
of a dynamic evaluation factor from a starting point t0 to the present moment t (cf. Fig.
5B). More specifically, DCF and dynamic ImF integrate their net flow. The net flow
during any interval [t1,t2] is the area bounded by the graph of the net rate between the
start and the end of the interval (cf. Fig. 5C). Thus, the value of a dynamic evaluation
factor at t2 can be calculated as the sum of its value at t1 and the area under the net rate
curve between t1 and t2. In Fig. 5C, the value at t1 is S1. Adding the area under the net
rate curve between t1 and t2 increases the value to S2.
          </p>
          <p>Rate variables are specified by rate equations. A rate equation specifies the net
change caused by a particular flow (influencing either a DCF or a dynamic ImF)
between two computed conditions (cf. Section 3.3). Rate equations for DCF-related flows
A) Elements of a Simulation Model</p>
          <p>B) Specifying Dynamic Evaluation Factors
Constant
Equations</p>
          <p>Rate
Equations</p>
          <p>Set of
Equations</p>
          <p>Integral
Equations
Auxiliary</p>
          <p>Equations
Equation-based Simulation Model
Step-by-Step Numerical Solution</p>
          <p>DCF*</p>
          <p>Inflow Outflow
DCF(t) = ∫t[Inflow(s) - Outflow(s)]ds + DCF(t0)
where t0
- Inflow(s) represents the value of the inflow at any time s
between between the initial time t0 and the current time t.
- Outflow(s) represents the value of the outflow at any time s
between between the initial time t0 and the current time t.
- DCF(t0) represents the initial value of DCF at t0.
* also valid for dynamic ImF
e
t
a
R
t
e
N
0
CS2
F
D
a
f
o
lauS1
e</p>
          <p>V
C) Graphical Integration (DCF &amp; dyn. ImF)</p>
          <p>Change of the
DCF = Grey Area
t1
t2</p>
          <p>Change
of the DCF
time
time
specify the ”amount of costs” flowing to, from, or between DCF. Rate equations for
ImF-related flows specify the ”impact” flowing to, from, or between dynamic ImF. A
rate equation comprises those model variables which influence the flow it controls. This
can be SCF, DCF, dynamic ImF, and auxiliary variables.</p>
          <p>Finally, auxiliary variables are specified by auxiliary equations. Their constituting
elements may be static and dynamic evaluation factors as well as other auxiliary
variables. Though the value of auxiliary variables changes during simulation, they do not
represent a model state. Instead, they are used for intermediate calculations.
Nonlinear Relationships. An important part of our evaluation models are ImF. If an
(either static or dynamic) ImF has a nonlinear impact on DCF, such nonlinearities will
have to be represented in our simulation models as well. In our simulation models,
nonlinearities are represented by an additional auxiliary variable between the ImF and
the DCF. This auxiliary variable is specified by a table1 function f transferring an input
value X (e.g., a certain level of process knowledge) into a corresponding output value
Y (e.g., expressing a specific effect on a DCF).
1
0
ttr
o
c
a
F
Iacem
p
o
t
u
tD
Icam
p</p>
          <p>A</p>
          <p>Impact
Rating
(IR) &lt; 1</p>
          <p>Impact
2
tro
c
a
tF
Icaem
p
to
u
d
F
C
D
n
to
Icam
p
1</p>
          <p>B</p>
          <p>Impact
Rating
(IR) &gt; 1</p>
          <p>Impact
Rating
(IR) &gt; 1
2
tro
c
a
tF
Icaem
p
to
u
d
F
C
D
n
to
Iacm
p
1</p>
          <p>C
Impact</p>
          <p>
            Impact
0 Degree of Impact Factor (normalized) 1
0 Degree of Impact Factor (normalized) 1
0 Degree of Impact Factor (normalized) 1
IR = f(x) with x,IRin [
            <xref ref-type="bibr" rid="ref1">0,1</xref>
            ]
          </p>
          <p>
            IR = f(x) with x in [
            <xref ref-type="bibr" rid="ref1">0,1</xref>
            ] and IR in [
            <xref ref-type="bibr" rid="ref1 ref2">1,2</xref>
            ]
          </p>
          <p>
            IR = f(x) with x in [
            <xref ref-type="bibr" rid="ref1">0,1</xref>
            ] and IR in [
            <xref ref-type="bibr" rid="ref1 ref2">1,2</xref>
            ]
1 Linear interpolation is used for values lying between the specified table values.
1 results in decreasing costs (cf. Fig. 6A). A rating equal to 1 does neither increase nor
decrease costs. A rating larger than 1 results in increasing costs (cf. Fig. 6B and Fig.
6C). Quantifications based on such impact ratings are also known from software cost
models like COCOMO [
            <xref ref-type="bibr" rid="ref18">18</xref>
            ]. Generally, there exists no standard way of building robust
table functions (a ”best practice” guideline is given in [
            <xref ref-type="bibr" rid="ref12">12</xref>
            ]).
          </p>
          <p>Empirical and Experimental Research. The expressiveness of simulation results
always depends on the plausibility and resilience of the underlying simulation model.
In particular, the specification of nonlinear dependencies is a difficult task to
accomplish. In order to be able to build simulation models, it is often inevitable to rely on
hypotheses, sometimes even arguable assumptions.</p>
          <p>
            In response to this problem (i.e., to generate needed data), we have accomplished
various empirical and experimental research activities in the EcoPOST project (e.g.,
software experiments, online surveys, case studies) in order to put our simulation
models on a more reliable basis (see [
            <xref ref-type="bibr" rid="ref19">19</xref>
            ] for examples).
3.5
          </p>
          <p>Illustrating Example</p>
          <p>Assume that the business process redesign activities are scheduled for 32 weeks. In
order to simulate the evolution of the resulting costs along this time frame, we use the
2 Note that it is the basic goal of this example to illustrate the simulation of our evaluation models. Usually, evaluation
models are more complex. However, due to lack of space we cannot give a more extensive example.
simulation model depicted in Fig. 7B. The nonlinear impact of end user fears on the
DCF is represented through a table function. Fig. 7C shows the values of the evaluation
model’s dynamic evaluation factors over time when executing the simulation model.
Fig. 7D shows the outcome of the simulation. As can be seen, there is a significant
negative impact of end user fears on the costs of business process redesign.
4</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>Summary</title>
      <p>Our paper has illustrated the use of simulation to investigate the dynamic implications
described by EcoPOST evaluation models. We have motivated the use of simulation as a
means to analyze the dynamic effects caused by feedback loops. We have described the
constituting elements of EcoPOST simulation models and have discussed the execution
of simulation models. Finally, we have given an illustrating example.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rinderle</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kreher</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dadam</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Adaptive Process Management with ADEPT2</article-title>
          .
          <source>Proc. 21th ICDE '05</source>
          , pp.
          <fpage>1113</fpage>
          -
          <lpage>1114</lpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Dumas</surname>
          </string-name>
          , M.,
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>ter Hofstede</surname>
            ,
            <given-names>A.H.</given-names>
          </string-name>
          :
          <article-title>Process-aware Information Systems: Bridging People and Software through Process Technology</article-title>
          . Wiley (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Reijers</surname>
          </string-name>
          , H.A.,
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          :
          <source>The Effectiveness of Workflow Management Systems - Predictions and Lessons Learned. Int'l. J. of Inf</source>
          . Manag.,
          <volume>25</volume>
          (
          <issue>5</issue>
          ), pp.
          <fpage>457</fpage>
          -
          <lpage>471</lpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Choenni</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bakkera</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baetsa</surname>
          </string-name>
          , W.:
          <article-title>On the Evaluation of Workflow Systems in Business Processes</article-title>
          .
          <source>Electronic Journal of IS Evaluation (EJISE)</source>
          ,
          <volume>6</volume>
          (
          <issue>2</issue>
          ) (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Oba</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Onoda</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Komoda</surname>
          </string-name>
          , N.:
          <source>Evaluating the Quantitative Effects of Workflow Systems based on Real Cases. Proc. 33rd HICSS</source>
          (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Kleiner</surname>
          </string-name>
          , N.:
          <article-title>Can Business Process Changes Be Cheaper Implemented with WorkflowManagement-Systems?</article-title>
          <source>Proc. IRMA '04</source>
          , pp.
          <fpage>529</fpage>
          -
          <lpage>532</lpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Mutschler</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>A Survey on Evaluation Factors for Business Process Management Technology</article-title>
          .
          <source>Technical Report, TR-CTIT-06-63</source>
          , University of Twente (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Mutschler</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bumiller</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>An Approach for Evaluating Workflow Management Systems from a Value-Based Perspective</article-title>
          .
          <source>Proc. 10th IEEE EDOC</source>
          , pp.
          <fpage>477</fpage>
          -
          <lpage>482</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Mutschler</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Analyzing the Dynamic Cost Factors of Process-aware Information Systems: A Model-based Approach</article-title>
          .
          <source>Proc. CAiSE</source>
          '
          <volume>07</volume>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Richardson</surname>
            ,
            <given-names>G.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pugh</surname>
            ,
            <given-names>A.L.</given-names>
          </string-name>
          :
          <article-title>System Dynamics - Modeling with DYNAMO</article-title>
          . (
          <year>1981</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Forrester</surname>
            ,
            <given-names>J.W.</given-names>
          </string-name>
          : Industrial Dynamics. Productivity Press, Cambridge, London (
          <year>1961</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Sterman</surname>
            ,
            <given-names>J.D.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Business Dynamics - Systems Thinking</surname>
          </string-name>
          and Modeling.
          <string-name>
            <surname>McGraw-Hill</surname>
          </string-name>
          (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Mutschler</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bumiller</surname>
          </string-name>
          , J.:
          <article-title>Designing an Economic-driven Evaluation Framework for Process-oriented Software Technologies</article-title>
          .
          <source>Proc. 28th ICSE</source>
          , pp.
          <fpage>885</fpage>
          -
          <lpage>888</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Jensen</surname>
            ,
            <given-names>F.V.</given-names>
          </string-name>
          :
          <article-title>Bayesian Networks and Decision Graphs</article-title>
          . Springer (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Brassel</surname>
            ,
            <given-names>K.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mhring</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schumacher</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Troitzsch</surname>
            ,
            <given-names>K.G.</given-names>
          </string-name>
          :
          <article-title>Can Agents Cover All the World? Simulating Social Phenomena</article-title>
          ,
          <source>LNEMS 456</source>
          , Springer (
          <year>1997</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Scholl</surname>
          </string-name>
          , H.J.:
          <article-title>Agent-based and System Dynamics Modeling: A Call for Cross Study and Joint Research</article-title>
          .
          <source>Proc. 34th Int'l. Conf. on System Sciences</source>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Ogata</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <string-name>
            <given-names>System</given-names>
            <surname>Dynamics. Prentice Hall</surname>
          </string-name>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Boehm</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Abts</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brown</surname>
            ,
            <given-names>A.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chulani</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Clark</surname>
            ,
            <given-names>B.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horowitz</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Madachy</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reifer</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Steece</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Software Cost Estimation with Cocomo 2</article-title>
          .
          <string-name>
            <given-names>Prentice</given-names>
            <surname>Hall</surname>
          </string-name>
          (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Mutschler</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bumiller</surname>
          </string-name>
          , J.:
          <article-title>Why Process-Orientation is Scarce: An Emp. Study of Process-oriented IS in the Autom</article-title>
          .
          <source>Industry. Proc. 10th IEEE EDOC</source>
          , pp.
          <fpage>433</fpage>
          -
          <lpage>438</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>