<!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>Software Component Allocation in Distributed Development Settings</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Tommi Kramer</string-name>
          <email>kramer@uni-mannheim.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Chair of Information Systems University of Mannheim 68131 Mannheim</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Outsourcing in software development projects has become a widely adopted utility model for dealing with competitive issues such as cost pressure and the lack of skilled human resources. Established outsourcing relationships in terms of captive o shoring centers or clientvendor partnerships are prone to fail due to the lack of quali ed outsourcing decisions for the allocation of software components to either in-house or external/o shored development. Therefore, this design-oriented research endeavor aims at developing a methodology and a corresponding tool to inform and improve the outsourcing decision in global software development projects on the basis of software components. For that reason, the results of explorative case studies researching outsourcing decision making as well as concepts of collaborative software development are combined and form the proposed methodology for supporting project leads in decision making and in avoiding of instinctive and spontaneous decisions on the allocation of software components.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        From a national and global perspective, the sourcing of application systems has
signi cantly matured and been widely adopted over the past years. A signi
cant amount of software companies nowadays engage in software development
outsourcing (SDO) as they expect bene ts such as cost reduction,
round-theclock-development, or additional skilled workforce [
        <xref ref-type="bibr" rid="ref20 ref21 ref22 ref6">22, 20, 21, 6</xref>
        ]. However, the
success of outsourcing relationships in the IT sector is limited as about half of
SDO projects are prone to fail [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ]. A critical aspect for the outcome of
outsourcing relationships is the sourcing decision [
        <xref ref-type="bibr" rid="ref20 ref21">20, 21</xref>
        ]. However, despite the vast
amount and the variety of studies that analyze the outsourcing decision in SDO,
the decision making of outsourcing clients on the allocation of software
components has not been thoroughly analyzed in Information Systems (IS) research
yet. However, a deeper understanding of the sourcing allocation behavior could
on the one hand lead to contributions to the theoretical body of knowledge in
terms of sourcing behavior and on the other side it could improve the sourcing
strategy of software companies and thereby have a positive e ect on the SDO
outcomes like less software defects or better customer satisfaction.
      </p>
      <p>
        From a global software development (GSD) perspective rms have to deal
with collaboration of team members that are separated in di erent locations.
Since separation in terms of location or time challenge GSD projects in regard to
their success, collaboration platforms and smart concepts for communication and
collaboration have been established. Amongst others, traceability has become a
widespread methodology in GSD for controlling, tracing, and decision making
in globally distributed software projects [
        <xref ref-type="bibr" rid="ref14 ref16">16, 14</xref>
        ].
      </p>
      <p>As stated above, the sourcing decision of software components has only been
scarcely researched while the development setups of companies have shifed to a
global perspective. Hence, GSD provides approaches and concepts that fertilize
the decision making in SDO. For that, the research questions of this doctoral
thesis are as follows: 1) Which in uencing factors have an impact on the sourcing
decision of software components? 2) How can a sourcing decision for software
components based on the in uencing factors be made? These research questions
lead to this theory-informed and design-oriented research endeavor including the
following research objectives:
1. Developing a methodology to inform the outsourcing decision of SDO projects
on the allocation of software components to either in-house or external/o
shored teams and
2. to design and to implement an information system for supporting and
informing the component-based outsourcing decision.</p>
      <p>The remainder of this research proposal is structured as follows: First, basic
information about SDO and GSD as well as outsourcing decisions as foundation
of this research endeavor are described in the next section. Following, related
research in the area of outsourcing decisions is presented while selected
theories providing determinants for the component-based outsourcing decision are
introduced. In the consecutive subsection, the proposed approach and its
deduction, the used research methodology, and the preliminary ndings are described.
Finally, this proposal is conclude in the last section.
2
2.1</p>
    </sec>
    <sec id="sec-2">
      <title>Fundamentals</title>
      <sec id="sec-2-1">
        <title>Global Software Development and Outsourcing of Software</title>
      </sec>
      <sec id="sec-2-2">
        <title>Development Activities</title>
        <p>
          Development of software products in a globally distributed setting is the
preferred software engineering mode for an increasing number of companies [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ]. In
so-called virtual teams, in which team members are spread internationally all
over the world, software is developed by decision making regarding a common
goal and as product of collaboratively contributed components [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ]. Hence, a
development team may consist of members from all over the world (e.g. members
from Central Europe and Asia) and it is not bound to a single physical
location. However, the team as a whole aims at creating a common software product
independent from location, time zone, or organizational a liation [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ].
        </p>
        <p>
          Software development with virtual teams is highly interconnected with
outsourcing in software development projects which "is a multifaceted and complex
activity in which clients and vendors interact in many di erent ways to produce
and deliver the software services required" [10, p. 960]. This results in di
erent settings of client-vendor-relationships which are considered as outsourcing of
software activities to an external provider (classical outsourcing), as outsourcing
to an external provider in an o shore/farshore country (o shoring), or as internal
provision at an o shore location (captive o shoring) whereof each outsourcing
type is challenging di erently but is also strongly supported by concepts of GSD
[
          <xref ref-type="bibr" rid="ref29 ref31 ref4">29, 4, 31</xref>
          ].
        </p>
        <p>
          The variety and availability of di erent outsourcing types are not only means
for large software companies. Even small and medium-sized enterprises make use
of the described sourcing models as they want to participate in the advantages
of GSD and SDO as well, which are for them primarily the access to skilled
workforce, the exibility to allocate and to clear resources, or to save costs [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ].
However, a large number of companies struggle to handle several barriers and
problems caused by outsourcing settings. Hence, just to name a few, vendor
selection, relationship quality, knowledge transfer, or hidden transaction costs
are cause for SDO projects that fail, since the goals of a software development
project are not achieved in time or with reasonable costs [
          <xref ref-type="bibr" rid="ref28 ref34 ref7">7, 28, 34</xref>
          ].
        </p>
        <p>
          As a consequence, this research endeavor aims at analyzing the concepts of
GSD, especially the concept of traceability and rationale management (TRM),
with regard to failing factors of SDO projects. As traceability and rationale
information in distributed software development projects represent a network
consisting of software development artifacts, connections between these artifacts,
and annotations to these connections, the stringent maintenance of such data
provides detailed information about planned software components [
          <xref ref-type="bibr" rid="ref16 ref23">16, 23</xref>
          ]. Since
the allocation of software components (in-house vs. external/o shored) in the
context of distributed software development is a crucial factor of the success of
outsourcing relationships, the focus of this research work is set on
componentbased allocation decision making in SDO.
2.2
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>Outsourcing Decision Making</title>
        <p>Decision making as a part of SDO is a vital element for minimizing the
faultproneness of an outsourcing relationship. It comprises the analysis of
multifaceted in uencers regarding their implications on the sourcing strategy of a
company. Hence, a range of outsourcing decision making approaches has been
proposed in past research.</p>
        <p>
          [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] have set their focus on the make-or-buy decision, which analyzes the
fundamental type of sourcing by not only focusing on IT functions but also
on hardware. Furthermore, [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] have researched decision making with regard
to speci c IT functions while [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] have put emphasize on contractual issues
of an outsourcing relationship. Additionally, decisions have been analyzed in
consideration of the sourcing location by analyzing nearshore and farshore [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ].
To sum it up, the in uencing factors of an outsourcing decision can, according
to [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ], be categorized in:
{ Motivation to Outsource
{ Client Firm Characteristics
{ Transaction Attributes
{ In uence Sources
        </p>
        <p>
          However, current outsourcing decisions are generally strategic in nature [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]
and consider aspects that can be determined on a strategic level before an
outsourcing relationship is initiated. For that purpose, several process models are
provided by the literature [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. Decision support methodologies that focus on the
allocation of software components, meaning development decisions on the
operational level of software projects, are currently missing in IS research, since
determinants in uencing the component-based outsourcing decision have not
been researched in detail yet.
3
3.1
        </p>
        <p>Decision Making in Software Development Outsourcing</p>
      </sec>
      <sec id="sec-2-4">
        <title>Existing Research and Related Work</title>
        <p>
          The aim of this dissertation work is to analyze determinants and contingency
factors that in uence the allocation decision for software components in SDO
(cf. research question 1). Additionally, this research endeavor seeks to develop a
decision support approach for evaluating software components according to their
outsourcing potential (cf. research question 2). Therefore, the wheel has not to be
reinvented, since there already exist collections and literature synopses of
decision determinants as shown by [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] and [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ]. They show that the sourcing decision
on the one hand depends on rm speci c characteristics such as management
capabilities and the nature of the activity. On the other hand, the decision is
in uenced by external environments and, hence, by economic factors. Depending
on these factors, the decision can be mapped on di erent potential sourcing
options { e.g. in-house, outsourced, captive o shored, or externally o shored [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ].
However, the focus has not yet been set on speci c software development tasks
but only on a project level which disables component-based sourcing decisions.
The collection of factors in uencing the decision making is still expected to be
incomplete.
        </p>
        <p>
          Support of the decision making process in SDO has experienced little
attention in IS research only. Similar to determinants and contingency factors in the
paragraph above, decision making processes have been developed on a strategic
level thoroughly but have been unattended on project level, where the question
of component allocation arises. Thus, the dynamic model of o shore software
development by [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] serves as existing research model for outsourcing decision
making on project level, however, the granularity of the decision making process
only allows to evaluate entire projects or development phases, but not software
development tasks in terms of components. Another contribution delivers a
decision matrix with best practices for a possible organization form according to
the decomposition of the product development [
          <xref ref-type="bibr" rid="ref33">33</xref>
          ]. Hence, a structured and
rigorous component-based decision making in SDO remains open and is the aim of
this dissertation endeavor.
3.2
        </p>
      </sec>
      <sec id="sec-2-5">
        <title>Selected Theories</title>
        <p>
          In the course of a theory informed design science research approach, relevant
theories from IS literature that are used to inform the search for decision
determinants have been selected and are explained in the following: The Resource-based
View (RBV) considers a rm as a set of productive resources [
          <xref ref-type="bibr" rid="ref2 ref35">2, 35</xref>
          ]. It explicates
that the set of resources contains a subset that is responsible for achieving
competitive advantage and another one that enables superior long-term performance.
Hence, the company is able to prevent resources from imitation, substitution, or
transfer.
        </p>
        <p>
          The Knowledge-based View (KBV) has its origin in the RBV of the rm and is
a theoretical perspective that regards knowledge as the most important resource
of the rm [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. It states that in case of integrating knowledge from di erent
sources under certain conditions the e ciency is higher when it is performed
within the rm's boundaries.
        </p>
        <p>Additonally, Transaction Cost Economics (TCE) consider the market
participation as costly while identifying conditions under which market governance
is more advantageous than internal governance of a rm [36, 37]. Hence,
transaction costs have to be considered when participating in the market and the
assumptions of bounded rationality and opportunistic behavior of other
participants have to be taken into account. For protecting against opportunistic
behavior of another market participant transaction costs occur.</p>
        <p>
          Finally, the Systems Theory (ST) [
          <xref ref-type="bibr" rid="ref3 ref32">32, 3</xref>
          ] describes the interactions of complex
systems. It states that a complex system consists of several subsystems that
interact and are interdependent to a certain degree, depending on the design of
the system. An implication of ST is that weak interactions between subsystems
lead to an almost decomposable system.
3.3
        </p>
      </sec>
      <sec id="sec-2-6">
        <title>Intended Research Approach and Preliminary Results</title>
        <p>
          In order to meet the intended research goals, the structure of this dissertation
endeavor is design-oriented in nature [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] and follows the research approach of
theory building from case study research [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. Hence, a theory-informed artifact
is created from conducted case studies. The structure of the intended research
work is brie y summarized in Table 1 and is described in detail after this. The
descriptions are complemented with preliminary ndings, if already available.
        </p>
        <p>In a rst step, case studies with eight small and medium-sized enterprises
(SME) that engage in GSD with virtual teams have been conducted. The study
describes the software development phases that are suitable for outsourcing,
organizational and operational aspects of outsourcing decision, and characteristics
of software components that qualify for outsourcing (the publication is under
review at the moment). The study reveals the need for decision support in the role
Step Results / Planned Activity Status
Case studies Identify need for a decision support methodology Done
in SDO projects on the basis of software
components.</p>
        <p>Deduction of require- Deduction of requirements from RBV and KBV Done
ments from theory of the rm, from ST, and from software
engineering principles. Development of a t model
including determinants of the allocation decision of SDO
projects that a ect software components.</p>
        <p>Complement determi- Extend the set of determinants with exploratory In
nants with input from case studies to prove the relevance for practice. progress
practice
Development of a deci- Development of an outsourcing decision support In
sion support methodol- methodology for the allocation of software com- progress
ogy ponents (in-house development versus external or
o shored development).</p>
        <p>Development of a deci- Implementing the requirements of the decision Planned
sion support tool support methodology as mobile web-application
by enriching the determinants and contingencies
with available data from collaboration platforms
of GSD teams.</p>
        <p>Evaluation Evaluation of the the developed methodology for Planned
component-based outsourcing decisions as an
empirical study in an organizational setting.
of a project manager and shows that software development outsourcing is mainly
a ecting the implementation phase of a software project as software components
are allocated either for in-house or outsourced development. Therefore, this
research endeavor intends to develop a methodology and tool support for project
managers in order to make informed outsourcing decisions for components.</p>
        <p>In a second step, requirements for the intended decision support methodology
were deduced from theories described in the previous subsection. From the RBV,
the KBV, and the ST the following requirements have been derived:
{ Software components that are highly interacting with other components of
the software system should not be developed over company boundaries (ST).
{ The priorities of connected requirements or requirements sets of a
component describe the importance of the software component and, thus, increase
the competitive advantage of a rm. Hence, the subsystem should not be
outsourced (KBV).
{ In the case of intense communication between software developers for the
planning/implementation of a single component, the development should
not be outsourced (RBV).
{ Depending on the required knowledge for the software component to be
developed, the component is either developed in-house or outsourced,
depending on the skill availability. The required knowledge has to be di
erentiated between functional knowledge, business process speci c knowledge,
and technical knowledge (KBV).
{ The development of a component should not be outsourced if a frequent
exchange of information is required (TCE).</p>
        <p>Additional requirements were derived from outsourcing literature and
software engineering practices in GSD:
{ Traceability and rationale information resulting from collaboration platforms
should be used to improve the sourcing decision making process (e.g. use
traceability details such as requirements and their connectivity to software
components in order to determine the importance of a component by the
priority of connected requirements).
{ The solution should be optimized for project leads, since they are primarily
in charge of outsourcing decision making. Thus, the software tool should be
lightweight and should be provided as mobile solution but must not be
lacking the interfaces to latest data stored in the rm's collaboration platform.</p>
        <p>As described in Table 1, in a third step, the requirements that were deduced
from existing theories are enriched by multiple case studies of an explorative
research design. The case studies consist of interviewing experts and reviewing
as well as analyzing documents and data of software companies. For this
purpose, semi-structured interviews according to a questionnaire consisting of 42
open questions are conducted [38]. The case studies aim at complementing the
in uencing determinants and contingency factors of component-based
outsourcing decision making. Thus, the target groups of the interviews are project leads
or deciders of SDO projects in small, medium-sized, or large software
engineering enterprises. Currently, six companies have been analyzed and at least six
more cases are planned. The preliminary results disclose further determinants
and contingencies that in uence the sourcing decision. Hence, the SDO decision
and its determinants can be modeled by the t model as presented in Figure 1.</p>
        <p>
          According to the proposed conceptual t model, the development of a
component-based decision support methodology for SDO projects is in the focus
of the next step. By incorporating the explored determinants of the
outsourcing decision, the approach makes use of the TRM approach of GSD. For each
determinant the possibility of using TRM data is analyzed and conceptually
described. Hence, this research endeavor aims at informing the sourcing decision
to a high degree with structured data from used collaboration platforms and to
increase the utility of the proposed methodology. An initial instantiation of the
component-based decision support methodology has already been published [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ]
and is continuously adapted to additional ndings resulting from the described
expert interviews of the case studies in step three.
        </p>
        <p>
          Finally, in step ve and six, the implementation and evaluation of the
conceptual methodology complete the theory-informed artifact building from case
studies [
          <xref ref-type="bibr" rid="ref15 ref30 ref8">15, 30, 8</xref>
          ]. The design oriented nature of this dissertation endeavor is
further emphasized by a rigorous evaluation framework that checks for the
following criteria that are notably relevant in practice: e ciency, practicability,
quality of implemented components, rework rate, solution speed of the
implementing team/company, and transfer e ort. The criteria list is not claimed to be
completed yet and is still subject to change. Due to time constraints of
practitioners that are seeked to evaluate the resulting artifact, it is intended to apply
a two step approach which consists on the one hand of a real case evaluation
and on the other hand of a virtual experiment based on the real case. In the
controlled experiment the ndings of the real case have to be re ned by further
experts.
4
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Conclusion</title>
      <p>Researching component-based outsourcing decision making in SDO combined
with the development of tool support by implementing concepts of GSD is highly
demanded by companies in corresponding outsourcing relationships. However,
not only the relevance for practice but also the request in academic research for
theoretical contribution to outsourcing decision support on a component level
lay the foundation for this research endeavor that has the goal to facilitate such
sourcing decisions by structured and well informed analyses of the component
speci cs. At the same time this research work extends the knowledge base of
decision making theory in SDO.</p>
      <p>The next steps of this research endeavor include the completion of the
exploratory phase by conducting the remaining case studies as well as the nal
definition of the described decision support methodology. Afterwards, the intended
artifact in form of a software tool is implemented and used for the evaluation
and testing of the underlying methodology.</p>
    </sec>
    <sec id="sec-4">
      <title>Acknowledgment</title>
      <p>This doctoral research is being supervised by Prof. Armin Heinzl (University of
Mannheim, heinzl@uni-mannheim.de) and is supported by the German state
of Baden-Wuerttemberg as part of the research project "GlobaliSE".
[36] Williamson, O.E.: Markets and Hierarchies: Analysis and Antitrust Implications.</p>
      <p>Free Press, New York (1975)
[37] Williamson, O.E.: The Economic Institutions of Capitalism: Firms, Markets,
Relational Contracting. Free Press, New York, USA (1985)
[38] Yin, R.K.: Case Study Research: Design and Methods. Sage Publications, Los
Angeles, California, USA (2010)</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Arnett</surname>
            ,
            <given-names>K.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jones</surname>
            ,
            <given-names>M.C.</given-names>
          </string-name>
          :
          <article-title>Firms that choose outsourcing: A pro le</article-title>
          .
          <source>Information and Management</source>
          <volume>26</volume>
          (
          <issue>4</issue>
          ),
          <volume>179</volume>
          {
          <fpage>188</fpage>
          (
          <year>1994</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Barney</surname>
            ,
            <given-names>J.B.</given-names>
          </string-name>
          :
          <article-title>Firm resources and sustained competitive advantage</article-title>
          .
          <source>Journal of Management</source>
          <volume>17</volume>
          (
          <issue>1</issue>
          ),
          <volume>99</volume>
          {
          <fpage>120</fpage>
          (
          <year>1991</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3] von Bertalan y, L.:
          <article-title>General System Theory: Foundations, Development, Applications</article-title>
          . G. Braziller, New York (
          <year>1968</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Carmel</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Agarwal</surname>
          </string-name>
          , R.:
          <article-title>Tactical approaches for alleviating distance in global software development</article-title>
          .
          <source>IEEE Software 18(2)</source>
          ,
          <volume>22</volume>
          {
          <fpage>29</fpage>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Dedrick</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Carmel</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kraemer</surname>
            ,
            <given-names>K.L.:</given-names>
          </string-name>
          <article-title>A dynamic model of o shore software development</article-title>
          .
          <source>Journal of Information Technology 26</source>
          ,
          <issue>1</issue>
          {
          <fpage>15</fpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Dibbern</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goles</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hirschheim</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jayatilaka</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Information systems outsourcing: A survey and analysis of the literature</article-title>
          .
          <source>Communications of the ACM</source>
          <volume>35</volume>
          (
          <issue>4</issue>
          ),
          <volume>6</volume>
          {
          <fpage>102</fpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Dibbern</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Winkler</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heinzl</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Explaining variations in client extra costs between software projects o shored to india</article-title>
          .
          <source>MIS Quarterly</source>
          <volume>32</volume>
          (
          <issue>2</issue>
          ),
          <volume>1</volume>
          {
          <fpage>30</fpage>
          (
          <issue>2008</issue>
          , June)
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Eisenhardt</surname>
            ,
            <given-names>K.M.:</given-names>
          </string-name>
          <article-title>Building theories from case study research</article-title>
          .
          <source>The Academy of Management Review</source>
          <volume>14</volume>
          (
          <issue>4</issue>
          ),
          <volume>532</volume>
          {
          <fpage>550</fpage>
          (
          <year>1989</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Gefen</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wyss</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lichtenstein</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Business familiarity as risk mitigation in software development outsourcing contracts</article-title>
          .
          <source>MIS Quarterly</source>
          <volume>32</volume>
          (
          <issue>3</issue>
          ),
          <volume>531</volume>
          {
          <fpage>551</fpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Gopal</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gosain</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>The role of organizational controls and boundary spanning in software development outsourcing: Implications for project performance</article-title>
          .
          <source>Information Systems Research</source>
          <volume>21</volume>
          (
          <issue>4</issue>
          ),
          <volume>960</volume>
          {
          <fpage>982</fpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Gopal</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sivaramakrishnan</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krishnan</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mukhopadhyay</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Contracts in o shore software development: An empirical analysis</article-title>
          .
          <source>Management Science</source>
          <volume>49</volume>
          (
          <issue>12</issue>
          ),
          <volume>1671</volume>
          {
          <fpage>1683</fpage>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Grant</surname>
            ,
            <given-names>R.M.</given-names>
          </string-name>
          :
          <article-title>Toward a knowledge-based theory of the rm</article-title>
          .
          <source>Strategic Management Journal</source>
          <volume>17</volume>
          (
          <issue>Winter Special Issue</issue>
          ),
          <volume>109</volume>
          {
          <fpage>122</fpage>
          (
          <year>1996</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Grover</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cheon</surname>
            ,
            <given-names>M.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Teng</surname>
            ,
            <given-names>J.T.C.</given-names>
          </string-name>
          :
          <article-title>An evaluation of the impact of corporate strategy and the role of information technology on is functional outsourcing</article-title>
          .
          <source>European Journal of Information Systems</source>
          <volume>3</volume>
          (
          <issue>3</issue>
          ),
          <volume>179</volume>
          {
          <fpage>191</fpage>
          (
          <year>1994</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Herbsleb</surname>
            ,
            <given-names>J.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moitra</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Global software development</article-title>
          .
          <source>IEEE Software 18</source>
          ,
          <issue>16</issue>
          { 20 (March - April
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>Hevner</surname>
            ,
            <given-names>A.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>March</surname>
          </string-name>
          , S.T.,
          <string-name>
            <surname>Park</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sudha</surname>
          </string-name>
          , R.:
          <article-title>Design science in information systems research</article-title>
          .
          <source>MIS Quarterly</source>
          <volume>28</volume>
          (
          <issue>1</issue>
          ),
          <volume>75</volume>
          {
          <fpage>105</fpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <surname>Hildenbrand</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Improving Traceability in Distributed Collaborative Software Development</article-title>
          . Lang,
          <string-name>
            <surname>Frankfurt</surname>
          </string-name>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <surname>Kaiser</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hawk</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Evolution of o shore software development: From outsourcing to co-sourcing</article-title>
          .
          <source>MIS Quarterly Executive</source>
          <volume>3</volume>
          (
          <issue>2</issue>
          ),
          <volume>69</volume>
          {
          <fpage>81</fpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <surname>Klimpke</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kramer</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Betz</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nordheimer</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Globally distributed software development in small and medium-sized enterprises in germany: Reasons, locations, and obstacles</article-title>
          .
          <source>In: Proceedings of the 19th European Conference on Information Systems (ECIS2011)</source>
          , Helsinki, Finland (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <surname>Kramer</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heinzl</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Spohrer</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Should this software component be developed inside or outside our rm? - a design science perspective on the sourcing of application systems</article-title>
          .
          <source>In: Proceedings of the 5th Global Sourcing Workshop</source>
          , Courchevel, France (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <surname>Lacity</surname>
            ,
            <given-names>M.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Khan</surname>
            ,
            <given-names>S.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yan</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Willcocks</surname>
            ,
            <given-names>L.P.:</given-names>
          </string-name>
          <article-title>A review of the it outsourcing empirical literature and future research directions</article-title>
          .
          <source>Journal of Information Technology</source>
          <volume>25</volume>
          ,
          <issue>395</issue>
          {
          <fpage>433</fpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <surname>Lacity</surname>
            ,
            <given-names>M.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Solomon</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yan</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Willcocks</surname>
            ,
            <given-names>L.P.</given-names>
          </string-name>
          :
          <article-title>Business process outsourcing studies: A critical review and research directions</article-title>
          .
          <source>Journal of Information Technology</source>
          <volume>26</volume>
          ,
          <issue>221</issue>
          {
          <fpage>258</fpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <surname>Lacity</surname>
            ,
            <given-names>M.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Willcocks</surname>
            ,
            <given-names>L.P.:</given-names>
          </string-name>
          <article-title>An empirical investigation of information technology sourcing practices: Lessons from experience</article-title>
          .
          <source>MIS Quarterly</source>
          <volume>22</volume>
          (
          <issue>3</issue>
          ),
          <volume>363</volume>
          {
          <fpage>408</fpage>
          (
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <surname>Lindvall</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sandahl</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Practical implications of traceability</article-title>
          .
          <source>Software - Practice &amp; Expererience</source>
          <volume>26</volume>
          (
          <issue>10</issue>
          ),
          <volume>1161</volume>
          {
          <fpage>1180</fpage>
          (
          <year>1996</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <surname>Lipnack</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stamps</surname>
          </string-name>
          , J.: Virtual Teams:
          <article-title>Reaching across Space, Time, and Organizations with Technology</article-title>
          . John Wiley &amp; Sons, Inc. (
          <year>1997</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <surname>Maznevski</surname>
            ,
            <given-names>M.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chudoba</surname>
            ,
            <given-names>K.M.:</given-names>
          </string-name>
          <article-title>Bridging space over time</article-title>
          .
          <source>Organization Science</source>
          <volume>11</volume>
          (
          <issue>5</issue>
          ),
          <volume>473</volume>
          {
          <fpage>492</fpage>
          (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <surname>McDougall</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Dexterity required</article-title>
          .
          <source>InformationWeek June</source>
          <volume>19</volume>
          , 34 {
          <fpage>39</fpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <surname>Metters</surname>
            ,
            <given-names>R.:</given-names>
          </string-name>
          <article-title>A typology of o shoring and outsourcing in electronically transmitted services</article-title>
          .
          <source>Journal of Operations Management</source>
          <volume>26</volume>
          (
          <issue>2</issue>
          ),
          <volume>198</volume>
          {
          <fpage>211</fpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <surname>Mirani</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          :
          <article-title>Client-vendor relationships in o shore applications development: An evolutionary framework</article-title>
          .
          <source>Information Resources Management Journal</source>
          <volume>19</volume>
          (
          <issue>4</issue>
          ),
          <volume>72</volume>
          {
          <fpage>86</fpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <surname>Olsson</surname>
            ,
            <given-names>H.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Conchuir</surname>
            ,
            <given-names>E.O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Agerfalk</surname>
            ,
            <given-names>P.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fitzgerald</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Two-stage o shoring: An investigation of the irish bridge</article-title>
          .
          <source>MIS Quarterly</source>
          <volume>32</volume>
          (
          <issue>2</issue>
          ),
          <volume>257</volume>
          {
          <fpage>279</fpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <surname>Pe</surname>
            <given-names>ers</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Tuunanen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Rothenberger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.A.</given-names>
            ,
            <surname>Chatterjee</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.:</surname>
          </string-name>
          <article-title>A design science research methodology for information systems research</article-title>
          .
          <source>Journal of Management Information Systems</source>
          <volume>24</volume>
          (
          <issue>3</issue>
          ),
          <volume>45</volume>
          {
          <fpage>78</fpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [31]
          <string-name>
            <surname>Sahay</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nicholson</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krishna</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <source>Global IT Outsourcing: Software Development across Borders</source>
          . Cambridge University Press, Cambridge, USA (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [32]
          <string-name>
            <surname>Simon</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          :
          <article-title>The architecture of complexity</article-title>
          .
          <source>In: Proceedings of the American Philosophical Society</source>
          . vol.
          <volume>106</volume>
          , pp.
          <volume>467</volume>
          {
          <issue>482</issue>
          (
          <year>1962</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          [33]
          <string-name>
            <surname>Tripathy</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Eppinger</surname>
          </string-name>
          , S.D.:
          <article-title>Organizing global product development for complex engineered systems</article-title>
          .
          <source>IEEE Transactions on Engineering Management PP</source>
          ,
          <volume>1</volume>
          {
          <fpage>20</fpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          [34]
          <string-name>
            <surname>Wadhwa</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ravindran</surname>
            ,
            <given-names>A.R.</given-names>
          </string-name>
          :
          <article-title>Vendor selection in outsourcing</article-title>
          .
          <source>Computers &amp; Operations Research</source>
          <volume>34</volume>
          (
          <issue>12</issue>
          ),
          <volume>3725</volume>
          {
          <fpage>3737</fpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          [35]
          <string-name>
            <surname>Wernerfelt</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>A resource-based view of the rm</article-title>
          .
          <source>Strategic Management Journal</source>
          <volume>5</volume>
          ,
          <issue>171</issue>
          {
          <fpage>180</fpage>
          (
          <year>1984</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>