SlideShare ist ein Scribd-Unternehmen logo
1 von 8
Downloaden Sie, um offline zu lesen
IOSR Journal of Computer Engineering (IOSRJCE)
ISSN: 2278-0661 Volume 3, Issue 2 (July-Aug. 2012), PP 24-31
www.iosrjournals.org

Software Development Multi-Sourcing Relationship Management
  Model (Sdmrmm) Protocol (A Systematic Literature Review)
                            Muhammad Salam1, Dr.Siffat Ullah Khan2
                   1
                    (Department of Computer Science and IT, University of Malakand, Pakistan)
       2
           (Department, Computer Science and IT/Software Engineering, University of Malakand, Pakistan)

Abstract :CONTEXT: Software development multi-sourcing is a modern software engineering paradigm in
which the software project is contracted out to multi-vendors. In software multi-sourcing, there is one client and
many vendors involved in the outsourcing contract. The client relies on more than one outsourcing vendors for
the fulfillment of the software development activity.
OBJECTIVE: The objective of this study is to develop SDMRMM to assist multi-sourcing vendor organizations
in establishing, strengthening and maintenance of the relationships with fellow vendors and client in multi-
sourcing situation. The model is for vendor to vendor and vendor to customer relationships in multi-sourcing
paradigm.
METHOD: we have developed a systematic literature review (SLR) protocol for software development multi-
sourcing relationships management model (SDMRMM) from vendor’s perspective. SLR is based on a structured
protocol and is therefore different from ordinary literature view.
EXPECTED OUTCOME: The anticipated outcome of this review will be a list of challenges faced by vendors in
establishment and maintenance of relationships with Clint as well as fellow vendors in multi-vendors software
outsourcing also critical success factors for establishment and maintenance of log-lasting relationships will be
identified.
Keywords: Software Multisourcing; Multi-vendors outsourcing; Multisourcing relationships;

                                           I.           Introduction
         Keeping in view global software development, software outsourcing is a new software engineering
pattern[2].This research proposal describes the systematic literature review (SLR) [3] protocol which will be
used to investigate that what are the challenges faced by vendors in the establishment and maintenance of multi-
vendor outsourcing relationships and what are the critical success factors to be developed by vendors for the
success of multi-source project. Identifying the challenges and critical success factors will help the vendors to
establish and maintain long-lasting relationships with fellow vendors as well as clients. This may also help to
ensure the successful outcomes of the multi sourced software projects.
         Multi-sourcing is sometime called ―multi-vendor outsourcing‖ OR ―multi-supplier sourcing‖ [4].In
multi-sourcing, the client has one outsourcing contract with multiple suppliers. A multi-sourcing paradigm
allows a client to engage multiple vendors for various components of software project that are then jointly
performed by multiple suppliers. since the work is performed together by multi vendors, this implies that a
cooperative and competitive environment exists between the suppliers working jointly as shown in the Fig.1[4].




                                      Fig.1 A typical multisourcing situation

         There are five research questions as mentioned in section 3 of this protocol that have motivated the
work reported in this research study.
         The core purpose of this study is to build Software Development Multi-sourcing Relationship
Management Model (SDMRMM).The model will help software outsourcing organizations (vendors) to establish
sound and long lasting relationships with fellow vendors and clients in a software multisourcing.
         The outsourcing may be unisourcing or multi-sourcing, prior to undertake software project outsourcing,
the customer decides either to go for unisourcing or multi-sourcing. There are clear differences between the two
approaches. The most important difference between unisourcing and multi-sourcing is that they require different

                                                www.iosrjournals.org                                    24 | Page
Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol
internal management structures. Multisourcing will need wider internal management which has the capability to
accommodate several suppliers at one time. Moreover there are other compulsions. In Unisourcing one party
perform its promise whereby, in multi-sourcing more than one party held responsible in case of project failure.
The cost and return factors along with risk of these two approaches are taken into consideration[5].Multi
sourcing is preferred comparatively because it has many advantages for customers, for example, it creates a
competing environment and decreases to maximum extent the risk of project failure, and enhance the quality of
the software. Furthermore, multi sourcing is practiced when the suppliers feel that they are deficient in terms of
capabilities[6].―Risk sharing is, hence, a common practice for parties adopting multiple outsourcing
relationships‖[7].Different studies show that trust is critical for all business relationships [8].However the focus
of our study is on multi-vendors outsourcing relationships. A number of researchers have tried to address some
of the issues of Multi-outsourcing, e.g. [9-11].Placement of an order in an environment, where many suppliers
are working, needs proper attention and care, For reducing the average inventory cost, questions like when to
place an order, how to order and how many order from each suppliers, are to be answered[6].The manager
should establish and maintain productive and good working relationship among the members of virtual teams to
achieve the predetermined results and goals, other studies in the literature have also showed the importance of
trust in virtual teams [12].Establishing and maintaining good relationship with the outsourcing partners and
suppliers helps the managers to share and transfer skills, and also ensure the trust worthiness and confidence of
the suppliers on partners [13].―Recently, as global business environments have become increasingly complex
and turbulent with the rise of off- shoring, firms started selecting and combining relationships with multiple
service providers based in different countries as part of their sourcing strategy― [14].―New approaches and skills
are required to effectively manage the increased volume and complexity of relationships between the various
parties involved in multi-sourcing deals―[15].However, nobody has used the Systematic Literature Review
(SLR) [3] approach in order to identify the challenges faced by vendors in multi-vendor outsourcing
relationship and critical success factors to be developed by vendors for successful multi-vendor outsourcing
relationships.―A systematic literature review is a means of identifying, evaluating and interpreting all available
research relevant to a particular research question, or topic area, or phenomenon of interest‖[16].―systemic
literature review (SLR) has become an important research methodology in software engineering, since the
introduction of evidence-based software engineering(EBSE) in 2004―[17].The purpose of this study is to
develop Software Development Multi-sourcing Relationships Management Model (SDMRMM) the model is
useful for software vendors which works in multi-vendors outsourcing. During the model and protocol
development I have studied a number of systemic literature reviews [18, 19].

                                II.         Background of multi-sourcing
         Multi sourcing is the combination of two words-‗Multi‘ and ‗Sourcing‘. Hence Multi mean many and
―Sourcing refers to the act of transferring work, responsibilities and decision rights to someone else‖ or in other
words we can say that ―Sourcing is the act of transferring work from one entity to another‖ so we can say that
multi sourcing is the transferring of work (software) from one entity (Client) to multiple entities
(Vendors).According to [20] there are three components of outsourcing 1) Client 2) Vendor 3) Project, The
organization transferring the work is referred to as the client, the organization that conducts the work and makes
decisions is the vendor, and the scope of the work is captured in a project as shown in Fig.2




                                                       Fig.2

          ―Software development outsourcing is defined as a situation where a company (a client) contracts out
all or part of its software development activates to another company (a vendor), who provides agreed services
for remuneration‖ [21]. ―In today‘s global services outsourcing arena, increasing numbers of companies adopt
multi-sourcing, that is, they select and combine information technology (IT) and business services from multiple
providers‖ [14]. ―Multi-sourcing is when you outsource functions to more than one vendor. Multi-sourcing
involves breaking up the project into several components that can be handled by independent vendors and
usually occurs during a total outsourcing project. Multi-sourcing encourages competition between vendors and
creates a shared objective to Perform at high levels‖ [20]. Components of multi-sourcing Relationship are
shown in the following Fig.1.


                                             www.iosrjournals.org                                         25 | Page
Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol
According to [22] are various types of outsourcing which can be divided into two main categories as shown in
the Fig.3




                                       Fig.3 various types of outsourcing

         The research work reported in this study is related to multisourcing relationships management from
vendor to vendor (V2V) and from vendor to customer (V2C). The research is based on systematic literature
review. The protocol for SDMRMM is developed on the basis of five research questions which are mentioned in
section 3 of this protocol.

                                    III.         Research Questions
         There are five research questions that have motivated the work reported in this research proposal.
RQ1. What are the challenges/barriers, as identified in the literature, faced by vendor‘s in the establishment and
maintenance of relationships with client as well as the fellow vendors in multi-vendors software outsourcing
situation?
RQ2. What are the critical success factors, as identified in the literature, to be developed by vendors for the
establishment and maintenance of long-lasting relationships with client as well as the fellow vendors in multi-
vendors software outsourcing situation?
RQ3. What are the challenges/barriers, as identified in the outsourcing industry, faced by vendors in the
establishment and maintenance of relationships with client as well as the fellow vendors in multi-vendors
software outsourcing situation?
RQ4. What are the critical success factors, as identified in the outsourcing industry, to be developed by vendors
for the establishment and maintenance of long-lasting relationships with client as well as the fellow vendors in
multi-vendors software outsourcing situation?
RQ5. What are the real-world practices for addressing the identified success factors and barriers in multi-
vendors software outsourcing situation?

         For RQ1 and RQ2 the identification of CBs (Critical Barriers) and CSFs (Critical Success Factors), we
will use systematic literature review (SLR). We will conduct empirical study (questionnaire survey) for the
validation of SRL findings and to answer research questions RQ3, RQ4 and RQ5. The Software Development
multi-sourcing relationship Management Model (SDMRMM) will be developed using SLR guidelines[3, 16]
this model will help software outsourcing organizations (vendors) to indentify the challenges/barriers in
establishment and maintenance of relationships with client as well as fellow vendors in multi-vendors software
outsourcing, the proposed model will be useful for establishment and maintenance of log-lasting relationships
with client and fellow vendors.

                IV.          Systematic Literature Review Protocol for SDMRMM
          A systematic literature review is a new research methodology, it is a way of identifying, evaluating and
interpreting all available research relevant to a particular research question, or topic area, or phenomenon of
interest [16]. Now a a day‘s systematic literature review has become an important research methodology [17].
SLR has the following main three phases.
 Planning the review
 Conducting the review
 Reporting the review
     The expected outcomes of this review will be the identification of different CSFs and CBs that play
important role in software development multisourcing relationships.

4.1 Constructing Search Term
The following details will help in designing a search term relevant to our research questions.
    Population: Software Development multisourcing relationship, multi-vendors software outsourcing
    relationships, multi supplier software outsourcing, client and vendors.
 Intervention: challenges, barriers, critical success factors, establishment of relationships, maintenance
    relationships.
                                            www.iosrjournals.org                                        26 | Page
Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol
   Outcomes of relevance: establishment and maintenance of long-lasting relationships, identification of
    challenges/barriers in establishment and maintenance of relationships with client as well as fellow vendors
    in multi-vendors software outsourcing, Software Development Multi-sourcing Relationship Management
    Model (SDMRMM), long-lasting relationships with clients, long-lasting relationships with fellow vendors.
 Experimental Design: Empirical studies, systematic literature review, theoretical studies, case studies,
    expert‗s opinions, etc.
Examples of the Research Questions containing the above details are:
RQ1:
       [Challenges/barriers]                                                       INTERVENTION
       [Software Multi-sourcing Relationships]                                     POPULATION
       Faced by vendor
       [in the establishment and maintenance of relationships with client as well as the fellow vendors in
multi-vendors software outsourcing situation]                             OUTCOMES OF RELEVANCE

                                         V.           search strategy
5.1 Trail search
         A trial search was conducted using the following search string on selected digital libraries as shown
section 5.4 of this protocol.
          (Multisourcing OR ―software multisourcing‖ OR ―multi vendors outsourcing" OR ―multi Supplier
outsourcing‖ OR ―dual sourcing‖) AND (―multi-vendors relationships‖ OR "multi-vendors outsourcing" OR
―outsourcing relationships").

             S.No                             Digital library            Search Conduction Date
             IEEE Explore                     15,55                      26 April 2012
             ACM Digital Library              1214                       26 April 2012
             Google Scholar                   232                        26 April 2012
             Science Direct                   1084                       26 April 2012
             Site Seer Digital Library        1116                       26 April 2012
             Springer link                    236 + 247                  26 April 2012

                                         Table 2: Trail Search Results

         The papers retrieved through this search string will be used as a guide for the development and
validation of the major search terms.

5.2 Indentifying search term
         The following search strategy is used for the construction of search terms.
a) Use the Research Questions for the derivation of major terms, by identifying population, intervention and
outcome;
b) For these major terms, find the alternative spellings and synonyms;
c) Verify the key words in any relevant paper;
d) Use of Boolean Operators OR, AND

Results for (a)
RQ1: Multisourcing, software development multisourcing relationships, challenges, barriers, client, vendors,
Establishment and maintenance of multisourcing relationships.
RQ2: Multisourcing, Software development multisourcing relationships, success factors, client, vendors,
Establishment and maintenance of Multisourcing relationships

Results for (b)
RQ1:
         Multisourcing :( Multisourcing OR ―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR
―dual sourcing‖ OR ―multiple sourcing‖)
         Software development multisourcing relationships: (―multi-vendor relationships‖ OR ―multisourcing
relationships‖ OR ―multiple supplier relationships‖ OR ―dual sourcing relationships‖ OR ―software multi-
sourcing relationships‖ OR ―software multi-vendor relationships‖ OR ―multi-vendor collaboration‖ OR ―multi
vendor coordination‖ OR ―multi-vendors alliance‖ OR ―multi-vendors partnerships‖ OR ―multisourcing
contract‖)
Challenges: (challenges OR barriers OR problems OR complications)
Barriers: (risks OR failures OR barriers ―critical factors‖ OR ―risk analysis‖ OR ―critical factors‖)
                                               www.iosrjournals.org                                   27 | Page
Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol
Client: (customer OR clients OR users)
Vendors: (―service providers‖ OR supplier OR developer)
          Establishment and maintenance of multisourcing relationships: (―Building multi-sourcing
relationships‖ OR ―establishing multi-vendors relationships‖ OR ―multi-sourcing relationships management‖
OR ―strengthening multi vendors relationships‖)

RQ2:
          Multisourcing :(Multisourcing OR ―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR
―dual sourcing‖)
          Software development multisourcing relationships: (―multi-vendor relationships‖ OR ―multisourcing
relationships‖ OR ―multiple supplier relationships‖ OR ―dual sourcing relationships‖ OR ―software multi-
sourcing relationships‖ OR ―software multi-vendor relationships‖ OR ―multi-vendor collaboration‖ OR ―multi
vendor coordination‖ OR ―multi-vendors alliance‖ OR ―multi-vendors partnerships‖ OR ―multisourcing
contract‖)
Success factors :( ―Success elements‖ OR factors OR ―success factors‖ OR ―success parameters‖ OR ―key
factores‖ OR ―important factors‖)
Client: (customer OR clients OR users)
Vendors: (―service providers‖ OR supplier OR developer)
          Establishment and maintenance of multi-sourcing relationships: (―Building multi-sourcing
relationships‖ OR ―establishing multi-vendors relationships‖ OR ―multi-sourcing relationships management‖
OR ―strengthening multi vendors relationships‖)

Results for (C)
         Multi-sourcing, software multi-sourcing, multi vendors outsourcing, multi Supplier outsourcing, dual
sourcing, multi-vendors relationships, multi-vendors outsourcing, vendors relationships, critical success factors,
factors, challenges, software multi-sourcing models, dual sourcing relationships, vendors to vendors
relationships, vendors to client relationships, supplier relationship management.

Results for (d)
RQ1.
         (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple
sourcing‖)AND((―multi-vendor relationships‖ OR ―multisourcing relationships‖ OR ―multiple supplier
relationships‖ OR ―dual sourcing relationships‖ OR ―software multi-sourcing relationships‖ OR ―software
multi-vendor relationships‖ OR ―multi-vendor collaboration‖ OR ―multi vendor coordination‖ OR ―multi-
vendors alliance‖ OR ―multi-vendors partnerships‖ OR ―multisourcing contract‖ )OR(challenges OR ―barriers‖
OR ―problems‖ OR ―complications‖ )OR(―risks‖ OR failures OR barriers ―critical factors‖ OR ―risk analysis‖
OR ―critical factors‖ )OR (―customer‖ OR ―clients‖ OR ―users‖) OR(―service providers‖ OR ―supplier‖ OR
―developer‖)OR(―Building multi-sourcing relationships‖ OR ―establishing multi-vendors relationships‖ OR
―multi-sourcing relationships management‖ OR ―strengthening multi vendors relationships‖))

RQ2.
         (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple
sourcing‖)AND ((multi-vendor relationships‖ OR ―multisourcing relationships‖ OR ―multiple supplier
relationships‖ OR ―dual sourcing relationships‖ OR ―software multi-sourcing relationships‖ OR ―software
multi-vendor relationships‖ OR ―multi-vendor collaboration‖ OR ―multi vendor coordination‖ OR ―multi-
vendors alliance‖ OR ―multi-vendors partnerships‖ OR ―multisourcing contract‖) OR Success factors :(
―Success elements‖ OR factors OR ―success factors‖ OR ―success parameters‖ OR ―key factors‖ OR ―important
factors‖) OR (Customer OR clients OR users) OR (―Service providers‖ OR ―supplier‖ OR ―developer‖) OR
(―Building multi-sourcing relationships‖ OR ―establishing multi-vendors relationships‖ OR ―multi-sourcing
relationships management‖ OR ―strengthening multi vendors relationships‖))

5.3 Search term break up
         We will first use the search strings RQ1 and RQ2 mentioned in 3.2(d) as our search terms. As Some of
the databases don‘t allow the lengthy search strings we will split the search term into Smaller sub strings and
will do separate search for each of these search strings. Finally we will summarize the search results by
removing the redundancy. The breakup of the RQ1 and RQ2 are mentioned in the form smaller strings
mentioned below.
Search string 1
         (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple
sourcing‖)AND(―multi-vendor relationships‖ OR ―multisourcing relationships‖ OR ―multiple supplier

                                            www.iosrjournals.org                                        28 | Page
Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol
relationships‖ OR ―dual sourcing relationships‖ OR ―software multi-sourcing relationships‖ OR ―software
multi-vendor relationships‖ OR ―multi-vendor collaboration‖ OR ―multi vendor coordination‖ OR ―multi-
vendors alliance‖ OR ―multi-vendors partnerships‖ OR ―multisourcing contract‖)

Search string 2
         (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple
sourcing‖)AND (Challenges OR barriers OR problems OR complications)

Search string 3
         (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple
sourcing‖)AND (Risks OR failures OR barriers ―critical factors‖ OR ―risk analysis‖ OR ―critical factors‖)

Search string 4
         (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple
sourcing‖)AND (Customer OR clients OR users)

Search String 5
        (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple
sourcing‖)AND (Service providers OR supplier OR developer)

Search string 6
         (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple
sourcing‖)AND (―Building multi-sourcing relationships‖ OR ―establishing multi-vendors relationships‖ OR
―multi-sourcing relationships management‖ OR ―strengthening multi vendors relationships‖)

Search string 7
         (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple
sourcing‖)AND Success factors :( ―Success elements‖ OR factors OR ―success factors‖ OR ―success
parameters‖ OR ―key factors‖ OR ―important factors‖)

5.4 Resources to be searched
The following digital libraries and databases will be searched.
 IEEE Explore
 ACM Digital Library
 Google Scholar
 Science Direct
 Site Seer Digital Library
 Springer link

5.5 Search Constraints and validation
         The above selected digital libraries will be searched against each search string (string to string 7) with
out applying any Date boundaries.

5.6 Search Documentation
The search results will be documented in a table having the following information.
 Search conduction date
 Name of digital library
 Searched string used
 Date Constrain
 Total publication found
 Initial selection
 Final selection

1.7     Search Result Management
The records all the candidate papers from the digital libraries are kept in a directory. In which the
Record of each digital library is stored in separate directory, where each page is saved as .html page.
To be on safe side the the backup of the search results are also stored on Google Drive.



                                             www.iosrjournals.org                                        29 | Page
Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol
                              VI.         publication selection
6.1 Inclusion Criteria
          Inclusion criteria are used to select only that literature (research papers / reports / books) found in the
search results obtained. We will only select those research papers related to augmented reality. The inclusion
criteria are listed as below:
 Research studies and articles that are related to our protocol
 Research work that describe software multi-sourcing
 Research work that describes difficulties difficulties in software multi-sourcing
 Research work that identifies software multi-sourcing relationships
 Research papers and studies that describe multi-sourcing relationships
 Paper that describes the challenges of multi-sourcing relationships
 Research work that describes multi vendor‘s relationships.
 Research papers that describes multi supplies relationships management.
 Research papers that describes barriers and challenges in multi-sourcing relationships with clients and
     fellow vendors.
 Research papers and articles that describes critical success factors for the establishment and maintenance of
     long-lasting relationships with clients and fellow vendors in multi vendor software outsourcing.

6.2 Exclusion Criteria
         Exclusion criteria are used to decide which piece of literature (research papers / reports / books) found
by the search term will not be selected for review. The criteria are listed below:
 Research work that is not relevant to the research questions will be excluded.
 Literature that don‘t describe multi-sourcing relationships.
 Research work other then multi-sourcing and multi vendors.

6.3 Selecting primery sourecs
          Primary sources will be initially selected by analyzing the title, keywords and abstracts of searched
literature. This review will exclude / ignore those searched literature which have no relevance to the research
questions. The primary sources chosen during this initial selection process will be checked against the above
inclusion / exclusion criteria by reviewing through full text of the research papers. If any uncertainty occurs
regarding the inclusion / exclusion decision, the case will be sent to the secondary reviewer. The process will be
checked by the third reviewer. Inclusion / exclusion decision record regarding each primary source will be
maintained properly. This will include the justification whether or not the primary source has been included in
the final review.

                              VII.          publication quality assessment
         The conduction of quality measurement will be performed after the final selection of publications. The
quality checklist contains the following questions:
 Is it clear how the challenges/barriers faced by vendors in the establishment and maintenance of
    relationships with clients as well as the fellow vendors in multi-vendors software outsourcing situation were
    identified?
     Is it clear how the critical success factors to be developed by the vendors for establishment and
    maintenance of long-lasting relationships with client as well as the fellow vendors in multi-vendors
    software outsourcing situation were identified?
 Each of the above questions will be marked as ‗YES‘, ‗NO‘, ‗Partially‗ or N.A‘.

                                 VIII.          Data extraction strategy
8.1 Primery study data
The core aim of SDMRMM protocol is to extract the data which satisfies the RQ1 and RQ2.
The following data will be extracted from each selected research publication.
          Date of review, title, authors, references, database , methodology, sample population, publication
quality description, organization type, company size, location of analysis, year, CBs (Critical Barriers), CSFS
(Critical success factors).
8.1 Data Extraction process
          The review will be undertaken by a single researcher, who will be responsible for the data extraction. A
secondary reviewer and tertiary reviewer will be approached for guidance in case of an issue regarding the data
extraction. The reliability test will be performed after the data extraction process by the primary reviewer. The
secondary reviewer will select few publications randomly from the list of publication already chosen by the
primary reviewer. The secondary reviewer will independently extract the data from the randomly selected


                                              www.iosrjournals.org                                         30 | Page
Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol
publication. The results will then be compared with the results produced by the primary reviewer. The tertiary
reviewer will be approached for guidance during conducting the review.
Primary Reviewer:           Mr.Muhammad Salam
Secondary Reviewer:         Dr. Siffat Ullah Khan
8.2 Data storage
         The summarized data for each publication will be kept as a Microsoft Word/pdf document and will be
stored as soft form in personal laptops by all authors. A backup are kept at Google Drive.

                                                IX.            Data synthesis
        The synthesis of data will also be categorized into two parts as we have two research questions.
For the RQ1, the data will be synthesized by creating one summary table having the columns(S.No,
challenges/barriers, Frequency, Percentages) showing the list of all the factors along with their
frequencies and percentages. For the RQ2, the data will be synthesized by creating one summary table having
the columns (S.No, CSF, Frequency, Percentages) showing the list of all the factors along with their
frequencies and percentages.

                                                   X.            Divergences
       In case of any divergence from the protocol that may occur during the study will be recorded in an
Appendix to this report.

                                             XI.             Acknowledgment
         We are thankful Software Engineering Research Group at University of Malakand (SERG_UOM) for
the Review and their valuable comments in validation process of the protocol.

                                                            References
[1]    S. U. Khan, M. Niazi, and N. Ikram, "Software Development Outsourcing Relationships Trust: A Systematic Literature Review
       Protocol," presented at Evaluation and Assessment in Software Engineering, EASE 2010, Keele University, UK, 2010.
[2]    S. U. Khan, M. Niazi, and R. Ahmad, "Barriers in the Selection of Offshore Software Development Outsourcing Vendors: An
       Exploratory Study using a Systematic Literature Review," Information and Software Technology,(Elsevier), doi:
       10.1016/j.infsof.2010.08.003, 2010.
[3]    B. Kitchenham and C. Charters, "Guidelines for performing Systematic Literature Reviews in Software Engineering, Keele
       University and Durham University Joint Report," EBSE 2007-001, 2007.
[4]    H. S. Kehal and V. P. Singh, Outsourcing and offshoring in the 21st Century: A Socio-Economic Perspective.
[5]    J. K. HALVEY and B. M. MELBY, INFORMATION TECHNOLOGY OUTSOURCING TRANSACTIONS PROCESS,
       STRATEGIES, AND CONTRACTS, 2ND EDITION ed: John Wiley & Sons, Inc., Hoboken, New Jersey.Published simultaneously
       in Canada.
[6]    G. Wang, Z. Jiang, Z. Li, and W. Liu, " Supplier selection and order splitting in multiple-sourcing inventory systems," Frontiers of
       Mechanical Engineering in China, vol. 3, pp. 23-27.
[7]    R. Sharma, S. Apoorva, V. Madireddy, and V. Jain, "Best Practices for Communication between Client and Vendor in IT
       Outsourcing Projects," Journal of Information, Information Technology, and Organizations, vol. 3, 2008.
[8]    P. Kanawattanachai and Y. Yoo, "Dynamic Nature of Trust in Virtual Teams," The Journal of Strategic Information Systems, vol.
       11, pp. 187-213, 2002.
[9]    O. d. Gaudemar, "Multi-sourcing: benefits and challenges," vol. 2011.
[10]   "Egham, UK, August 27, 2009 — Gartner, Inc Three Pitfalls of Multisourcing," vol. 2011, 27 August 2009.
[11]   v. b. kartha, "Multi-Sourcing from Best of Breed Providers:Perspectives for BPO," vol. 2011, January 2007.
[12]   P. Kanawattanachai and Y. Yoo, "Dynamic Nature of Trust in Virtual Teams," Sprouts: Working Papers on Information Systems,
       vol. 2, 2002.
[13]   ShitaoYanga, JianYangb, and L. Abdel-Malek, "Sourcing with random yields and stochastic demand: A newsvendor approach,"
       Computers & Operations Research, vol. 34, pp. 3682 – 3690, 2007.
[14]   N. Levina and N. Su, "Global Multisourcing Strategy: TheEmergence of a Supplier Portfolio in Services Offshoring," Decision
       Sciences, vol. Volume 39 Number 3, pp. 541-570, August 2008.
[15]   " Meeting the Challenges of Supplier Relations in a Multisourcing Environment."
[16]   B. Kitchenham, "Procedures for Performing Systematic Reviews," Keele University Technical ReportTR/SE0401, 2004.
[17]   H. Zhang, M. A. Babar, and P. Tell, "Identifying relevant studies in software engineering," Information and Software Technology,
       vol. 53, pp. 625-637, 2011.
[18]   P. Brereton, B. A. Kitchenham, D. Budgen, M. Turner, and M. Khalil, "Lessons from applying the systematic literature review
       process within the software engineering domain," The Journal of Systems and Software, pp. 571–583, 2007.
[19]   H. Zhang, M. A. Babar, and P. Tell, "Identifying relevant studies in software engineering," Information and Software Technology,
       vol. 53, pp. 625-637, 2011.
[20]   M. J. Power, K. C. Desouza, and C. Bonifazi, The Outsourcing Handbook How to implement a successful outsourcing process: First
       published in Great Britain and the United States in 2006 by Kogan Page Limited.
[21]   M. Ali-Babar, J. Verner, and P. Nguyen, "Establishing and maintaining trust in software outsourcing relationships: An empirical
       investigation," The Journal of Systems and Software, vol. 80, pp. 1438–1449, 2007.
[22]   S. U. Khan and M. Niazi, "Systematic Literature Review Protocol for Software Outsourcing Vendors Readiness Model (SOVRM),
       Technical Report: TR/08-01, ISSN: 1353-7776, School of Computing and Maths, Keele University, UK," 2008.
[23]   M. J. Gallivan and W. Oh, "Analyzing IT Outsourcing Relationships as Alliances among Multiple Clients and Vendors," presented
       at Proceedings of the 32nd Hawaii international Conference on System Sciences, Hawaii, USA, 1999.
[24]   V. Imsland, "The Role of Trust in Global Software Outsourcing Relationships," in Department of Informatics: UNIVERSITY OF
       OSLO, 30th July 2003.

                                                      www.iosrjournals.org                                                     31 | Page

Weitere ähnliche Inhalte

Was ist angesagt?

Final Paper_Manik
Final Paper_ManikFinal Paper_Manik
Final Paper_Manik
Manik Verma
 
Supply Chain Management
Supply Chain ManagementSupply Chain Management
Supply Chain Management
Ron Calonica
 
Delportvervestvanheck Emj April 2004
Delportvervestvanheck   Emj April 2004Delportvervestvanheck   Emj April 2004
Delportvervestvanheck Emj April 2004
Eric van Heck
 
SOA In Insurance Industry 0.2
SOA In Insurance Industry 0.2SOA In Insurance Industry 0.2
SOA In Insurance Industry 0.2
Infogain
 

Was ist angesagt? (11)

IRJET- Identifying the Conflicts in the Software Requirement Engineering:...
IRJET-  	  Identifying the Conflicts in the Software Requirement Engineering:...IRJET-  	  Identifying the Conflicts in the Software Requirement Engineering:...
IRJET- Identifying the Conflicts in the Software Requirement Engineering:...
 
Bpm17industry10
Bpm17industry10Bpm17industry10
Bpm17industry10
 
Final Paper_Manik
Final Paper_ManikFinal Paper_Manik
Final Paper_Manik
 
Concept of Semantic Information Pool for manufacturing supply networks
Concept of Semantic Information Pool for manufacturing supply networksConcept of Semantic Information Pool for manufacturing supply networks
Concept of Semantic Information Pool for manufacturing supply networks
 
Thorny Issues of Stakeholder Identification and Prioritization in Requirement...
Thorny Issues of Stakeholder Identification and Prioritization in Requirement...Thorny Issues of Stakeholder Identification and Prioritization in Requirement...
Thorny Issues of Stakeholder Identification and Prioritization in Requirement...
 
CRESUS: A TOOL TO SUPPORT COLLABORATIVE REQUIREMENTS ELICITATION THROUGH ENHA...
CRESUS: A TOOL TO SUPPORT COLLABORATIVE REQUIREMENTS ELICITATION THROUGH ENHA...CRESUS: A TOOL TO SUPPORT COLLABORATIVE REQUIREMENTS ELICITATION THROUGH ENHA...
CRESUS: A TOOL TO SUPPORT COLLABORATIVE REQUIREMENTS ELICITATION THROUGH ENHA...
 
Supply Chain Management
Supply Chain ManagementSupply Chain Management
Supply Chain Management
 
Delportvervestvanheck Emj April 2004
Delportvervestvanheck   Emj April 2004Delportvervestvanheck   Emj April 2004
Delportvervestvanheck Emj April 2004
 
The Global Networked Value Circle
The Global Networked Value CircleThe Global Networked Value Circle
The Global Networked Value Circle
 
SOA In Insurance Industry 0.2
SOA In Insurance Industry 0.2SOA In Insurance Industry 0.2
SOA In Insurance Industry 0.2
 
Open standards in document output
Open standards in document outputOpen standards in document output
Open standards in document output
 

Andere mochten auch (9)

Debbie crespo comp 2 #1 paper
Debbie crespo comp 2 #1 paperDebbie crespo comp 2 #1 paper
Debbie crespo comp 2 #1 paper
 
#Ted #TedXEutropolis #Unitedstasiofamerica Tip of the Iceberg
#Ted #TedXEutropolis #Unitedstasiofamerica Tip of the Iceberg#Ted #TedXEutropolis #Unitedstasiofamerica Tip of the Iceberg
#Ted #TedXEutropolis #Unitedstasiofamerica Tip of the Iceberg
 
F0134249
F0134249F0134249
F0134249
 
Customer financing in Brazil
Customer financing in BrazilCustomer financing in Brazil
Customer financing in Brazil
 
Electronic Dicitionary of Bantik Language
Electronic Dicitionary of Bantik LanguageElectronic Dicitionary of Bantik Language
Electronic Dicitionary of Bantik Language
 
D0352630
D0352630D0352630
D0352630
 
D0142635
D0142635D0142635
D0142635
 
D0321823
D0321823D0321823
D0321823
 
C0110913
C0110913C0110913
C0110913
 

Ähnlich wie E0322431

Business and technical requirements of software as-a-service implications in ...
Business and technical requirements of software as-a-service implications in ...Business and technical requirements of software as-a-service implications in ...
Business and technical requirements of software as-a-service implications in ...
ijfcstjournal
 
Project Planning, Execution And Closure Essay
Project Planning, Execution And Closure EssayProject Planning, Execution And Closure Essay
Project Planning, Execution And Closure Essay
Jennifer Letterman
 
Software For Software Development Life Cycle
Software For Software Development Life CycleSoftware For Software Development Life Cycle
Software For Software Development Life Cycle
Christina Padilla
 
Net impact implementation application development life-cycle management in ba...
Net impact implementation application development life-cycle management in ba...Net impact implementation application development life-cycle management in ba...
Net impact implementation application development life-cycle management in ba...
CSITiaesprime
 

Ähnlich wie E0322431 (20)

Software Development Multi-Sourcing Relationship Management Model (Sdmrmm) P...
Software Development Multi-Sourcing Relationship Management  Model (Sdmrmm) P...Software Development Multi-Sourcing Relationship Management  Model (Sdmrmm) P...
Software Development Multi-Sourcing Relationship Management Model (Sdmrmm) P...
 
Agile Customer Engagement A Longitudinal Qualitative Case Study
Agile Customer Engagement  A Longitudinal Qualitative Case StudyAgile Customer Engagement  A Longitudinal Qualitative Case Study
Agile Customer Engagement A Longitudinal Qualitative Case Study
 
Portfolio Cost Management in Offshore Software Development Outsourcing Relat...
Portfolio Cost Management in Offshore Software Development  Outsourcing Relat...Portfolio Cost Management in Offshore Software Development  Outsourcing Relat...
Portfolio Cost Management in Offshore Software Development Outsourcing Relat...
 
Business and technical requirements of software as-a-service implications in ...
Business and technical requirements of software as-a-service implications in ...Business and technical requirements of software as-a-service implications in ...
Business and technical requirements of software as-a-service implications in ...
 
Vendor Management - An Overview (Project File)
Vendor Management - An Overview (Project File)Vendor Management - An Overview (Project File)
Vendor Management - An Overview (Project File)
 
Project Planning, Execution And Closure Essay
Project Planning, Execution And Closure EssayProject Planning, Execution And Closure Essay
Project Planning, Execution And Closure Essay
 
H017245157
H017245157H017245157
H017245157
 
DevOps shifting software engineering strategy Value based perspective
DevOps shifting software engineering strategy Value based perspectiveDevOps shifting software engineering strategy Value based perspective
DevOps shifting software engineering strategy Value based perspective
 
Not All Collaboration Solutions are Built the Same
Not All Collaboration Solutions are Built the Same Not All Collaboration Solutions are Built the Same
Not All Collaboration Solutions are Built the Same
 
Forrester Market Overview Projectbased Erp For Service Delivery Professional ...
Forrester Market Overview Projectbased Erp For Service Delivery Professional ...Forrester Market Overview Projectbased Erp For Service Delivery Professional ...
Forrester Market Overview Projectbased Erp For Service Delivery Professional ...
 
Forrester Marktonderzoek: Project ERP
Forrester Marktonderzoek: Project ERPForrester Marktonderzoek: Project ERP
Forrester Marktonderzoek: Project ERP
 
Market Overview Project Based Erp For Service Delivery
Market Overview Project Based Erp For Service DeliveryMarket Overview Project Based Erp For Service Delivery
Market Overview Project Based Erp For Service Delivery
 
EXPLORING THE LINK BETWEEN LEADERSHIP AND DEVOPS PRACTICE AND PRINCIPLE ADOPTION
EXPLORING THE LINK BETWEEN LEADERSHIP AND DEVOPS PRACTICE AND PRINCIPLE ADOPTIONEXPLORING THE LINK BETWEEN LEADERSHIP AND DEVOPS PRACTICE AND PRINCIPLE ADOPTION
EXPLORING THE LINK BETWEEN LEADERSHIP AND DEVOPS PRACTICE AND PRINCIPLE ADOPTION
 
Software For Software Development Life Cycle
Software For Software Development Life CycleSoftware For Software Development Life Cycle
Software For Software Development Life Cycle
 
Net impact implementation application development life-cycle management in ba...
Net impact implementation application development life-cycle management in ba...Net impact implementation application development life-cycle management in ba...
Net impact implementation application development life-cycle management in ba...
 
EXPLORING THE LINK BETWEEN LEADERSHIP AND DEVOPS PRACTICE AND PRINCIPLE ADOPTION
EXPLORING THE LINK BETWEEN LEADERSHIP AND DEVOPS PRACTICE AND PRINCIPLE ADOPTIONEXPLORING THE LINK BETWEEN LEADERSHIP AND DEVOPS PRACTICE AND PRINCIPLE ADOPTION
EXPLORING THE LINK BETWEEN LEADERSHIP AND DEVOPS PRACTICE AND PRINCIPLE ADOPTION
 
An Approach To Product Roadmapping In Small Software Product Businesses
An Approach To Product Roadmapping In Small Software Product BusinessesAn Approach To Product Roadmapping In Small Software Product Businesses
An Approach To Product Roadmapping In Small Software Product Businesses
 
An Empirical Evaluation of Capability Modelling using Design Rationale.pdf
An Empirical Evaluation of Capability Modelling using Design Rationale.pdfAn Empirical Evaluation of Capability Modelling using Design Rationale.pdf
An Empirical Evaluation of Capability Modelling using Design Rationale.pdf
 
Secured Cloud ERP
Secured Cloud ERPSecured Cloud ERP
Secured Cloud ERP
 
Project Organizational Responsibility Model - ORM
Project Organizational Responsibility Model -  ORMProject Organizational Responsibility Model -  ORM
Project Organizational Responsibility Model - ORM
 

Mehr von iosrjournals (20)

I0114549
I0114549I0114549
I0114549
 
H0124246
H0124246H0124246
H0124246
 
H0114044
H0114044H0114044
H0114044
 
G0145458
G0145458G0145458
G0145458
 
G0135059
G0135059G0135059
G0135059
 
G0123541
G0123541G0123541
G0123541
 
G0113839
G0113839G0113839
G0113839
 
F0144153
F0144153F0144153
F0144153
 
F0122934
F0122934F0122934
F0122934
 
F0112937
F0112937F0112937
F0112937
 
E0143640
E0143640E0143640
E0143640
 
E0133641
E0133641E0133641
E0133641
 
E0112128
E0112128E0112128
E0112128
 
D0133235
D0133235D0133235
D0133235
 
D0121720
D0121720D0121720
D0121720
 
D0111420
D0111420D0111420
D0111420
 
C0141625
C0141625C0141625
C0141625
 
C0132131
C0132131C0132131
C0132131
 
C0121116
C0121116C0121116
C0121116
 
B0140815
B0140815B0140815
B0140815
 

Kürzlich hochgeladen

Why Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire businessWhy Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire business
panagenda
 
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
?#DUbAI#??##{{(☎️+971_581248768%)**%*]'#abortion pills for sale in dubai@
 

Kürzlich hochgeladen (20)

Corporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptxCorporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptx
 
Apidays Singapore 2024 - Modernizing Securities Finance by Madhu Subbu
Apidays Singapore 2024 - Modernizing Securities Finance by Madhu SubbuApidays Singapore 2024 - Modernizing Securities Finance by Madhu Subbu
Apidays Singapore 2024 - Modernizing Securities Finance by Madhu Subbu
 
A Year of the Servo Reboot: Where Are We Now?
A Year of the Servo Reboot: Where Are We Now?A Year of the Servo Reboot: Where Are We Now?
A Year of the Servo Reboot: Where Are We Now?
 
Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...
Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...
Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...
 
DBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor PresentationDBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor Presentation
 
Boost Fertility New Invention Ups Success Rates.pdf
Boost Fertility New Invention Ups Success Rates.pdfBoost Fertility New Invention Ups Success Rates.pdf
Boost Fertility New Invention Ups Success Rates.pdf
 
FWD Group - Insurer Innovation Award 2024
FWD Group - Insurer Innovation Award 2024FWD Group - Insurer Innovation Award 2024
FWD Group - Insurer Innovation Award 2024
 
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
TrustArc Webinar - Unlock the Power of AI-Driven Data DiscoveryTrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
 
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
 
AWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of TerraformAWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of Terraform
 
TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments
TrustArc Webinar - Stay Ahead of US State Data Privacy Law DevelopmentsTrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments
TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments
 
Automating Google Workspace (GWS) & more with Apps Script
Automating Google Workspace (GWS) & more with Apps ScriptAutomating Google Workspace (GWS) & more with Apps Script
Automating Google Workspace (GWS) & more with Apps Script
 
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected WorkerHow to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected Worker
 
Apidays New York 2024 - The value of a flexible API Management solution for O...
Apidays New York 2024 - The value of a flexible API Management solution for O...Apidays New York 2024 - The value of a flexible API Management solution for O...
Apidays New York 2024 - The value of a flexible API Management solution for O...
 
Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...
Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...
Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...
 
AXA XL - Insurer Innovation Award Americas 2024
AXA XL - Insurer Innovation Award Americas 2024AXA XL - Insurer Innovation Award Americas 2024
AXA XL - Insurer Innovation Award Americas 2024
 
Why Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire businessWhy Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire business
 
ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke
ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemkeProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke
ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke
 
Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood
Polkadot JAM Slides - Token2049 - By Dr. Gavin WoodPolkadot JAM Slides - Token2049 - By Dr. Gavin Wood
Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood
 
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
 

E0322431

  • 1. IOSR Journal of Computer Engineering (IOSRJCE) ISSN: 2278-0661 Volume 3, Issue 2 (July-Aug. 2012), PP 24-31 www.iosrjournals.org Software Development Multi-Sourcing Relationship Management Model (Sdmrmm) Protocol (A Systematic Literature Review) Muhammad Salam1, Dr.Siffat Ullah Khan2 1 (Department of Computer Science and IT, University of Malakand, Pakistan) 2 (Department, Computer Science and IT/Software Engineering, University of Malakand, Pakistan) Abstract :CONTEXT: Software development multi-sourcing is a modern software engineering paradigm in which the software project is contracted out to multi-vendors. In software multi-sourcing, there is one client and many vendors involved in the outsourcing contract. The client relies on more than one outsourcing vendors for the fulfillment of the software development activity. OBJECTIVE: The objective of this study is to develop SDMRMM to assist multi-sourcing vendor organizations in establishing, strengthening and maintenance of the relationships with fellow vendors and client in multi- sourcing situation. The model is for vendor to vendor and vendor to customer relationships in multi-sourcing paradigm. METHOD: we have developed a systematic literature review (SLR) protocol for software development multi- sourcing relationships management model (SDMRMM) from vendor’s perspective. SLR is based on a structured protocol and is therefore different from ordinary literature view. EXPECTED OUTCOME: The anticipated outcome of this review will be a list of challenges faced by vendors in establishment and maintenance of relationships with Clint as well as fellow vendors in multi-vendors software outsourcing also critical success factors for establishment and maintenance of log-lasting relationships will be identified. Keywords: Software Multisourcing; Multi-vendors outsourcing; Multisourcing relationships; I. Introduction Keeping in view global software development, software outsourcing is a new software engineering pattern[2].This research proposal describes the systematic literature review (SLR) [3] protocol which will be used to investigate that what are the challenges faced by vendors in the establishment and maintenance of multi- vendor outsourcing relationships and what are the critical success factors to be developed by vendors for the success of multi-source project. Identifying the challenges and critical success factors will help the vendors to establish and maintain long-lasting relationships with fellow vendors as well as clients. This may also help to ensure the successful outcomes of the multi sourced software projects. Multi-sourcing is sometime called ―multi-vendor outsourcing‖ OR ―multi-supplier sourcing‖ [4].In multi-sourcing, the client has one outsourcing contract with multiple suppliers. A multi-sourcing paradigm allows a client to engage multiple vendors for various components of software project that are then jointly performed by multiple suppliers. since the work is performed together by multi vendors, this implies that a cooperative and competitive environment exists between the suppliers working jointly as shown in the Fig.1[4]. Fig.1 A typical multisourcing situation There are five research questions as mentioned in section 3 of this protocol that have motivated the work reported in this research study. The core purpose of this study is to build Software Development Multi-sourcing Relationship Management Model (SDMRMM).The model will help software outsourcing organizations (vendors) to establish sound and long lasting relationships with fellow vendors and clients in a software multisourcing. The outsourcing may be unisourcing or multi-sourcing, prior to undertake software project outsourcing, the customer decides either to go for unisourcing or multi-sourcing. There are clear differences between the two approaches. The most important difference between unisourcing and multi-sourcing is that they require different www.iosrjournals.org 24 | Page
  • 2. Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol internal management structures. Multisourcing will need wider internal management which has the capability to accommodate several suppliers at one time. Moreover there are other compulsions. In Unisourcing one party perform its promise whereby, in multi-sourcing more than one party held responsible in case of project failure. The cost and return factors along with risk of these two approaches are taken into consideration[5].Multi sourcing is preferred comparatively because it has many advantages for customers, for example, it creates a competing environment and decreases to maximum extent the risk of project failure, and enhance the quality of the software. Furthermore, multi sourcing is practiced when the suppliers feel that they are deficient in terms of capabilities[6].―Risk sharing is, hence, a common practice for parties adopting multiple outsourcing relationships‖[7].Different studies show that trust is critical for all business relationships [8].However the focus of our study is on multi-vendors outsourcing relationships. A number of researchers have tried to address some of the issues of Multi-outsourcing, e.g. [9-11].Placement of an order in an environment, where many suppliers are working, needs proper attention and care, For reducing the average inventory cost, questions like when to place an order, how to order and how many order from each suppliers, are to be answered[6].The manager should establish and maintain productive and good working relationship among the members of virtual teams to achieve the predetermined results and goals, other studies in the literature have also showed the importance of trust in virtual teams [12].Establishing and maintaining good relationship with the outsourcing partners and suppliers helps the managers to share and transfer skills, and also ensure the trust worthiness and confidence of the suppliers on partners [13].―Recently, as global business environments have become increasingly complex and turbulent with the rise of off- shoring, firms started selecting and combining relationships with multiple service providers based in different countries as part of their sourcing strategy― [14].―New approaches and skills are required to effectively manage the increased volume and complexity of relationships between the various parties involved in multi-sourcing deals―[15].However, nobody has used the Systematic Literature Review (SLR) [3] approach in order to identify the challenges faced by vendors in multi-vendor outsourcing relationship and critical success factors to be developed by vendors for successful multi-vendor outsourcing relationships.―A systematic literature review is a means of identifying, evaluating and interpreting all available research relevant to a particular research question, or topic area, or phenomenon of interest‖[16].―systemic literature review (SLR) has become an important research methodology in software engineering, since the introduction of evidence-based software engineering(EBSE) in 2004―[17].The purpose of this study is to develop Software Development Multi-sourcing Relationships Management Model (SDMRMM) the model is useful for software vendors which works in multi-vendors outsourcing. During the model and protocol development I have studied a number of systemic literature reviews [18, 19]. II. Background of multi-sourcing Multi sourcing is the combination of two words-‗Multi‘ and ‗Sourcing‘. Hence Multi mean many and ―Sourcing refers to the act of transferring work, responsibilities and decision rights to someone else‖ or in other words we can say that ―Sourcing is the act of transferring work from one entity to another‖ so we can say that multi sourcing is the transferring of work (software) from one entity (Client) to multiple entities (Vendors).According to [20] there are three components of outsourcing 1) Client 2) Vendor 3) Project, The organization transferring the work is referred to as the client, the organization that conducts the work and makes decisions is the vendor, and the scope of the work is captured in a project as shown in Fig.2 Fig.2 ―Software development outsourcing is defined as a situation where a company (a client) contracts out all or part of its software development activates to another company (a vendor), who provides agreed services for remuneration‖ [21]. ―In today‘s global services outsourcing arena, increasing numbers of companies adopt multi-sourcing, that is, they select and combine information technology (IT) and business services from multiple providers‖ [14]. ―Multi-sourcing is when you outsource functions to more than one vendor. Multi-sourcing involves breaking up the project into several components that can be handled by independent vendors and usually occurs during a total outsourcing project. Multi-sourcing encourages competition between vendors and creates a shared objective to Perform at high levels‖ [20]. Components of multi-sourcing Relationship are shown in the following Fig.1. www.iosrjournals.org 25 | Page
  • 3. Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol According to [22] are various types of outsourcing which can be divided into two main categories as shown in the Fig.3 Fig.3 various types of outsourcing The research work reported in this study is related to multisourcing relationships management from vendor to vendor (V2V) and from vendor to customer (V2C). The research is based on systematic literature review. The protocol for SDMRMM is developed on the basis of five research questions which are mentioned in section 3 of this protocol. III. Research Questions There are five research questions that have motivated the work reported in this research proposal. RQ1. What are the challenges/barriers, as identified in the literature, faced by vendor‘s in the establishment and maintenance of relationships with client as well as the fellow vendors in multi-vendors software outsourcing situation? RQ2. What are the critical success factors, as identified in the literature, to be developed by vendors for the establishment and maintenance of long-lasting relationships with client as well as the fellow vendors in multi- vendors software outsourcing situation? RQ3. What are the challenges/barriers, as identified in the outsourcing industry, faced by vendors in the establishment and maintenance of relationships with client as well as the fellow vendors in multi-vendors software outsourcing situation? RQ4. What are the critical success factors, as identified in the outsourcing industry, to be developed by vendors for the establishment and maintenance of long-lasting relationships with client as well as the fellow vendors in multi-vendors software outsourcing situation? RQ5. What are the real-world practices for addressing the identified success factors and barriers in multi- vendors software outsourcing situation? For RQ1 and RQ2 the identification of CBs (Critical Barriers) and CSFs (Critical Success Factors), we will use systematic literature review (SLR). We will conduct empirical study (questionnaire survey) for the validation of SRL findings and to answer research questions RQ3, RQ4 and RQ5. The Software Development multi-sourcing relationship Management Model (SDMRMM) will be developed using SLR guidelines[3, 16] this model will help software outsourcing organizations (vendors) to indentify the challenges/barriers in establishment and maintenance of relationships with client as well as fellow vendors in multi-vendors software outsourcing, the proposed model will be useful for establishment and maintenance of log-lasting relationships with client and fellow vendors. IV. Systematic Literature Review Protocol for SDMRMM A systematic literature review is a new research methodology, it is a way of identifying, evaluating and interpreting all available research relevant to a particular research question, or topic area, or phenomenon of interest [16]. Now a a day‘s systematic literature review has become an important research methodology [17]. SLR has the following main three phases.  Planning the review  Conducting the review  Reporting the review The expected outcomes of this review will be the identification of different CSFs and CBs that play important role in software development multisourcing relationships. 4.1 Constructing Search Term The following details will help in designing a search term relevant to our research questions.  Population: Software Development multisourcing relationship, multi-vendors software outsourcing relationships, multi supplier software outsourcing, client and vendors.  Intervention: challenges, barriers, critical success factors, establishment of relationships, maintenance relationships. www.iosrjournals.org 26 | Page
  • 4. Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol  Outcomes of relevance: establishment and maintenance of long-lasting relationships, identification of challenges/barriers in establishment and maintenance of relationships with client as well as fellow vendors in multi-vendors software outsourcing, Software Development Multi-sourcing Relationship Management Model (SDMRMM), long-lasting relationships with clients, long-lasting relationships with fellow vendors.  Experimental Design: Empirical studies, systematic literature review, theoretical studies, case studies, expert‗s opinions, etc. Examples of the Research Questions containing the above details are: RQ1:  [Challenges/barriers] INTERVENTION  [Software Multi-sourcing Relationships] POPULATION  Faced by vendor  [in the establishment and maintenance of relationships with client as well as the fellow vendors in multi-vendors software outsourcing situation] OUTCOMES OF RELEVANCE V. search strategy 5.1 Trail search A trial search was conducted using the following search string on selected digital libraries as shown section 5.4 of this protocol. (Multisourcing OR ―software multisourcing‖ OR ―multi vendors outsourcing" OR ―multi Supplier outsourcing‖ OR ―dual sourcing‖) AND (―multi-vendors relationships‖ OR "multi-vendors outsourcing" OR ―outsourcing relationships"). S.No Digital library Search Conduction Date IEEE Explore 15,55 26 April 2012 ACM Digital Library 1214 26 April 2012 Google Scholar 232 26 April 2012 Science Direct 1084 26 April 2012 Site Seer Digital Library 1116 26 April 2012 Springer link 236 + 247 26 April 2012 Table 2: Trail Search Results The papers retrieved through this search string will be used as a guide for the development and validation of the major search terms. 5.2 Indentifying search term The following search strategy is used for the construction of search terms. a) Use the Research Questions for the derivation of major terms, by identifying population, intervention and outcome; b) For these major terms, find the alternative spellings and synonyms; c) Verify the key words in any relevant paper; d) Use of Boolean Operators OR, AND Results for (a) RQ1: Multisourcing, software development multisourcing relationships, challenges, barriers, client, vendors, Establishment and maintenance of multisourcing relationships. RQ2: Multisourcing, Software development multisourcing relationships, success factors, client, vendors, Establishment and maintenance of Multisourcing relationships Results for (b) RQ1: Multisourcing :( Multisourcing OR ―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple sourcing‖) Software development multisourcing relationships: (―multi-vendor relationships‖ OR ―multisourcing relationships‖ OR ―multiple supplier relationships‖ OR ―dual sourcing relationships‖ OR ―software multi- sourcing relationships‖ OR ―software multi-vendor relationships‖ OR ―multi-vendor collaboration‖ OR ―multi vendor coordination‖ OR ―multi-vendors alliance‖ OR ―multi-vendors partnerships‖ OR ―multisourcing contract‖) Challenges: (challenges OR barriers OR problems OR complications) Barriers: (risks OR failures OR barriers ―critical factors‖ OR ―risk analysis‖ OR ―critical factors‖) www.iosrjournals.org 27 | Page
  • 5. Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol Client: (customer OR clients OR users) Vendors: (―service providers‖ OR supplier OR developer) Establishment and maintenance of multisourcing relationships: (―Building multi-sourcing relationships‖ OR ―establishing multi-vendors relationships‖ OR ―multi-sourcing relationships management‖ OR ―strengthening multi vendors relationships‖) RQ2: Multisourcing :(Multisourcing OR ―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖) Software development multisourcing relationships: (―multi-vendor relationships‖ OR ―multisourcing relationships‖ OR ―multiple supplier relationships‖ OR ―dual sourcing relationships‖ OR ―software multi- sourcing relationships‖ OR ―software multi-vendor relationships‖ OR ―multi-vendor collaboration‖ OR ―multi vendor coordination‖ OR ―multi-vendors alliance‖ OR ―multi-vendors partnerships‖ OR ―multisourcing contract‖) Success factors :( ―Success elements‖ OR factors OR ―success factors‖ OR ―success parameters‖ OR ―key factores‖ OR ―important factors‖) Client: (customer OR clients OR users) Vendors: (―service providers‖ OR supplier OR developer) Establishment and maintenance of multi-sourcing relationships: (―Building multi-sourcing relationships‖ OR ―establishing multi-vendors relationships‖ OR ―multi-sourcing relationships management‖ OR ―strengthening multi vendors relationships‖) Results for (C) Multi-sourcing, software multi-sourcing, multi vendors outsourcing, multi Supplier outsourcing, dual sourcing, multi-vendors relationships, multi-vendors outsourcing, vendors relationships, critical success factors, factors, challenges, software multi-sourcing models, dual sourcing relationships, vendors to vendors relationships, vendors to client relationships, supplier relationship management. Results for (d) RQ1. (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple sourcing‖)AND((―multi-vendor relationships‖ OR ―multisourcing relationships‖ OR ―multiple supplier relationships‖ OR ―dual sourcing relationships‖ OR ―software multi-sourcing relationships‖ OR ―software multi-vendor relationships‖ OR ―multi-vendor collaboration‖ OR ―multi vendor coordination‖ OR ―multi- vendors alliance‖ OR ―multi-vendors partnerships‖ OR ―multisourcing contract‖ )OR(challenges OR ―barriers‖ OR ―problems‖ OR ―complications‖ )OR(―risks‖ OR failures OR barriers ―critical factors‖ OR ―risk analysis‖ OR ―critical factors‖ )OR (―customer‖ OR ―clients‖ OR ―users‖) OR(―service providers‖ OR ―supplier‖ OR ―developer‖)OR(―Building multi-sourcing relationships‖ OR ―establishing multi-vendors relationships‖ OR ―multi-sourcing relationships management‖ OR ―strengthening multi vendors relationships‖)) RQ2. (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple sourcing‖)AND ((multi-vendor relationships‖ OR ―multisourcing relationships‖ OR ―multiple supplier relationships‖ OR ―dual sourcing relationships‖ OR ―software multi-sourcing relationships‖ OR ―software multi-vendor relationships‖ OR ―multi-vendor collaboration‖ OR ―multi vendor coordination‖ OR ―multi- vendors alliance‖ OR ―multi-vendors partnerships‖ OR ―multisourcing contract‖) OR Success factors :( ―Success elements‖ OR factors OR ―success factors‖ OR ―success parameters‖ OR ―key factors‖ OR ―important factors‖) OR (Customer OR clients OR users) OR (―Service providers‖ OR ―supplier‖ OR ―developer‖) OR (―Building multi-sourcing relationships‖ OR ―establishing multi-vendors relationships‖ OR ―multi-sourcing relationships management‖ OR ―strengthening multi vendors relationships‖)) 5.3 Search term break up We will first use the search strings RQ1 and RQ2 mentioned in 3.2(d) as our search terms. As Some of the databases don‘t allow the lengthy search strings we will split the search term into Smaller sub strings and will do separate search for each of these search strings. Finally we will summarize the search results by removing the redundancy. The breakup of the RQ1 and RQ2 are mentioned in the form smaller strings mentioned below. Search string 1 (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple sourcing‖)AND(―multi-vendor relationships‖ OR ―multisourcing relationships‖ OR ―multiple supplier www.iosrjournals.org 28 | Page
  • 6. Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol relationships‖ OR ―dual sourcing relationships‖ OR ―software multi-sourcing relationships‖ OR ―software multi-vendor relationships‖ OR ―multi-vendor collaboration‖ OR ―multi vendor coordination‖ OR ―multi- vendors alliance‖ OR ―multi-vendors partnerships‖ OR ―multisourcing contract‖) Search string 2 (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple sourcing‖)AND (Challenges OR barriers OR problems OR complications) Search string 3 (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple sourcing‖)AND (Risks OR failures OR barriers ―critical factors‖ OR ―risk analysis‖ OR ―critical factors‖) Search string 4 (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple sourcing‖)AND (Customer OR clients OR users) Search String 5 (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple sourcing‖)AND (Service providers OR supplier OR developer) Search string 6 (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple sourcing‖)AND (―Building multi-sourcing relationships‖ OR ―establishing multi-vendors relationships‖ OR ―multi-sourcing relationships management‖ OR ―strengthening multi vendors relationships‖) Search string 7 (―Multi-vendor outsourcing‖ OR ―multiple-supplier sourcing‖ OR ―dual sourcing‖ OR ―multiple sourcing‖)AND Success factors :( ―Success elements‖ OR factors OR ―success factors‖ OR ―success parameters‖ OR ―key factors‖ OR ―important factors‖) 5.4 Resources to be searched The following digital libraries and databases will be searched.  IEEE Explore  ACM Digital Library  Google Scholar  Science Direct  Site Seer Digital Library  Springer link 5.5 Search Constraints and validation The above selected digital libraries will be searched against each search string (string to string 7) with out applying any Date boundaries. 5.6 Search Documentation The search results will be documented in a table having the following information.  Search conduction date  Name of digital library  Searched string used  Date Constrain  Total publication found  Initial selection  Final selection 1.7 Search Result Management The records all the candidate papers from the digital libraries are kept in a directory. In which the Record of each digital library is stored in separate directory, where each page is saved as .html page. To be on safe side the the backup of the search results are also stored on Google Drive. www.iosrjournals.org 29 | Page
  • 7. Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol VI. publication selection 6.1 Inclusion Criteria Inclusion criteria are used to select only that literature (research papers / reports / books) found in the search results obtained. We will only select those research papers related to augmented reality. The inclusion criteria are listed as below:  Research studies and articles that are related to our protocol  Research work that describe software multi-sourcing  Research work that describes difficulties difficulties in software multi-sourcing  Research work that identifies software multi-sourcing relationships  Research papers and studies that describe multi-sourcing relationships  Paper that describes the challenges of multi-sourcing relationships  Research work that describes multi vendor‘s relationships.  Research papers that describes multi supplies relationships management.  Research papers that describes barriers and challenges in multi-sourcing relationships with clients and fellow vendors.  Research papers and articles that describes critical success factors for the establishment and maintenance of long-lasting relationships with clients and fellow vendors in multi vendor software outsourcing. 6.2 Exclusion Criteria Exclusion criteria are used to decide which piece of literature (research papers / reports / books) found by the search term will not be selected for review. The criteria are listed below:  Research work that is not relevant to the research questions will be excluded.  Literature that don‘t describe multi-sourcing relationships.  Research work other then multi-sourcing and multi vendors. 6.3 Selecting primery sourecs Primary sources will be initially selected by analyzing the title, keywords and abstracts of searched literature. This review will exclude / ignore those searched literature which have no relevance to the research questions. The primary sources chosen during this initial selection process will be checked against the above inclusion / exclusion criteria by reviewing through full text of the research papers. If any uncertainty occurs regarding the inclusion / exclusion decision, the case will be sent to the secondary reviewer. The process will be checked by the third reviewer. Inclusion / exclusion decision record regarding each primary source will be maintained properly. This will include the justification whether or not the primary source has been included in the final review. VII. publication quality assessment The conduction of quality measurement will be performed after the final selection of publications. The quality checklist contains the following questions:  Is it clear how the challenges/barriers faced by vendors in the establishment and maintenance of relationships with clients as well as the fellow vendors in multi-vendors software outsourcing situation were identified?  Is it clear how the critical success factors to be developed by the vendors for establishment and maintenance of long-lasting relationships with client as well as the fellow vendors in multi-vendors software outsourcing situation were identified?  Each of the above questions will be marked as ‗YES‘, ‗NO‘, ‗Partially‗ or N.A‘. VIII. Data extraction strategy 8.1 Primery study data The core aim of SDMRMM protocol is to extract the data which satisfies the RQ1 and RQ2. The following data will be extracted from each selected research publication. Date of review, title, authors, references, database , methodology, sample population, publication quality description, organization type, company size, location of analysis, year, CBs (Critical Barriers), CSFS (Critical success factors). 8.1 Data Extraction process The review will be undertaken by a single researcher, who will be responsible for the data extraction. A secondary reviewer and tertiary reviewer will be approached for guidance in case of an issue regarding the data extraction. The reliability test will be performed after the data extraction process by the primary reviewer. The secondary reviewer will select few publications randomly from the list of publication already chosen by the primary reviewer. The secondary reviewer will independently extract the data from the randomly selected www.iosrjournals.org 30 | Page
  • 8. Software Development Multi-sourcing Relationship Management Model (SDMRMM) Protocol publication. The results will then be compared with the results produced by the primary reviewer. The tertiary reviewer will be approached for guidance during conducting the review. Primary Reviewer: Mr.Muhammad Salam Secondary Reviewer: Dr. Siffat Ullah Khan 8.2 Data storage The summarized data for each publication will be kept as a Microsoft Word/pdf document and will be stored as soft form in personal laptops by all authors. A backup are kept at Google Drive. IX. Data synthesis The synthesis of data will also be categorized into two parts as we have two research questions. For the RQ1, the data will be synthesized by creating one summary table having the columns(S.No, challenges/barriers, Frequency, Percentages) showing the list of all the factors along with their frequencies and percentages. For the RQ2, the data will be synthesized by creating one summary table having the columns (S.No, CSF, Frequency, Percentages) showing the list of all the factors along with their frequencies and percentages. X. Divergences In case of any divergence from the protocol that may occur during the study will be recorded in an Appendix to this report. XI. Acknowledgment We are thankful Software Engineering Research Group at University of Malakand (SERG_UOM) for the Review and their valuable comments in validation process of the protocol. References [1] S. U. Khan, M. Niazi, and N. Ikram, "Software Development Outsourcing Relationships Trust: A Systematic Literature Review Protocol," presented at Evaluation and Assessment in Software Engineering, EASE 2010, Keele University, UK, 2010. [2] S. U. Khan, M. Niazi, and R. Ahmad, "Barriers in the Selection of Offshore Software Development Outsourcing Vendors: An Exploratory Study using a Systematic Literature Review," Information and Software Technology,(Elsevier), doi: 10.1016/j.infsof.2010.08.003, 2010. [3] B. Kitchenham and C. Charters, "Guidelines for performing Systematic Literature Reviews in Software Engineering, Keele University and Durham University Joint Report," EBSE 2007-001, 2007. [4] H. S. Kehal and V. P. Singh, Outsourcing and offshoring in the 21st Century: A Socio-Economic Perspective. [5] J. K. HALVEY and B. M. MELBY, INFORMATION TECHNOLOGY OUTSOURCING TRANSACTIONS PROCESS, STRATEGIES, AND CONTRACTS, 2ND EDITION ed: John Wiley & Sons, Inc., Hoboken, New Jersey.Published simultaneously in Canada. [6] G. Wang, Z. Jiang, Z. Li, and W. Liu, " Supplier selection and order splitting in multiple-sourcing inventory systems," Frontiers of Mechanical Engineering in China, vol. 3, pp. 23-27. [7] R. Sharma, S. Apoorva, V. Madireddy, and V. Jain, "Best Practices for Communication between Client and Vendor in IT Outsourcing Projects," Journal of Information, Information Technology, and Organizations, vol. 3, 2008. [8] P. Kanawattanachai and Y. Yoo, "Dynamic Nature of Trust in Virtual Teams," The Journal of Strategic Information Systems, vol. 11, pp. 187-213, 2002. [9] O. d. Gaudemar, "Multi-sourcing: benefits and challenges," vol. 2011. [10] "Egham, UK, August 27, 2009 — Gartner, Inc Three Pitfalls of Multisourcing," vol. 2011, 27 August 2009. [11] v. b. kartha, "Multi-Sourcing from Best of Breed Providers:Perspectives for BPO," vol. 2011, January 2007. [12] P. Kanawattanachai and Y. Yoo, "Dynamic Nature of Trust in Virtual Teams," Sprouts: Working Papers on Information Systems, vol. 2, 2002. [13] ShitaoYanga, JianYangb, and L. Abdel-Malek, "Sourcing with random yields and stochastic demand: A newsvendor approach," Computers & Operations Research, vol. 34, pp. 3682 – 3690, 2007. [14] N. Levina and N. Su, "Global Multisourcing Strategy: TheEmergence of a Supplier Portfolio in Services Offshoring," Decision Sciences, vol. Volume 39 Number 3, pp. 541-570, August 2008. [15] " Meeting the Challenges of Supplier Relations in a Multisourcing Environment." [16] B. Kitchenham, "Procedures for Performing Systematic Reviews," Keele University Technical ReportTR/SE0401, 2004. [17] H. Zhang, M. A. Babar, and P. Tell, "Identifying relevant studies in software engineering," Information and Software Technology, vol. 53, pp. 625-637, 2011. [18] P. Brereton, B. A. Kitchenham, D. Budgen, M. Turner, and M. Khalil, "Lessons from applying the systematic literature review process within the software engineering domain," The Journal of Systems and Software, pp. 571–583, 2007. [19] H. Zhang, M. A. Babar, and P. Tell, "Identifying relevant studies in software engineering," Information and Software Technology, vol. 53, pp. 625-637, 2011. [20] M. J. Power, K. C. Desouza, and C. Bonifazi, The Outsourcing Handbook How to implement a successful outsourcing process: First published in Great Britain and the United States in 2006 by Kogan Page Limited. [21] M. Ali-Babar, J. Verner, and P. Nguyen, "Establishing and maintaining trust in software outsourcing relationships: An empirical investigation," The Journal of Systems and Software, vol. 80, pp. 1438–1449, 2007. [22] S. U. Khan and M. Niazi, "Systematic Literature Review Protocol for Software Outsourcing Vendors Readiness Model (SOVRM), Technical Report: TR/08-01, ISSN: 1353-7776, School of Computing and Maths, Keele University, UK," 2008. [23] M. J. Gallivan and W. Oh, "Analyzing IT Outsourcing Relationships as Alliances among Multiple Clients and Vendors," presented at Proceedings of the 32nd Hawaii international Conference on System Sciences, Hawaii, USA, 1999. [24] V. Imsland, "The Role of Trust in Global Software Outsourcing Relationships," in Department of Informatics: UNIVERSITY OF OSLO, 30th July 2003. www.iosrjournals.org 31 | Page