<!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>Towards Operationalization of Business Models: Designing Service Compositions for Service-Dominant Business Models</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Bambang Suratno Supervisors: Paul Grefen</string-name>
          <email>b.suratno@tue.nl</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Oktay Turetken</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>School of Industrial Engineering, Technical University of Eindhoven</institution>
          ,
          <addr-line>Eindhoven</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The new trend of service-dominant business which produces socalled value-in-use as a competitive advantage demands rapidly changing business models and collaboration of organizations in a cross-organizational business network. As information technology nowadays largely contributes to the way of delivering business services to the customers, strong alignment between business models and information technology is critical for business continuity and success. This means the rapidly changing business models necessitate quick adaptation of information systems to address the need to continually provide support for these business models. Current solutions and approaches fail to address this need to a large extent. Recent works, on the other hand, have brought key contributions and opened new research directions in designing servicedominant business. Accordingly, business models can be operationalized using service compositions that bring together loosely-coupled business services offered by the organizations collaborating in the business network. However, these works provide tools and techniques to structure the service-dominant business design only at the conceptual level or in a limited way. Therefore, there is a need for a structured, systematic, and repeatable method that will help organizations to implement service-dominant business models into business processes in the form of service compositions at the operational level.</p>
      </abstract>
      <kwd-group>
        <kwd>business model</kwd>
        <kwd>operationalization</kwd>
        <kwd>business process</kwd>
        <kwd>service composition</kwd>
        <kwd>service-dominant business</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>The new paradigm of Service-Dominant Business offers great potential in creating
new business value that attracts customers. While the conventional paradigm of Good
Dominant Logic business focused on goods, the value chain has now shifted towards
the service and solution and value network based paradigm, i.e. the Service Dominant
Logic paradigm [1]. There are important implications of following this transition [2].
First, customers will expect coherent solutions, not stand-alone solution fragments for
their needs. Therefore, integration of multiple service providers with different
capabilities is essential to create the service. Second, customer-driven requirements to
solution-oriented services evolve much faster than requirements to the underlying
products. Rapid technology developments in the field of information processing and
flexible telecommunication will further reinforce this process. Therefore, service
providers must be able to follow the complex and rapidly changing needs of the
customers. They must be agile in managing their business.</p>
      <p>While a business model is important as a guidance to manage the business [3],
conventional business modeling tools widely used by companies (e.g. Business Model
Canvas) cannot cover all domain of business. While these tools have been
acknowledged for their usefulness in their particular domain [4], they are not adequate to
fulfill the requirements of the Service-Dominant Business (SDB). The SDB requires a
network of parties to collaborate for co-creation of a particular business model and
therefore necessitates a network-centric approach to business modeling [5].</p>
      <p>As business models have short lifecycles, the underlying IT applications
supporting the business models should also adapt quickly as a response to these changing
business settings [2]. This is a requirement for business agility. Many information
systems, mainly those for the Web, are therefore being created as a means of offering
services over the Internet, usually involving simple or complex business processes in
which several participants are collaborating [6]. The participant activity in the
business process represents the business service provided by each of them, which are then
composed as a service composition. This way, the service providers can provide
complex functionality using a set of simpler functions available in the market [2].</p>
      <p>
        Therefore, methods of operationalizing business models in a service-dominant
business setting require a set of key business concepts to be tightly integrated and
aligned. These include, for instance, network-centric business models, business
services, service compositions, and process-aware information systems that execute the
compositions. There are a plethora of studies in the literature proposing approaches
that address these concepts in isolation or their alignment in limited scope [
        <xref ref-type="bibr" rid="ref12">2, 6–13</xref>
        ].
However, there is yet no structured method for operationalizing these concepts and
implementing them as process-aware information systems. The IT solutions
operationalizing business models still relies on ad-hoc approaches. Moreover, ideal
requirements of business services suitable for this type of service compositions have not
been investigated sufficiently.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Research Objective</title>
      <p>To address the research problem depicted above, we need a structured, systematic,
and repeatable method that will help organizations to implement service-dominant
business models at the operational level. This research study will address a part of this
need by proposing a method to align two key elements: business models and their
operationalization in the form of executable service compositions. By extending and
adopting approaches and tools in the Business Process Management (BPM) domain,
the method will help in establishing a concrete and clear relation between business
models and their operationalization, which will contribute to business organizations
agility. Accordingly, this study will address the following main research question:
“How to develop a structured method that will help a network of organizations to
operationalize service-dominant business models into business processes in the
form of service compositions given a set of predefined business services?”</p>
      <p>The efforts on discovering the right approach for operationalizing business models
can go through the different route of investigation. However, we assume a general
case where business models are transformed into business service compositions that
previously have been predefined and then represented as conceptual business process
models in the business viewpoint, which are then subsequently transformed into
executable designs that can run as process-aware information systems potentially on
business process management system (BPMS) platforms. Accordingly, our work can
be identified through these four sub-questions:
RQ1:How to transform a service-dominant business model into service compositions?
A service composition composes a particular set of business services, which together
provide the functionality to realize the value-in-use in a business model. A service
composition at the business level is an abstract business process, which shows the
elements (and their ordering) that collectively generates the value-in-use in the
business model. Currently, there is no standard approach or notation that can be used to
represent the underlying scenario of business models as abstract business processes.
The research on this question will focus on formulating the transformation process of
service-dominant business models into service compositions by applying these
approaches, and discover what needs to be adjusted to the existing approaches to
address the research problem.</p>
      <p>RQ2: What are the essential properties of the business services required in service
compositions?
When the long-term vision strategy realized into concrete medium-term vision
business model, we always need to consider the condition of business services. Therefore,
it is necessary to determine the ideal properties of the business services that will be
used in the design of service composition. In answering this research question, we
will discover the essential properties that lead to the suitable design of service
compositions which can support business agility.</p>
      <p>RQ3: How to formulate the executable service compositions?
In order to operationalize the model, several IT related details should be added to
make the business process executable. This carries the model from the business
pyramid to the operations pyramid. Therefore, the executable processes are specified in
such a way that the cross-organisational setting can be accommodated. The research
on this question will then focus on the formulation of executable business service
compositions of service-dominant business in a cross-organizational setting.
RQ4: How to evaluate the developed approach?
The developed method in this research aims to align and ease the connection between
business concepts and its implementation. The relevance of research results to the
application in business has become a key distinguishing feature of design science
research [14]. The method should be applicable and usable in practice. Therefore, it
should be implemented in real-life business settings. In order to evaluate the method
that we will propose by answering the first three research questions, we also need to
involve the components of the platform level, which provides the technical
infrastructure for the operationalization.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Related Work</title>
      <p>In this section, we summarize the related works concerning business model
operationalization. Arsanjani et al. [7] present a method to provide a service-oriented
solution (namely, SOMA), in which the transformation of business model is mentioned in
their conceptual development steps. Di Valentin et al. [8] define a method for
transforming business models into process models through the use of a component-based
business model which is subsequently transformed using four view process template.
Traganos and Grefen [2] propose a method for business model operationalization
using network-centric business models embedded in their BASE/X framework, in
which service composition is used to transform the complex network-centric value
creation into business process by composing a set of simpler value offering services.
However, these transformations do not continue to technical level and stay in the
business (process) level.</p>
      <p>
        Fayoumi and Laucopoulos [9] present conceptual modeling steps, which
transform a high-level business goal model into process model in nine steps. The major
contribution of this approach is that it brings simulation, design rationale and
enterprise modeling together in one framework. Weigand et al [
        <xref ref-type="bibr" rid="ref12">10</xref>
        ] shows that the services
at the business level and software-services are interrelated. They propose a service
design method that starts from a value model. This method can help to identify core
and enhancing services, and possible web services available for service compositions.
However, while the previous approach considered to achieve business agility, it does
not take the network-centric business setting into consideration. The latter approach
also did not specifically address this matter.
      </p>
      <p>
        Ulmer et al. [11] introduce a metamodel-centric methodology for BPM
integrating concepts from Model Driven Engineering (MDE), particularly from Model Driven
Architecture (MDA) [
        <xref ref-type="bibr" rid="ref24">15</xref>
        ], by evolving MDA-approach to a BPM-approach, in which
consist of Business Process Analyst (BPA) and Business Process Implementation
(BPI) model. This methodology allows business analysts to develop conceptual
models, generally graphical ones, in accordance with a formalised metamodel. It also
guarantees to IT specialist the conversion of a conceptual model to a block-structured
one (technical model) in order to ease its implementation on an execution platform.
We consider this structure comparable with the BASE/X framework (Fig. 1). This
approach has the advantage of establishing a loose coupling between process analysis
and process integration, however, it does not define how a high-level business model
can be transformed into a process model.
      </p>
      <p>A Service-Oriented Development Method (SOD-M) is a transformation method
for business model following the MDA approach (from CIM to PIM oriented service)
developed by Castro et al. [6]. Authors represent CIM level by using Business Process
Modelling Notation (BPMN) [16] for modeling business process, and by using
e3value model [12] for identifying services from the beginning in the business
perspective. This approach has the advantage of identifying services and business process at
CIM level in order to guide a semi-automatic transformation to PIM level. However,
the business model aspect is addressed in a limited way, where the requirements of
the service-dominant business are clearly addressed.</p>
      <p>Rhazali et al. [13] propose a CIM to PIM transformation method with clear
transformation rules using graphic presentation. Based on the MDA, this approach
provides a solution to the problem of transforming business models represented in CIM
level to analysis and design models, modeled in PIM level. However, while the IT
aspects are highly emphasized, the use of the business practitioners-friendly
highlevel business model is not adequately addressed.</p>
      <p>
        We can categorize the works on business model operationalization as follows:
• We refer to approaches [2, 8, 9] that attempt to use a high-level business model
as the starting point of the transformation. However, these approaches do not
proceed to the implementation of the solution. In [9] the authors propose an
interesting approach concerning the transformation of business models to process
models, however, the authors only provide the conceptual model and do not
address the necessity of network-centric business settings.
• Other works, such as [13] focus more on the technical aspects, i.e. on the
transformation of the process models, but do not particularly necessitate business
models as the starting point.
• Another category of works considers a loose-coupling arrangement that leads to
business agility in process model transformation [11].
• There are also studies, such as [
        <xref ref-type="bibr" rid="ref12 ref18">10, 17–19</xref>
        ], that introduce relevant concepts but
only partially address the key elements and challenges in operationalizing
service-dominant business models.
• Finally, there are approaches, such as [6], which propose precise transformation
methods but address business model aspects in a limited way.
4
      </p>
    </sec>
    <sec id="sec-4">
      <title>Research Methodology</title>
      <p>This research project follows the design-science research paradigm for information
system discipline [20]. It will contribute mainly to the service-dominant business field
that can be considered to have a low application domain maturity. We will adopt and
extend existing solutions (e.g. BPMN) to this domain, while also use the recently
developed BASE/X framework as the basis for a solution. Given this problem
context, the steps in the research procedure [14] can be listed as follows (Fig. 2):
1. Literature
review</p>
      <p>Design
2. Develop the
method as a</p>
      <p>solution
Evaluation
3. Evaluate
through
cases/scenarios
4. Improve/
Re-design the
method
5. Evaluate
through case
studies
6. Reflection</p>
      <p>and
Communication</p>
      <p>Fig. 2. The DSR Methodology applied to our research (adapted from [14])
4.1</p>
      <sec id="sec-4-1">
        <title>Step 1. Literature review</title>
        <p>Prior work relevant to the study (including existing tools and methods that have
already been developed to solve similar problems) is currently being reviewed using
systematic literature review [21] to get a better understanding of the state-of-the-art
contributions and research gaps in this relatively new domain of service-dominant
business.
4.2</p>
      </sec>
      <sec id="sec-4-2">
        <title>Step 2. Develop the method as a solution</title>
        <p>This task will form a critical component of the research work in which the proposed
method - as a design artefact- will be developed based on the findings from the
systematic literature review, critical analysis of existing methods, tools and solutions,
prototype implementations and evaluations, as well as the (domain) knowledge we
gathered in a number of industry and research projects (including EU supported
H2020 projects) that we are involved in. The execution of this task will lead to an
initial (alpha) version of the proposed method and will address the first three
research questions. To this end, we will first develop the overall requirements for the
proposed method. Next, we will develop a set of structured steps for transforming a
service-dominant business model into conceptual service compositions (RQ1). In
doing so, we will also identify the essential properties of business services required in
service compositions (RQ2). Finally, we will develop guidelines as- a part of the
method- that will help in transforming conceptual service compositions into concrete
executable ones (RQ3), which will provide a key input for the implementation of
process-aware IS and their deployment on related IT platforms, eventually realizing
the business models. This step will be accompanied by the development of prototype
implementations of sample realistic business models for explorations and testing of
alternative solution fragments and tools.
4.3</p>
      </sec>
      <sec id="sec-4-3">
        <title>Step 3. Evaluate the method through business cases/scenarios simulation</title>
        <p>The utility, quality, or efficacy of a design artefact must be rigorously demonstrated
via well-executed evaluation methods [14]. This research will use an iterative
approach that includes intermediate testing and evaluation in the development process.
The alpha version of the proposed method will be evaluated using business cases and
realistic scenarios (gathered in previous industry projects) to test its validity and
applicability and to gather immediate feedback for further improvement of the method.
The objective is to investigate the alpha version of the proposed method and relevant
techniques/tools for their effectiveness in operationalizing business models, starting
with business model blueprints and ending with a process-aware information system
that supports its execution. This will also address partially the fourth research
question (RQ4).
4.4</p>
      </sec>
      <sec id="sec-4-4">
        <title>Step 4. Improve/re-design the method</title>
        <p>The first round of evaluation will provide feedback for the improvement (or, if
necessary, redesign) of the proposed solution. The proposed method will be updated and
finalized accordingly. This step will lead to a final (beta) version of the method,
which will be expected to address the first three research questions. The proposed
method will then be ready to go through a final round of evaluations using new
reallife cases.
4.5</p>
      </sec>
      <sec id="sec-4-5">
        <title>Step 5. Evaluate the method through case studies</title>
        <p>In the last round of evaluation, the final (beta) version of the proposed method will be
applied in one or two real-life business cases to assess its validity and utility, i.e., to
test if the method works, if it achieves its goals successfully, and if the results can be
generalizable/achievable also in other business settings. These cases will originate
from one of our projects in the mobility domain or from one of our industry projects
in the logistics &amp; transportation, or traffic management domains. Unlike the first
evaluation, in this step, the method will be applied in a larger scope and will
accommodate the involvement of experts and practitioners. The evaluation will involve not
only the assessment of the end-result (operationalized business model) but also the
elicitation of the views of the people (experts and practitioners participated in the
case) on how successful and effective they perceive the method was. This process will
be the second iteration step in addressing RQ4.
4.6</p>
      </sec>
      <sec id="sec-4-6">
        <title>Step 6. Reflection and Communication</title>
        <p>Step two to five is an iterative process in designing and evaluating the proposed
method. By doing that, we can reflect on the limitations and other adjustments that are
necessary for the implementation of the method, which complements the research
design.
5</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Proposed Method and Work Progress</title>
      <p>A Service-Dominant Business Model Radar (SDBM/R) [22] is a tool - used for the
high-level design of business models, integrated into the BASE/X (Business Agility
through Cross-Organizational Service Engineering) framework [23]. BASE/X is a
business engineering framework that is tuned to the basics of service-oriented
business [24] and built on the existing works on business design and engineering [25–28].
BASE/X framework conceptually covers the entire spectrum from high-level business
strategy definition to business information system architecture design, including
elements like business model design, business service specification, and their
composition into business processes. The framework incorporates three pyramids, namely
business, operations, and platform. Each pyramid consists of 4 layers: Strategy (S),
Business Model (BM), Service Composition (SC), and Business Service (BS) (Fig. 3).</p>
      <p>BASE/X proposed a conceptual alignment between all layers and pyramids of the
framework, offering a high-level guidance to traverse from different levels of the
pyramids. However, this alignment should be further delineated into concrete and
structured methods in order for the framework to be effectively applied in practice.
With respect to the BASE/X framework, our aim is to address our research questions
by following a certain trajectory as depicted in Fig. 3.</p>
      <p>Different trajectories across these pyramids can be followed to fulfill the
objectives of this research. The trajectory that we chose – as depicted in Fig. 3, follows the
line of thinking adapted in the existing works related to the operationalization of
business models (e.g. [6][9]). In this trajectory, the service compositions are defined at all
pyramids (business, operation, and platform) and at different granularity and
abstraction levels. Consequently, the research may rely on separate (but to be integrated)
composition approaches at each level.</p>
      <p>On-going research corresponds to the first and second step of the research design
(as given in Fig. 2), which are: (1) review of the existing literature; and (2) design of
the proposed method. For the first objective, based on the research questions, a
systematic literature review has been conducted. The initial strategy employed in the
review was to find as many as possible relevant scientific publications and then
narrow down the results by predefined acceptable criteria. Simultaneously, the proposed
method is being developed by iteratively improving the initial concept using a
reference from literature study and testing it in BPMN based business process
management systems.
6</p>
    </sec>
    <sec id="sec-6">
      <title>Conclusion and Perceived Contributions</title>
      <p>This research aims to create a bridge between the business model of an organization
and its operationalization to the level of information system implementation to cover
a wide spectrum of service-dominant business design. This will be achieved by
utilizing process-aware information systems. Therefore, it will contribute knowledge to the
Business Process Management field. After organization formulates their business
strategy into business models and business services that can be composed into
business processes at the conceptual business level, the next step in this context is to
realize this set of conceptual models at the operational level, by using BPMN to develop
the process-aware information systems. Therefore, developing an approach to address
this problem will lead to a more effectively implemented Service-Dominant Business
concept, which will contribute to Service Science research domain.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>Lusch</surname>
            ,
            <given-names>R.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vargo</surname>
            ,
            <given-names>S.L.</given-names>
          </string-name>
          :
          <article-title>Service-dominant logic: reactions, reflections and refinements</article-title>
          .
          <source>Mark. Theory. 6</source>
          ,
          <fpage>281</fpage>
          -
          <lpage>288</lpage>
          (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>Traganos</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grefen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Hybrid Service Compositions: When BPM Meets Dynamic Case Management</article-title>
          .
          <source>In: Int. Federation for Information Processing</source>
          . pp.
          <fpage>226</fpage>
          -
          <lpage>239</lpage>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <surname>Zott</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Amit</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          :
          <article-title>The Business Model: A Theoretically Anchored Robust Construct for Strategic Analysis</article-title>
          .
          <source>Strateg. Organ</source>
          .
          <volume>11</volume>
          ,
          <fpage>403</fpage>
          -
          <lpage>411</lpage>
          (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <surname>Osterwalder</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pigneur</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Business model generation: A handbook for visionaries, game changers and challengers</article-title>
          . John Willey &amp; Sons, Inc., New Jersey (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>Luftenegger</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Service-Dominant Business</surname>
            <given-names>Design</given-names>
          </string-name>
          ,
          <source>PhD Thesis</source>
          , (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <surname>De Castro</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marcos</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wieringa</surname>
          </string-name>
          , R.:
          <article-title>Towards a service-oriented MDA-based approach to the alignment of business processes with it systems: From the business model to a web service composition model</article-title>
          .
          <source>Int.J. Coop. Inf. Syst</source>
          .
          <volume>18</volume>
          ,
          <fpage>225</fpage>
          -
          <lpage>260</lpage>
          (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <string-name>
            <surname>Arsanjani</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghosh</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Allam</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Abdollah</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ganapathy</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Holley</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>SOMA: A method for developing service-oriented solutions</article-title>
          .
          <source>IBM Syst. J</source>
          .
          <volume>47</volume>
          ,
          <fpage>377</fpage>
          -
          <lpage>396</lpage>
          (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <string-name>
            <given-names>Di</given-names>
            <surname>Valentin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Burkhart</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Vanderhaeghen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Werth</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Loos</surname>
          </string-name>
          ,
          <string-name>
            <surname>P.</surname>
          </string-name>
          :
          <article-title>Towards a Framework for Transforming Business Models into Business Processes</article-title>
          .
          <source>In: AMCIS 2012 Proceedings</source>
          . p.
          <volume>10</volume>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <string-name>
            <surname>Fayoumi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Loucopoulos</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Conceptual modeling for the design of intelligent and emergent information systems</article-title>
          .
          <source>Expert Syst. Appl</source>
          .
          <volume>59</volume>
          ,
          <fpage>174</fpage>
          -
          <lpage>194</lpage>
          (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          Intell. Lect. Notes Bioinformatics).
          <source>5565 LNCS</source>
          ,
          <fpage>410</fpage>
          -
          <lpage>424</lpage>
          (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          <string-name>
            <surname>Ulmer</surname>
            ,
            <given-names>J.-S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Belaud</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Le</surname>
            <given-names>Lann</given-names>
          </string-name>
          , J.-M.:
          <article-title>Towards a pivotal-based approach for business process alignment</article-title>
          .
          <source>Int. J. Comput. Integr. Manuf</source>
          .
          <volume>24</volume>
          ,
          <fpage>1010</fpage>
          -
          <lpage>1021</lpage>
          (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          <string-name>
            <given-names>Its</given-names>
            <surname>Appl</surname>
          </string-name>
          .
          <volume>10</volume>
          ,
          <fpage>125</fpage>
          -
          <lpage>142</lpage>
          (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          <string-name>
            <surname>Gregor</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hevner</surname>
            ,
            <given-names>A.R.</given-names>
          </string-name>
          :
          <source>Positioning and Presenting Design Science Types of Knowledge in Design Science Research. MIS Q</source>
          .
          <volume>37</volume>
          ,
          <fpage>337</fpage>
          -
          <lpage>355</lpage>
          (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          <string-name>
            <surname>Miller</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mukerji</surname>
          </string-name>
          , J.:
          <source>MDA Guide Version 1.0.1</source>
          . (
          <year>2003</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          <article-title>OMG: Business Process Model and Notation (BPMN) Version 2</article-title>
          .0, (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          pp.
          <fpage>215</fpage>
          -
          <lpage>227</lpage>
          . Springer International Publishing,
          <string-name>
            <surname>Cham</surname>
          </string-name>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          <string-name>
            <surname>Jamshidi</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Khoshnevis</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Teimourzadegan</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nikravesh</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shams</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Toward automatic transformation of enterprise business model to service model</article-title>
          .
          <source>Workshop on Principles of Engineering Service Oriented Systems</source>
          <year>2009</year>
          . pp.
          <fpage>70</fpage>
          -
          <lpage>74</lpage>
          . IEEE (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          J.
          <volume>18</volume>
          ,
          <fpage>655</fpage>
          -
          <lpage>679</lpage>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          <string-name>
            <surname>Hevner</surname>
            ,
            <given-names>A.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>March</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Park</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ram</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <source>Design Science in Information Systems Research. MIS Q</source>
          .
          <volume>28</volume>
          ,
          <fpage>75</fpage>
          -
          <lpage>105</lpage>
          (
          <year>2004</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          <string-name>
            <surname>Kitchenham</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Guidelines for Performing systematic literature reviews in software engineering</article-title>
          . (
          <year>2007</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          <string-name>
            <surname>Grefen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Turetken</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Traganos</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>den Hollander</surname>
          </string-name>
          , A.,
          <string-name>
            <surname>Eshuis</surname>
          </string-name>
          , R.:
          <article-title>Creating Agility in Traffic Management by Collaborative Service-Dominant Business</article-title>
          .
          <article-title>PRO-VE 2015 Albi, Fr</article-title>
          . Oct.
          <volume>5</volume>
          -
          <issue>7</issue>
          ,
          <year>2015</year>
          Proceeding.
          <volume>463</volume>
          ,
          <fpage>100</fpage>
          -
          <lpage>109</lpage>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          <string-name>
            <surname>Grefen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Service-Dominant Business Engineering with BASE/X - Business Modeling Handbook</article-title>
          .
          <source>Amazon Distribution</source>
          , Leipzig, Germany (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          <string-name>
            <surname>Lusch</surname>
            ,
            <given-names>R.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vargo</surname>
            ,
            <given-names>S.L.</given-names>
          </string-name>
          :
          <article-title>The Service-Dominant Mindset. Service Science, Management and Engineering Education for the 21st Century</article-title>
          . pp.
          <fpage>89</fpage>
          -
          <lpage>96</lpage>
          . Springer US, Boston, MA (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          15th
          <string-name>
            <given-names>Bled</given-names>
            <surname>Electron</surname>
          </string-name>
          .
          <source>Commer. Conf. June 17-19</source>
          . 12 (
          <year>2002</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          <string-name>
            <surname>Sanz</surname>
            ,
            <given-names>J.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Becker</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cappi</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chandra</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kramer</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lyman</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nayak</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pesce</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Terrizzano</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vergo</surname>
          </string-name>
          , J.:
          <article-title>Business services and business componentization: New gaps between business and IT</article-title>
          . SOCA
          <year>2007</year>
          .
          <volume>271</volume>
          -
          <fpage>278</fpage>
          (
          <year>2007</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          <string-name>
            <surname>Al-Debei</surname>
            ,
            <given-names>M.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>El-Haddadeh</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Avison</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Defining the Business Model in the New World of Digital Business</article-title>
          .
          <source>Proc AMICS 2008</source>
          .
          <volume>1</volume>
          -
          <fpage>11</fpage>
          (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          <string-name>
            <surname>Al-Debei</surname>
            ,
            <given-names>M.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Avison</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Developing a unified framework of the business model concept</article-title>
          .
          <source>Eur. J. Inf. Syst</source>
          .
          <volume>19</volume>
          ,
          <fpage>359</fpage>
          -
          <lpage>376</lpage>
          (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>