<!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>A Survey of Roles and Responsibilities in Ecosystems Chen Hsi Tsaia and Jelena Zdravkovica</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Stockholm University Department of Computer and Systems Sciences</institution>
          ,
          <addr-line>Borgarfjordsgatan 12, Kista Stockholm</addr-line>
          ,
          <country country="SE">Sweden</country>
        </aff>
      </contrib-group>
      <fpage>44</fpage>
      <lpage>53</lpage>
      <abstract>
        <p>Digital Business Ecosystem is an emerging phenomenon aimed to reflect the behavior of natural ecosystems as a networked and online business model involving heterogeneous actors being engaged in a shared business vision and its implementation. Such as in an ecosystem, in a DBE, the actors are highly dependent on each other in terms of their capabilities and resources. It is, therefore, one of the essential needs for the research on DBEs to advance in understanding of which roles and responsibilities are entailed in enabling a DBE to function and sustain on a long-term basis. We have, in this study, performed a survey on the existing scientific studies related to the roles within DBEs, classified the collected results, and integrated them to a unified proposal. Using a recently developed and functioning DBE concerning the improvement of preventive healthcare by provisioning, exchanging, and using of a set of relevant resources, we have presented an initial validation of the correctness and fit of the proposal for the roles of actors and their responsibilities.</p>
      </abstract>
      <kwd-group>
        <kwd>1 Digital Business Ecosystem</kwd>
        <kwd>Role</kwd>
        <kwd>Resource</kwd>
        <kwd>Capability</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Digital Business Ecosystem (DBE) is a paradigm that has emerged in the recent years to enable
describing, developing, and monitoring novel business models. A digital business ecosystem is an
Internet-connected network of the organizational and individual actors engaged in the delivery and use
of a product or a service through cooperation. The notion is based on Moore's concept of Business
Ecosystem that, by following the notion of the ecosystem, is a complex system involving a
coevolutionary economic community of the organisms in the business world [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>
        Being different from traditional multi-actor business models such as manufacturer, retailer, or
franchise centered, using a shared digital environment, DBE implies heterogeneity, symbiosis,
coevolution, and self-organization of the involved actors, which enables it to span different business
domains as well as to exhibit diverse interests [
        <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
        ]. For many organizations and individuals, DBE
presents a novel collaborative approach to leverage offered and desired resources and enabling
capabilities across the involved members to meet each of their goals. As such, it is foreseen to be of
high value to the involved actors, but at the same time it is often complex and difficult to manage due
to many correlated or dependent interactions and interrelationships among actors [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>One of the essential aspects of DBE concerns understanding of the responsibilities of the involved
actors in regard to their different capabilities and offering and need for resources that make it possible
for an ecosystem to function and sustain according to its nature. As observed in an ongoing systematic
literature review of DBE analysis and design conducting by the authors, the DBE-related scientific
research has, so far, presented and described relevant roles, where the roles correspond to the DBE
specific responsibilities of the actual involved actors. For certain roles, the proposals match; while, for
others, they differ.</p>
      <p>
        The aim of this study has been to, by presenting a survey of the existing literature and research
results concerning DBE roles, classify and unify the elicited roles and identify their corresponding
responsibilities to provide a basis for modeling using a language. In order to provide an initial validation
of the proposed DBE roles, we have examined their correctness and fit in a real case related to the
Digital Vaccine DBE [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] consisting of heterogeneous actors, their complex interactions, capabilities,
and exchanged resources occurring in the interest of providing a collective outcome - good quality
preventive care to the citizens.
      </p>
      <p>The task of unifying the roles and their corresponding responsibilities is one of the essential steps in
order to understand how DBEs function in a multi-actor constellation and how a modeling language
can, in turn, be defined to support the analysis, design, and run-time management of DBEs. The
proposal for roles and responsibilities in DBEs can served as a framework to analyze what roles are
needed in a DBE, what roles an actor in the DBE can take on, what the actor is expected to fulfill in
terms of responsibilities, resources, capabilities, etc. to support the functioning of the DBE.</p>
      <p>The rest of the paper is structured in the following way: Section 2 reports a literature survey on DBE
roles. Following that, Section 3 presents our effort and results for classifying and unifying identified
roles, followed by an examination of their correctness and completeness in the Digital Vaccine DBE.
A discussion of the results and concluding remarks is presented in section 4.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Background</title>
      <p>
        The literature used in this study was a subset of 8 articles based on an ongoing systematic literature
review (SLR) focusing on analysis and design of DBE. Following the guidelines and principles
suggested by Kitchenham and Charters [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] and the Cochrane Handbook [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] as well as the PRISMA
checklist, searches were conducted in electronic databases, namely Scopus, IEEE Xplore, ACM Digital
Library, Web of Science, EBSCOhost, and ProQuest. Additionally, forward and backward searches
were conducted to compensate the risk of missing relevant articles. Inclusion and exclusion criteria
were applied during study selection, including the screening of titles and abstracts and the assessment
of full-text articles. A total number of 3509 candidate records were retrieved, whereof 63 articles were
included in the final qualitative analysis. For this study, we looked into the 63 articles and extracted
those which elaborated on actors and roles within DBEs. In total, 8 articles were included in this study.
      </p>
      <p>
        Since the concept of digital business ecosystem has its basis on Moore’s business ecosystem [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], we
started by looking into the roles of actors within BEs. Moore suggested that roles in BEs include
leadership company, competitor, supplier, customer, and governmental institution. Iansiti and Levien
[
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] proposed a strategic view when classifying the roles of actors in BEs with three roles, namely
keystone, niche player, and dominator. A keystone refers to an actor who actively looks over the whole
ecosystem's health, focuses on creating platforms, and guides the balance of value sharing and
extraction. A niche player refers to an actor who focuses on developing capabilities and creating values
in specialized areas within an ecosystem. A dominator refers to an actor who aims to control and own
a large part of an ecosystem through vertical and horizontal integration.
      </p>
      <p>
        Several studies which concern digital and technological aspects of ecosystems suggested different
roles of actors in DBEs. Combining the fundamentals of Moore’s [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] and Iansiti and Levien’s roles of
BE actors [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], Senyo et al. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] argued that, in DBEs, partners fit into the roles of keystone,
complementor, and customer. A complementor refers to an actor who creates or improves its product
and service innovations by using assets in a DBE. A customer refers to an actor who consumes value
created in a DBE as a recipient of a DBE’s interdependence efforts and a source of revenue for the
value. The authors posited that not all these roles may be present in every DBE. The interdependency
among DBE partners was analyzed together with resources and activities. In another study, Senyo et al.
[
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] suggested four categories of partners in DBEs: actor, client, provider, and regulator. An “actor” is
an entity/actor who provides core processes within a DBE. A client represents an actor who benefits
from a DBE’s efforts. A provider refers to an actor who offers resources for the operation of a DBE. A
regulator refers to an actor who provides guidelines that govern other partners in a DBE. Wieringa et
al. [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] addressed six roles: supplier, customer, competitor, complementor, rule maker, and association
based on Moore’s idea [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] and Brandenburger and Nalebuff’s view of members in an ecosystem [11].
A rule maker refers to an actor who defines the normative context within a DBE. The actor can represent
a government organization, a regulatory agency, or a standard body. An association refers to an actor,
such as a trade association, a labor union, or a special interest group, who provides mechanisms in a
domain. Radonjic-Simic and Pfisterer [12] argued that there are six DBE roles that actors can take,
including consumer, provider, technology provider, knowledge provider, advisor/mediator, and
reputation bank. Each role has its responsibilities within DBEs. A consumer is an actor who has
particular needs and requests for products and/or services. A technology provider refers to an actor who
provides technology, software or hardware, resources to support a DBE. A knowledge provider refers
to an actor who provided structured and useful knowledge for a specific domain. An advisor/mediator
refers to an actor who also provides knowledge and expertise to support decision making and dispute
resolving. A reputation back represents an actor who assesses reputations of actors within a DBE. Weill
and Woerner [13] proposed two roles, namely ecosystem driver and modular producer, in an ecosystem
design of the digital business model framework. An ecosystem driver represents an actor who organizes
a coordinated network, i.e., an ecosystem, to create value for all actors within the ecosystem. A modular
producer refers to an actor who provides “plug-and-play products or services” within a DBE. Giesecke
[14] suggested five roles, including input provider, enabler, aggregator and provider, governor, and end
user, in a domain specific DBE, an electric mobility business ecosystem. An input provider refers to an
actor who provides inputs, such as energy, information, ideas, and funding, which can change during
subsequent processes. An enabler refers to an actor who provides assets which do not change
subsequently. An “aggregator and provider” is an actor who combines and aggregates inputs into
products or services for end users. A governor refers to an actor who governs a DBE by defining and
providing standards, laws, or policies. An end user is an actor who consumes products and/or services
and may provide feedback and/or payment to others within a DBE.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Results</title>
    </sec>
    <sec id="sec-4">
      <title>3.1. Classification of the Roles Identified in the Literature</title>
      <p>In total, 27 roles were identified based on the literature summarized in section 2. These roles were
compared and classified into groups in Table 1 according to their similarities.</p>
      <p>As shown in the first column of Table 1, the roles: Leadership Company, Keystone, and Ecosystem
Driver were placed in the same group, Group 1: Driver, since they all have the characteristics of
organizing, guiding, and looking over all actors within an ecosystem and concern value creation and
balance. Aggregator and Provider shares some similarities with this group as it organizes, in terms of
aggregating and combining, multiple resources within an ecosystem into products and services.
However, it does not deal with leading a whole ecosystem with all involved actors. Consequently, the
role aggregator and provider were placed in its own group, Group 2: Aggregator.</p>
      <p>The roles: Supplier, Provider, Technology Provider, Knowledge Provider, Advisor/Mediator,
Modular Producer, Input Provider, Enabler and Niche Player share similarities as they pertain to the
development of capabilities and offering of resources, such as products, services, technologies,
knowledge, financial funding, etc., in an ecosystem. Therefore, these roles were classified in one group,
Group 3: Modular Producer. Even though the role of a Complementor resembles the role of a Niche
Player who develops capabilities and creates values in specialized areas within an ecosystem, we argue
that a Complementor is different from Supplier and Provider because its offerings as complements add
extra value to the core resources of an ecosystem and these complements are often bundled by end users
[15]. As a result, the role Complementor was separated into its own group, Group 4: Complementor.</p>
      <p>Customer and Client are the beneficiaries of an ecosystem’s efforts and the sources of revenue as
they pay for resources in an ecosystem. Whereas, Consumer and End User consume resources based on
specific needs and provide feedback to other ecosystem actors. Hence, we placed the roles Customer
and Client in one group, Group 5: Customer, and Consumer and End User in another, Group 6: End
User.</p>
      <p>The roles: Governor, Governmental Institution, Rule Maker, Regulator, Association were classified
in the same group, Group 7: Governor, since they all share the characteristic of defining normative
contexts, such as laws, policies, guidelines, and mechanisms, in an ecosystem.</p>
      <p>The remaining roles: Reputation Bank, Actor, Dominator, and Competitor were each placed in its
own group, respectively, Group 8: Reputation Guardian, Group 9, Group 10, and Group 11, as they do
Group 1: Driver
Leadership Company
Keystone
Ecosystem Driver
Group 2: Aggregator
Aggregator and Provider
Group 3: Modular
Producer
Supplier
Provider
Technology Provider</p>
      <sec id="sec-4-1">
        <title>Knowledge Provider Advisor/Mediator Modular Producer Input Provider</title>
        <p>Enabler
Niche Player
Group 4: Complementor
Complementor
Group 5: Customer
Customer
Client</p>
      </sec>
      <sec id="sec-4-2">
        <title>End User Consumer Group 6: End User x</title>
        <p>
          x
x
[
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]
x
x
x
[
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]
x
not share similarities with other roles. However, we argue that the role “Actor” encompasses all the
other roles as they all contribute to important processes in an ecosystem.
(continued on next page)
Group 7: Governor
Governor
Governmental Institution
        </p>
        <p>x
Rule Maker
Regulator
Association
Group 8: Reputation
Guardian
Reputation Bank
Group 9
Actor
Group 10
Dominator
Group 11
Competitor</p>
        <p>x
3.2.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Proposal of the DBE Roles and Responsibilities</title>
      <p>Based on the classification of the 27 roles in Table 1 and the surveyed literature, we proposed a list of
eight DBE roles -- namely Driver, Aggregator, Modular Producer, Complementor, Customer, End User,
Governor, and Reputation Guardian -- and their responsibilities in DBEs as shown in Table 2. Some of
the names of the roles have their close synonyms according to the surveyed literature, such as Provider
as for Modular producer; in such cases we were choosing the name that was more specific and unique
for DBE. A DBE role refers to an actor who takes on the corresponding DBE specific responsibilities
within a digital business ecosystem. Based on the literature definitions and/or descriptions of all roles
in each group (as in Table 1), the responsibilities of each proposed role in Table 2 were synthesized and
rephrased.
d1. It has the responsibility to set up a common vision for all actors in a DBE.
d2. It has the responsibility to guide all DBE actors toward a common vision.
d3. It has the responsibility to look over and improve the overall health - growth,
survival, and reputation of a DBE.
d4. It has the responsibility to provide and manage a digital platform.
d5. It has the responsibility to optimize entry barriers for joining a DBE.
d6. It has the responsibility to acquire and retain actors within a DBE.</p>
      <p>x</p>
      <sec id="sec-5-1">
        <title>Aggregator</title>
      </sec>
      <sec id="sec-5-2">
        <title>Modular Producer Complementor Customer</title>
        <p>d7. It has the responsibility to provide end-products and/or services to customers
and/or end users by integrating both its own capabilities and resources as well as
those of other actors within a DBE.
d8. It has the responsibility to collect and raise end users’ events and feedback.
d9. It has the responsibility to ensure an integrated end user experience.
a1. It has the responsibility to aggregate capabilities and resources within a DBE
into comprehensive products or services, which are aimed for end-users.
m1. It has the responsibility to, using its capabilities, provide resources within a
specialized domain of a DBE. A resource can be a product, or a service, or
knowledge, or money, which is enabled by one or more of the producer's
capabilities.
c1. It has the responsibility to, using its capabilities, provide resources that
complement the core resources (products, services, knowledge, money) offered in
a DBE, with some added-value features.
c2. It has the responsibility to buy one or more resources created in a DBE.
e1. It has the responsibility to consume one or more resources offered in a DBE.
e2. It has the responsibility to provide the information about its events and
feedback to other roles within a DBE, through Driver.
g1. It has the responsibility to govern all actors within a DBE by providing and/or
defining the standards, laws, policies, guidelines, norms, and ethics related to the
business concern of DBE.
r1. It has the responsibility to survey and assess all DBE actors' trustworthiness,
reliability, solvency, and worthiness.</p>
        <p>In addition to the unification of the DBE roles and their responsibilities in Table 2, we have
concluded the following:</p>
        <p>Neither Dominator nor Competitor is a DBE role because they do not concern the responsibilities
related to DBE functionality or quality. Dominator describes a rule-over relation of a DBE actor towards
the other DBE actors, whereas Competitor describes a relation of a DBE actor to the DBE actor(s)
offering or consuming the same resource(s).</p>
        <p>DBEs may be substantially different in their characteristics of exchanged resources and size in terms
of the number of involved actors. Following the surveyed literature, we recognize Driver, Modular
Producer, Customer, and End User as the essential roles for a DBE to function. The roles and the
responsibilities of Aggregator, Complementor, Governor, and Reputation Guardian are given to the
actors of an DBE when there is a need or a collective decision that they should be proclaimed. Also,
depending on the size and maturity of a DBE, an actor who takes on, or is given a DBE role within the
DBE, might not be able to realize all its responsibilities at the same time. It is important that, as the
DBE develops over time, the actor will gradually be able to fulfill all these responsibilities.
3.3.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Digital Vaccine: a Digital Business Ecosystem</title>
      <p>
        For the initial validation of the proposed DBE roles and responsibilities, we used an industrial case of
a Digital Vaccine DBE [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. The Digital Vaccine DBE consists of multiple heterogeneous actors, such
as health service providers, the digital vaccine company (Health Integrator AB, “HI”), private
employers and their employees as individual users, public sectors, etc. The vision of the Digital Vaccine
DBE is to shift the focus in healthcare to personal tailored preventive care with a health outcome-based
contracting model.
      </p>
    </sec>
    <sec id="sec-7">
      <title>4. Discussion, Conclusions, and Future Work</title>
      <p>In this study, we have presented a proposal for the roles and their responsibilities for DBE by collecting
and unifying the existing literature; in addition, we have examined the fit of the proposal on a real DBE
concerning creation and offering of Digital Vaccine for better health care.</p>
      <p>The performed survey has shown that despite the fact that research on DBE modeling, design, and
monitoring is still ongoing, a notable number of studies have been addressing the roles of the involved
actors. This shows that identifying distinguishing responsibilities in a DBE is an essential aspect for its
functionality and management. Also, eliciting and understanding the responsibilities needed in a
business model, in this case -- a complex, networked and with diverse types of actors, is the basis for
determining the capabilities required for specific roles, as well as their use of the resources that
characterize the ecosystem. This can further enable modeling of role-based capabilities which is highly
important in design of heterogeneous and complex IS, and where adaptations for different runtime
contexts are needed [18].</p>
      <p>The conducted survey has shown that the current DBE related research acknowledges the elementary
roles used in service and product exchange environments, but, in addition, proposes a number of other
roles that are specific to initialization of a DBE, onboarding of the actors, the care of the platform,
dissemination of knowledge, policies, and ethics, assurance of quality of exchanged resources, and
many other. We have in the study made an effort to integrate and unify the identified roles, as well as
to classify their responsibilities. Further, we contrasted the proposal with a model of an existing DBE
concerning provisioning of a diapason of physical and cyber resources to organizations and individuals
for the preventive self-care improvement purpose. A detailed analysis and discussion of the capabilities
and the resources of the Digital Vaccine DBE, has shown that a) the proposed roles covered all the
involved actors and their responsibilities identifiable in the model, and b) that some of the roles are not
presented. The latter can be explained by the fact that the case has been recently implemented and that
the number of actors is still relatively small, hence the capabilities for a refined and sustainable
management of the ecosystem corresponding to some of the non-essential roles are still in a planning
phase. Nevertheless, they are considered as a valuable guidance of how to ensure further improvements
in terms of stability and resilience of the ecosystem.</p>
      <p>Our further work will focus on investigating how the proposal for roles and responsibilities in DBEs
can be extended to support different scenarios and domains. As a way of implementing the proposal,
we will also focus on defining a modeling language for design and run-time management of DBE; for
that research, a continuous analysis, definition, and validation of responsibilities of DBE actors to
improve and expand the proposal has been recognized as one of main tasks.
5. References
Institute of Electrical and Electronics Engineers Inc., Moscow, Russia, 2019, pp. 147–156.
doi:10.1109/CBI.2019.00024.
[11] A. Brandenburger and B. Nalebuff, Co-opetition, Currency and Doubleday, New York, New</p>
      <p>York,1997.
[12] M. Radonjic-Simic, D. Pfisterer, A Decentralized Business Ecosystem Model for Complex
Products, in: S. Patnaik, X. S. Yang, M. Tavana, F. Popentiu-Vlădicescu, F. Qiao (Eds.), Digital
Business, volume 21 of Lecture Notes on Data Engineering and Communications Technologies,
Springer, Cham, 2019, pp. 23–52. doi:10.1007/978-3-319-93940-7_2.
[13] P. Weill, S. Woerner, What's your digital business model? : six questions to help you build the
next-generation enterprise, Harvard Business School Press, Boston, Massachusetts, 2018.
[14] R. Giesecke, The electric mobility business ecosystem, in: Proceedings of the 9th. International
Conference on Ecological Vehicles and Renewable Energies, EVER ’14, Institute of Electrical and
Electronics Engineers Inc., Monte-Carlo, Monaco, 2014, pp. 1–13.
doi:10.1109/EVER.2014.6844046.
[15] M. J. M. Habets, Complementors: Their Effects on New Value Creation by SMEs in the Dutch</p>
      <p>Printing Industry, Master’s thesis, University of Twente, Enschede, Netherlands, 2012.
[16] C. H. Tsai, J. Zdravkovic, J. Stirna, Capability Management of Digital Business Ecosystems – A
Case of Resilience Modeling in the Healthcare Domain, in: N. Herbaut, M. La Rosa (Eds.),
Proceedings of the 32nd. International Conference on Advanced Information Systems
Engineering, volume 386 of CAiSE ’20, Lecture Notes in Business Information Processing,
Springer, Cham, 2020, pp. 126–137. doi:10.1007/978-3-030-58135-0_11.
[17] K. Sandkuhl, J. Stirna, A. Persson, M. Wißotzki, Enterprise modeling. Springer, Berlin,</p>
      <p>Heidelberg, 2014.
[18] H. Schön, J. Zdravkovic, J. Stirna, S. Strahringer, A Role-Based Capability Modeling Approach
for Adaptive Information Systems, in: J. Gordijn, W. Guédria, H. Proper (Eds.), Proceedings of
the 12th. IFIP Working Conference on The Practice of Enterprise Modeling, volume 369 of PoEM
’19, Lecture Notes in Business Information Processing, Springer, Cham, 2019, pp. 68–82. doi:
10.1007/978-3-030-35151-9_5</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J. F.</given-names>
            <surname>Moore</surname>
          </string-name>
          , Predators and Prey: A New Ecology of Competition,
          <source>Harvard Business Review</source>
          <volume>71</volume>
          (
          <year>1993</year>
          )
          <fpage>75</fpage>
          -
          <lpage>86</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>F.</given-names>
            <surname>Nachira</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Dini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Nicolai</surname>
          </string-name>
          ,
          <article-title>A network of digital business ecosystems for Europe: roots, processes and perspectives</article-title>
          , in: F.
          <string-name>
            <surname>Nachira</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Nicolai</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Dini</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Le Louarn</surname>
          </string-name>
          , L. Rivera Leon (Eds.),
          <source>Digital Business Ecosystems. European Commission, Bruxelles</source>
          ,
          <year>2007</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>20</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>P. K.</given-names>
            <surname>Senyo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Effah</surname>
          </string-name>
          ,
          <article-title>Digital business ecosystem: Literature review and a framework for future research</article-title>
          ,
          <source>International Journal of Information Management</source>
          <volume>47</volume>
          (
          <year>2019</year>
          )
          <fpage>52</fpage>
          -
          <lpage>64</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.ijinfomgt.
          <year>2019</year>
          .
          <volume>01</volume>
          .002.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>P. K.</given-names>
            <surname>Senyo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Effah</surname>
          </string-name>
          ,
          <article-title>Towards a methodology for modelling interdependencies between partners in digital business ecosystems</article-title>
          ,
          <source>in: Proceedings of the 7th. IEEE international conference on logistics, informatics and service sciences, LISS '17</source>
          ,
          <article-title>Institute of Electrical and Electronics Engineers Inc</article-title>
          .,
          <string-name>
            <surname>Kyoto</surname>
          </string-name>
          , Japan,
          <year>2017</year>
          , pp.
          <fpage>1165</fpage>
          -
          <lpage>1170</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>S. E.</given-names>
            <surname>Bonn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Löf</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. G.</given-names>
            <surname>Östenson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Trolle Lagerros</surname>
          </string-name>
          ,
          <article-title>App-technology to improve lifestyle behaviors among working adults - the Health Integrator study, a randomized controlled trial</article-title>
          .
          <source>BMC Public Health</source>
          ,
          <volume>19</volume>
          :
          <fpage>273</fpage>
          (
          <year>2019</year>
          ).
          <source>doi:10.1186/s12889-019-6595-6.</source>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>B. A.</given-names>
            <surname>Kitchenham</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Charters</surname>
          </string-name>
          ,
          <article-title>Guidelines for performing systematic literature reviews in software engineering</article-title>
          ,
          <source>Technical Report EBSE-2007-01</source>
          , School of Computer Science and Mathematics, Keele University,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>J. P. T.</given-names>
            <surname>Higgins</surname>
          </string-name>
          , J. Thomas,
          <string-name>
            <given-names>J.</given-names>
            <surname>Chandler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Cumpston</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. J.</given-names>
            <surname>Page</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V. A.</given-names>
            <surname>Welch</surname>
          </string-name>
          ,
          <article-title>Cochrane Handbook for Systematic Reviews of Interventions version 6.0 (electronic source), Cochrane</article-title>
          ,
          <source>Chichester (UK)</source>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>M.</given-names>
            <surname>Iansiti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Levien</surname>
          </string-name>
          ,
          <article-title>The Keystone Advantage: What the New Dynamics of Business Ecosystem Mean for Strategy, Innovation, and</article-title>
          <string-name>
            <surname>Sustainability</surname>
          </string-name>
          , Harvard Business School Publishing, Boston, Massachusetts,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>P. K.</given-names>
            <surname>Senyo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Effah</surname>
          </string-name>
          ,
          <article-title>Understanding behaviour patterns of multi-agents in digital business ecosystems: An organisational semiotics inspired framework</article-title>
          , in: J.
          <string-name>
            <surname>Kantola</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Nazir</surname>
          </string-name>
          , T. Barath (Eds.),
          <source>Proceeding of the 2nd. International Conference on Applied Human Factors and Ergonomics</source>
          , volume
          <volume>783</volume>
          <source>of AHFE '18</source>
          , Springer, Cham,
          <year>2018</year>
          , pp.
          <fpage>206</fpage>
          -
          <lpage>217</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>319</fpage>
          -94709-9_
          <fpage>21</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>R.</given-names>
            <surname>Wieringa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Engelsman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Gordijn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Ionita</surname>
          </string-name>
          ,
          <article-title>A business ecosystem architecture modeling framework</article-title>
          ,
          <source>in: Proceeding of the 21st. IEEE Conference on Business Informatics</source>
          , CBI '
          <volume>19</volume>
          ,
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>