<!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>From Business to Process Models - a Chaining Methodology</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Birger Andersson</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Maria Bergholtz</string-name>
          <email>maria@dsv.su.se</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Bertrand Grégoire</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Paul Johannesson</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michael Schmitt</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jelena Zdravkovic</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computer and Systems Sciences Stockholm University and Royal Institute of Technology Forum 100</institution>
          ,
          <addr-line>SE-164 40 Kista</addr-line>
          ,
          <country country="SE">Sweden</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Public Research Centre Henri Tudor 29</institution>
          ,
          <addr-line>Avenue John F.Kennedy L-1855 Luxembourg-Kirchberg</addr-line>
          ,
          <country country="LU">Luxembourg</country>
        </aff>
      </contrib-group>
      <fpage>211</fpage>
      <lpage>218</lpage>
      <abstract>
        <p>In this paper we discuss the problem of how to go from a business model to a process model in a systematic way. Business models are economic models used for business analysis, while process models capture low-level business activities and their coordination. We propose a method that starts with a business model where the main actors and their relationships are identified. This forms a basis for design of a final process model. Processes are described in terms of patterns stored in a pattern library.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        In e-commerce it is possible to identify two basic types of models: business models
and process models. A business model focuses on the what in an e-commerce system,
identifying agents, goals, resources, and exchanges of resources between agents.
Thus, a business model provides a high-level view of the activities taking place in
ecommerce. A process model, on the other hand, focuses on the how in an e-commerce
system, specifying operational and procedural aspects of business communication.
Although different, business and process models are interrelated as the correctness
and quality of a process model depends on its ability to support a business model.
Two questions arise in the context. First, how can we be sure that an operational
process does support the goals and exchanges specified in a business model? This
question has been discussed in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The authors of that work do not specify how to
derive a process model from a value model, but provides a correctness criterion for a
given process model with respect to a value model. A second question is: how can
we systematically construct a process model starting from a given business model?
      </p>
      <p>
        We propose a method for addressing the second question by starting from a
business model and arriving at a process model by using patterns from a process library.
As suggested in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], the method takes into account communicative, logistical, and
trust aspects, which to a large extent determine the design of a process model. The
method is based on two recent contributions in the areas of business modelling and
requirements engineering - an analysis of the notion of value objects [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] and the use
of process patterns [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. In [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] a structured query session is proposed as a method. In
[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] a model of different types of dependencies is introduced as an intermediate step
between the value and the process model. In [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] additional aspects, such as risk
mitigation, are considered and a pattern based approach is chosen when the final process
model is designed.
      </p>
      <p>
        The business model formalism that we use in this paper is that of e3-value as
proposed in [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. The formalism is based on identifying actors involved in a business as
well as value objects that those actors exchange. The method is based on a number of
phases of business transactions. Open-EDI [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] introduces five phases of business
transactions: the planning and identification phases where values and agents are
identified respectively, the negotiation phase where commitments to particular value
exchanges are established, the actualization phase where the agreed value exchanges
are carried out and the post-actualization phase where possible complaints are
performed.
      </p>
      <p>In the next section we describe our method which is followed by a deep analysis of
the use of process patterns in Section 3. Section 4 contains some concluding remarks
and future research.</p>
    </sec>
    <sec id="sec-2">
      <title>2 Chaining Method</title>
      <p>
        In order to design a process model supporting a business model, we need to
analyze in more detail the structure of value exchanges and value objects [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. A first
distinction can be made between resources and rights on resources. A Resource is an
object that is regarded as valuable by some actors. A Right on a resource means that
an actor is entitled to use that resource in some way. An example is the ownership of
a book, which means that an actor is entitled to read the book, give it to someone else,
or even destroy it. Another example of a right is borrowing a book, which gives the
actor the right to read it, but not to give it away or destroy it. For a value exchange,
both the resource being transferred and the right on the resource must be specified.
For example, the value exchanges in which a car is sold and borrowed respectively,
concern the same resource but transfer different rights on that resource.
      </p>
      <p>Another component of a value exchange is transferring the custody of the resource
being exchanged from one actor to another. An actor has the Custody of a resource if
he has immediate charge and control of the resource, typically physical access of the
resource. If an actor has the custody of a resource, this does not mean that she has any
rights on the resource. For example, a distributor may have the custody of some
goods, but he is not allowed to use the goods in any way. Providing custody of a
resource is essential in a value exchange, as the buyer is typically unable to exercise
the rights she gets unless she has custody of the resource.</p>
      <p>A value exchange may also include the transfer of some evidence document that
certifies that the buyer has certain rights on a resource. A typical example of an
evidence document is a movie ticket that certifies that its owner has the right to watch a
movie. Summarising, a value exchange can be seen as combining four components:
- The resource being exchanged from one actor to another, e.g., a book
- The right that the buyer obtains on the resource, e.g., the ownership of a book
- The custody of the resource, e.g., the delivery of a book to the buyer
- The evidence document, e.g., a ticket
While the first two components, the resource and right, always are included in a value
exchange, the last two components are optional. For example, when buying a piece of
land, the buyer is typically not given the custody of that resource. Clearly, evidence
documents are not always provided in a value exchange. Furthermore, the provision
of custody and evidence documents may be so trivial that it is not of interest to make
them explicit.</p>
      <p>The analysis above will give a basis for the initial steps of the proposed
methodology. The starting point is an e3-value model, which we extend by introducing
elements corresponding to the components of value exchanges. In Fig. 1 rectangles
represent actors and arrows represent value exchanges.</p>
      <p>Step 1: Consider an e3-value model (see Fig. 1).</p>
      <p>Step 2: For each value exchange, determine whether the custody component of the
value exchange exists and shall be modelled explicitly. If so, add one or more arrows
to the model that represent transfers of custody from one actor to another.</p>
      <p>This step can be viewed as “factoring out” the custody component of a value
exchange and modelling it explicitly by additional flows in the model. It should be
noted that several actors may be involved in transferring the custody from one actor
to another. This is illustrated in the extended model in Fig. 2a, where the custody of a
painting is first transferred from the producer to the distributor and then from the
distributor to the customer (flows for custody are dashed).</p>
      <p>Step 3: For each value exchange, determine whether the evidence document
component of the value exchange exists and shall be modelled explicitly. If so, add one or
more arrows to the model that represent transfers of evidence documents from one
actor to another.</p>
      <p>Analogously to the step for custody, this step can be viewed as factoring out the
evidence document component of a value exchange. Also in this case, several actors
may be involved, e.g., when a ticket office supplies tickets on behalf of other service
providers. In Fig. 2b, the transfer of the owner certificate of a painting is made
explicit (flows for evidence documents are dotted).
Step 4: Identify a set of processes based on the extended e3-value model from Step 3
and the Open-EDI transaction phases described in Section 1.
a) For each value transaction, one negotiation process is added
b) For each arrow in the extended model, one actualization process is added
c) For each arrow in the extended model, optionally one post-actualization process is
added</p>
      <p>The following processes will be identified based on the extended e3-value model
in Fig. 2 (The nomenclature is Custody when discussing physical goods and Access
when discussing services): Negotiation process for Painting, Negotiation process for
Transport, PaintingCustody2Distributor, PaintingCustody2Customer,
TransportAccess2Supplier, Money2Supplier, Money2Distributor, Painting2Customer,
Transport2Supplier and EvidenceDoc2Customer.</p>
      <p>The above steps only concern the identification of flows relating the actors, which
gives a set of processes. The following step concerns the design of the resulting
processes. For this end we make use of a library where processes are described in terms of
patterns. A pattern contains information about properties that characterize sets of
processes. For example, a pattern may characterize a process as involving three actors
and to be secure.</p>
      <p>Step 5: For each process, select a pattern based on the resource managed by the
process and the goals of the actors (for details on this selection procedure, see the next
section). Apply the selected pattern to the set of identified processes.</p>
      <p>Applying a pattern to the set of identified processes will result in specifying the
internal structure of a process or relating processes to each other. In some cases, a
process is not retained but replaced by two or more new processes related to one or
more added actors. For example, a payment process between a buyer and a seller can
be restructured to include an intermediate additional actor (a bank) that participates in
new processes with both the buyer and seller. Application of patterns with this effect
means that the structure of the business model is also changed. In the following
section we elaborate on the concept of pattern and illustrate the use of a pattern library.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Patterns</title>
      <p>
        Patterns can be described from different points of view. From a model designer’s
perspective, they are off-the-shelf business processes that can be linked and chained
up to build more complex, end-to-end transactions. The UN/CEFACT Unified
Modelling Methodology [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] states that the use of patterns optimizes business process and
information model reusability, a precondition for this being that there is a pattern
corresponding to the requirements of the business collaboration. Let us consider a
sample pattern for a situation of goods’ delivery between a supplier and a distributor.
The UML activity diagram in Fig. 3 defines the dynamic aspects of business
collaboration. It describes the course of action and fixes a time window within which the
distributor must confirm the goods’ receipt. (More information on Timed Activity
Diagrams can be found in [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]).
The static aspects of the business collaboration, or rather the information content of
the business documents, are illustrated in the UML class diagram in Fig. 4. The
SHIPMENT_ADVICE document refers to a previous customer order and specifies the
exact delivery schedules and quantities for each line item of that order. The order
document is used in this context as a point of reference and links the goods’ delivery
activity to the larger business context of the overall transaction it is embedded in. The
chaining algorithm must ensure that relevant business information of the previous
collaboration phases are passed on to the delivery phase. Note that the same pattern
may be employed for a business case where the distributor would take ownership of
the goods, and thus all costs and risks associated with the transport. In this case, it
would be sufficient to modify the terms and conditions for the goods delivery in the
preceding order document. Patterns are always described by both its dynamic and
static properties.
      </p>
      <p>In business terms, patterns can be considered as instruments to achieve business
goals. Let us consider the example in Fig. 5:
A Supplier receives a purchase order from a Customer. Instead of invoicing the
Customer after the goods’ delivery, he sells his claim on the order value to a Factoring
Partner who pays him 80% of the value of the claim’s value upfront before he collects
the money from the Customer. This pattern solves several business purposes:
! For the Supplier, it fulfils a financing function as he receives his money upfront. It
also relieves him from the burden to collect his money from the Customer.
Whether there’s a delay in payment or the Customer goes bankrupt, he can be sure
to have 80% of the total order value.
! For the Factoring partner, he can either make a profit of 20% of the order value or
loose 80%. In order to reduce his risk exposure he would want to engage only in
the business with the Supplier, if the latter contracts him on a regular basis.
Given such a business case, we can derive the commercial conditions for the use of
our Factoring pattern: there need to be a Supplier who has regular trade with a
Customer and wants or needs – due to either a requirement for financing or because he
perceives the risk of non-payment with regards to the Customer in question as rather
high - to mitigate all payment-related risks by involving a Factoring partner.
Furthermore, the profit margin must be higher than 20 % in order to obtain an economically
sound Factoring solution.</p>
      <p>Generally speaking, we can associate all patterns with their business characteristics so
as to find the best pattern for any given business situation, and to evaluate the
pattern’s feasibility with regards to the business goals of the firms involved. There are
four categories of pattern characteristics:
! The collaboration phase it refers to. Some patterns (e.g. business processes for
price negotiations) apply to one collaboration phase of the Open-EDI model,
while others are more generic.
! The type of resource used in a business exchange. Patterns that can be used to
mitigate payment risks are in most cases not suited to deal with information
exchange or the transport of physical goods or services.
! Contractual characteristics:
- Patterns have specific characteristics with regards to their ability to manage
risks. While some patterns put all risks on a single business partner, others do
balance risks among the firms involved. An example of the latter is a letter of
credit. A specific aspect is the moment (and hence the risks associated with)
when the transfer of title on a resource passes from the seller to the buyer.
- Patterns can be described in terms of their cost allocation behaviour. Many
patterns, among which we find the Incoterms, define which party needs to pay
which part of the value creation activity.
! Process characteristics. This category subsumes the practical concerns related to
the execution of the business process the pattern describes: process efficiency,
duration as well as administrative and technical complexity of execution.
For each of these categories, there is a range of possible values, and each vector of
values (instances) maps onto a set of patterns that would fit the requirements.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Conclusion and Future Work</title>
      <p>In this paper we have discussed the problem of how to go from a business model to a
process model in a systematic way. A method is proposed that starts with a business
model where the main actors and their relationships, in the form of value exchanges,
are identified. In a number of steps, each value exchange is analysed and identified as
a sub-process that is to constitute the final process model. When analysing value
exchanges between business actors, we consider them as consisting of components,
which we call resource, right, custody, and document evidence. Each separate
component motivates a sub-process in the process model, and consequently a modeller
should decide whether to treat a value exchange as a unit or factor out one or several
of its components. Using a set of criteria, identified sub-processes are matched with
the complete process descriptions described in form of patterns stored in a library.
Use of the patterns enables a fast, module-based process design and stipulates the
alignment between the starting business model and the process model.</p>
      <p>Future research also involves investigations on how to properly use a pattern
library in this context. For instance, should the current content in the library decide the
design of the process model, or should the pattern library be used for validation
purposes when the modeller is finished, or both. Another topic for future research
includes further identifying and describing the dependencies that exist between
processes. These dependencies are expected to be useable means of deriving and
facilitating the selection of appropriate candidate patterns for implementing a particular
relationship, and consequently increase the quality of the resulting process model.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Wieringa</surname>
            <given-names>R.J.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Gordijn</surname>
            <given-names>J.</given-names>
          </string-name>
          , “
          <article-title>Value-Oriented Design of Service Coordination Processes: Correctness and Trust”</article-title>
          ,
          <source>ACM Symposium on Applied Computing</source>
          , Organizational Engineering Track,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Weigand</surname>
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johannesson</surname>
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Andersson</surname>
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bergholtz</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Edirisurya</surname>
            <given-names>A.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Ilayperyma</surname>
            <given-names>T.</given-names>
          </string-name>
          “
          <article-title>Value Object Analysis and the Transformation from Value Model to Process Model”. Accepted for publication at E-ISA'06 proceedings</article-title>
          . Bordeaux, France.
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Weigand</surname>
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johannesson</surname>
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Andersson</surname>
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bergholtz</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Edirisurya</surname>
            <given-names>A.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Ilayperyma</surname>
            <given-names>T.</given-names>
          </string-name>
          “
          <article-title>On the Notion of Value Object”. Accepted for publication in CAiSE'06 proceedings</article-title>
          . Luxemburg,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Jayaweera</surname>
            <given-names>P. “</given-names>
          </string-name>
          <article-title>A Unified Framework for e-Commerce Systems Development: Business Process Pattern Perspective (BP3)”</article-title>
          ,
          <source>PhD Thesis (ISBN 91-7265-938-6) Sept</source>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Andersson</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bergholtz</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Edirisuriya</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ilayperuma</surname>
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johannesson</surname>
            <given-names>P. “</given-names>
          </string-name>
          <article-title>A Declarative Foundation of Process Models”</article-title>
          ,
          <source>Proc. CAISE'05</source>
          , Springer-Verlag, LNCS,
          <year>2005</year>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Bergholtz</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grégoire</surname>
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johannesson</surname>
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schmitt</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wohed</surname>
            <given-names>P.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Zdravkovic</surname>
            <given-names>J.</given-names>
          </string-name>
          “
          <article-title>Integrated Methodology for linking business and process models with risk mitigation”</article-title>
          ,
          <source>REBNITA 05.</source>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Gordijn</surname>
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Akkermans</surname>
            <given-names>J.M.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Vliet J.C. van</surname>
          </string-name>
          , “
          <article-title>Business Modeling is not Process Modeling”, Conceptual Modeling for E-Business and the Web</article-title>
          ,
          <source>LNCS 1921</source>
          , Springer-Verlag pp.
          <fpage>40</fpage>
          -
          <lpage>51</lpage>
          ,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <article-title>8. UN-Centre for Trade Facilitation and Electronic Business, Open-EDI phases with REA</article-title>
          , http://www.unece.org/cefact/docum/download/02bp_rea.doc
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <article-title>9. UN-Centre for Trade Facilitation</article-title>
          and
          <string-name>
            <given-names>Electronic</given-names>
            <surname>Business</surname>
          </string-name>
          , Unified Modelling Methodology, http://www.untmg.org/
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Nicolas</surname>
            <given-names>Guelfi</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>Amel</given-names>
            <surname>Mammar</surname>
          </string-name>
          .
          <article-title>A Formal Semantics of Timed Activity Diagrams and its PROMELA Translation</article-title>
          ,
          <source>Asia Pacific Software Engineering Conference (APSEC'05)</source>
          , Taipei, Taiwan, IEEE Computer Society Press,
          <year>December 2005</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>