No description available.

In recent years, software tools used for Global Software Development (GSD) processes (e.g., continuous integration, version control and bug tracking) are increasingly being deployed in the cloud to serve multiple users. Multitenancy is an important architectural property in cloud computing in which a single instance of an application is used to serve multiple users. There are two key challenges of implementing multitenancy: (i) ensuring isolation either between multiple tenants accessing the service or components designed (or integrated) with the service; and (ii) resolving trade-offs between varying degrees of isolation between tenants or components. The aim of this thesis is to investigate how to architect the deployment of cloud-hosted service while guaranteeing the required degree of multitenancy isolation. Existing approaches for architecting the deployment of cloud-hosted services to serve multiple users have paid little attention to evaluating the effect of the varying degrees of multitenancy isolation on the required performance, resource consumption and access privilege of tenants (or components). Approaches for isolating tenants (or components) are usually implemented at lower layers of the cloud stack and often apply to the entire system and not to individual tenants (or components). This thesis adopts a multimethod research strategy to providing a set of novel approaches for addressing these problems. Firstly, a taxonomy of deployment patterns and a general process, CLIP (CLoud-based Identification process for deployment Patterns) was developed for guiding architects in selecting applicable cloud deployment patterns (together with the supporting technologies) using the taxonomy for deploying services to the cloud. Secondly, an approach named COMITRE (COmponent-based approach to Multitenancy Isolation Through request RE-routing) was developed together with supporting algorithms and then applied to three case studies to empirically evaluate the varying degrees of isolation between tenants enabled by multitenancy patterns for three different cloud-hosted GSD processes, namely-continuous integration, version control, and bug tracking. After that, a synthesis of findings from the three case studies was carried out to provide an explanatory framework and new insights about varying degrees of multitenancy isolation. Thirdly, a model-based decision support system together with four variants of a metaheuristic solution was developed for solving the model to provide an optimal solution for deploying components of a cloud-hosted application with guarantees for multitenancy isolation. By creating and applying the taxonomy, it was learnt that most deployment patterns are related and can be implemented by combining with others, for example, in hybrid deployment scenarios to integrate data residing in multiple clouds. It has been argued that the shared component is better for reducing resource consumption while the dedicated component is better in avoiding performance interference. However, as the experimental results show, there are certain GSD processes where that might not necessarily be so, for example, in version control, where additional copies of the files are created in the repository, thus consuming more disk space. Over time, performance begins to degrade as more time is spent searching across many files on the disk. Extensive performance evaluation of the model-based decision support system showed that the optimal solutions obtained had low variability and percent deviation, and were produced with low computational effort when compared to a given target solution.

Context: Global software development is the emerging trend in today’s world as it provides the software companies with certain advantages like access to skill and cheap labor, low development cost etc. There are also many challenges and risks involved in globally distributed software project as compare to co-located projects like communication, coordination and control etc. due to geographical separation. There is also a recent interest in applying agile methods in offshore projects in order to minimize certain offshore challenges. Agile methods in collocated environment demands high communication, coordination and collaboration between the team members. However implementing agile methods in distributed environment is beneficial and challenging too, because of inherited GSD challenges. Therefore, it is necessary to carefully understand the benefits and challenges of applying agile methods in distributed project before actually initiating the development. Objectives: This research study aims to look at current empirical evidence regarding benefits and challenges of applying agile methods in offshore projects, in order to understand it properly. Furthermore, we have examined that which of the benefits and challenges reported in literature can be seen in practice. This helped us in finding out the similarities and differences between the benefits and challenges that are reported in literature and in practice. Methods: To fulfill our aims and objectives we have first conducted the detailed systematic review analysis of the empirical studies from year 2000-2010. The systematic review approach helped us to collect and summarize the empirical data available regarding the benefits and challenges of applying agile methods in offshore projects. The research studies were identified from the most authentic databases that are scientifically and technically peer reviewed such as Inspec and Compendex, IEEE Xplore, ACM digital library, Springer Link, Science Direct, Google Scholar, Scopus, ISI Web of Knowledge and Willey Inter Science Journal Finder. Furthermore, industrial survey was conducted in order to identify whether the benefits and challenges enlisted in literature can be confirmed by practitioners. This helped us in determining the similarities and differences between benefits and challenges that are reported in empirical literature and industrial survey. Results: From systematic review results, we have found the list of benefits and challenges of most applied agile practices such as daily scrum meetings, sprint planning meetings, sprint review meetings, retrospective meetings, pair programming, short release and on-site customer. The most common benefits related to above identified agile practices are early problem identification, project visibility, increase communication, coordination and collaboration, trust, clarification of work and requirements, early client feedback and customer satisfaction. Similarly the most common challenges associated with above identified agile practices are lack of linguistic skills, culture differences and temporal differences. From survey result, it was found that the majority of benefits and challenges identified through literature review are prevalent in software industries to some extent. We were able to identify the benefits and challenges of agile practices such as daily scrum, sprint planning meetings, sprint review, retrospective meetings and short release. The most common benefits of above identified agile practices highlighted by survey participants are project visibility, early problem identification, increase coordination, opportunity for knowledge sharing and transferring, immediate feedback from client, and opportunity for understanding the task properly. Similarly the most common challenges identified by survey participants are language problems, temporal difference and difficult to explain and understand problems or issues over communication technologies. However, there are certain challenges like trust and culture issues, which have received most attention in the empirical literature, but are not identified by majority of industry respondents. Conclusions: From the information attained so far regarding the benefits and challenges of agile methods in offshore projects, we observed that there is an emerging trend of using agile methods in offshore projects and practitioners actually found it beneficial. The benefits of agile practices does not achieve straightaway there are certain challenging factors of GSD too, which can restrict the implementation or make the methodology not useful such as communication, coordination and collaboration. These challenges are usually occurred due to geographical separation, lack of trust and linguistic skills, culture difference etc. The presented work add contribution in a sense as to the best of our knowledge no systematic review effort has been done in this area with specifically focuses on highlighting the benefits and challenges. From survey results we found that majority of benefits and challenges highlighted by survey participants are to some extent same with what we have already studied in literature. However there are certain important challenges which have received most attention in empirical literature but were less identified by the survey participants like trust issue and culture difference. The benefits and challenges identified through industrial survey do not add much information into our attention. This does not mean that all possible benefits and challenges of applying agile methods in offshore project have been explored. The responses which were received from industry practitioners were quite few to make any kind of arguments. There is a probability that we missed the important benefits and challenges related to particular agile practices during our industrial survey. Therefore we conclude that a much thorough and inclusive answers should be required to identify the benefits and challenges of applying agile methods in offshore projects.

Context. Global Software Development (GSD) or Global Software Engineering (GSE) is defined as the plan of action in which the software development is performed under various boundaries, such as temporal, political, organizational and cultural [1,2] . The projects developed in globally distributed environment are containing more risks than projects developed in collocated environment because of different challenges such as temporal, geographical and socio-cultural distances [67]. In this thesis communication risks have been discussed along with their causes and effects that hinder the effectiveness of GSD projects. Moreover mitigation practices to resolve communication risks and their negative impacts are also discussed. Objectives. The study describes the identification of communication risks, their causes, effects and the practices to mitigate the risks from both literature and industrial perspectives. Some recommendations has also been discussed on the basis of these resulted communication risks and their mitigation practices. Methods. Detailed systematic literature review in order to collect the data from relevant empirical studies with respect to our scope has been conducted in the first phase. Studies were selected from various Electronic Data Sources (EDS) such as IEEE Xplore (IEEE), ACM Digital Library (ACM), Inspec (IS), Compendex (CD), ISI Web of Science (WoS), Cite Seer (CS), Google Scholar (GS), Science Direct (SD), Springer Link (SL), Wiley Inter Science (WIS), and Business Source Premier (BSP). In second phase 22 industrial interviews were conducted from 13 different multinational organizations. In third phase data analysis has been made based on the analysis of ground theory. On the basis of the codes of grounded theory, comparative analysis has been performed between literature and industrial settings. At the end of the thesis some recommendations has been provided in order to resolve communication risks in GSD. Results. As a result of systematic literature review 44 risks, 44 causes, 38 effects and 63 practices have been identified in GSD with respect to communication. 27 risks, 22 causes, 19 effects and 39 mitigation practices were identified from the industrial interviews. These risks, causes, effects and practices are not only described in this thesis but also mapped in relation to each other. At the end in comparative analysis the combined risks, causes, effects and practices were identified in tabular form. In total 47 risks, 45 causes, 39 effects and 65 mitigation practices were identified through this work. Conclusions. Communication plays a fundamental role in achieving the best practices in Global Software Engineering. This study points out the salient risks and limitations that hamper the process of smooth communication in geographically dispersed teams. The causes and effects of the mentioned risks are discussed in detail and a set of recommendations is provided to cope with those risks and to minimize their effect. The resultant set of recommendations is based on the best suitable practices which shall be followed by globally distributed organizations to achieve a fully communicated environment just like an in-house development setting. / 0046760622684

Global Software Development (GSD) is an emerging trend in today's software world in which teams are geographically dispersed, either in close proximity or globally. GSD provides certain advantages to development companies like low development cost, access to cheap and skilled labour etc. This type of development is noted as a more risky and challenging as compared to projects developed with teams under same roof. Inherently the nature of GSD projects are cooperative in which many software developers work on a common project, share information and coordinate activities. Coordination is a fundamental part of software development. GSD comprises different types of development systems i.e. insourcing, outsourcing, nearshoring, or farshoring, whatever the types of development systems selected by a company there exist the challenges to coordination. Therefore the knowledge of potential challenges, associated threats to coordination and practices to mitigate them plays a vital role for running a successful global project.

Background: The rapid improvement of technological infrastructure over the past three decades have led to increased connectivity and communication possibilities. This has allowed firms to develop sophisticated firm-specific governance structures with the use of different sourcing strategies. The main objectives have been to cut costs and gain competitive advantages by outsourcing activities offshore to developing countries or third-party vendors. The decision to outsource has its roots in the classical transaction cost theory and resource-based view. Some outsourcing partnerships have resulted in failures while others in success stories. The stories are evident in the software industry as the industry is highly susceptible to sourcing strategies, hence outsourcing is often used in global software development (GSD) projects. Firms engage in GSD with the ultimate goal of producing products faster, at a low-cost, and of high quality. In spite of this, GSD projects face huge challenges in terms of geographical-, temporal-, and cultural distances while the added complexity and issues associated with different sourcing strategies amplifies these challenges. The use of different sourcing strategies in GSD projects has not received as much attention as the debate about whether co-located or distributed teams perform better. Objective: The objective of this thesis is to explore how outsourcing, insourcing, and the combination of both in a co-located and distributed development setting relates to the software development project performance measured in terms of quality and productivity. The aim is to enrich and add to the scarce literature of global software development project performance in relation to sourcing strategies and when these are combined in projects. Method: In this thesis, we employed a case study at a software firm which engages in large-scale global software development projects. A total of 64 projects were selected for the study and data was collected primarily from archival documents where we made use of management documents and code databases. The data analysis was conducted using statistical tests in SPSS to investigate relationships and differences in quality and productivity for the four strategies. Results: The results revealed a statistically significant difference in quality among the sourcing strategies. Insourcing projects are associated with the highest quality followed by outsourcing projects and co-located mixed sourcing projects. Distributed mixed sourcing projects are generating the lowest quality. Although not statistically significant, distributed mixed sourcing projects are the most productive strategy followed by outsourcing projects, insourcing projects and lastly co-located mixed sourcing projects Conclusions: The recent trends in GSD which indicate that many companies turn back to insourcing after outsourcing is justified in our results as insourcing projects displays the highest quality. While outsourcing projects have been associated with poor quality and productivity, our findings suggest they are very competitive in terms of both. The mix of internal employees and third-party consultants in a co-located and distributed setting is associated with lower quality while poor productivity is only attributed to the co-located case. / Bakgrund: Teknikens framfart över de tre senaste decenierna har lett till ökade anslutnings- och kommunikationsmöjligheter. Detta har möjliggjort för företag att utveckla sofistikerade företagsspecifika stryelsestrukturer med använding av olika sourcing strategier. Det huvudsakliga målet med att outsourca olika aktiviteter till utvecklingsländer eller tredjepartsleverantörer har varit att minska kostnader och att erhålla konkrurrensfördelar. Belsutet om att outsourca aktiviteter i ett företag är resursbaserat och grundar sig i den klassiska transaktionskostnadsteorin och resursbaserade teorin (resource-based view). Somliga partnerskap har resulterat i misslyckanden, andra i framgångssagor. Många av dessa har åstadkommits inom mjukvaruindustrin då industrin är mottaglig för olika sourcing strategier, bland annat används outsourcing mycket i globala mjukvaruutvecklingsprojekt. IT-företagen bedriver globala mjukvaruprojekt med de slutgiltliga målet att producera snabbare till ett lägre pris och en högre produktkvalitet. Trots detta uppstår ofta utmaningar när de gäller geografiska, tidsmässiga eller kulturella avstånd där nyttjandet av sourcing strategier adderar ytterligare ett lager av komplexitet. Majoriteten av uppmärksamhet har riktats mot hur samlokaliserade eller distrubuerade projekt presterar medan nyttjandet av sourcingstrategier i globala mjukvaruutvecklingsprojekt har fått mindre uppmärksamhet.      Syfte: Syftet är att undersöka hur outsourcing, insourcing och en kombination av de två i en samlokaliserad eller distrubuerad miljö relaterar till mjukvaruutvecklingsprojkets prestanda i termer om produktivitet och kvalitet. Målet är att berika och addera kunskap till en knapp litteratur om prestanda för globala mjukvaruutvecklingsprojekt med avseende på sourcing strategier när dessa tillämpas i en kombination. Metod. En fallstudie har bedrivits på ett mjukvaruutvecklingsföretag som arbetar med globala storskaliga mjukvaruutvecklingsprojekt. Totalt har 64 projekts blivit utvalda, analyserade och grupperade i fyra olika sourcing strategier. Sekundärdata samlades primärt in från interna företagsarkiv såsom företagets interna databaser och projektledarverktyg. Intervjuer har också genomförts med två projektledare för att få en mer djupgående förståelse av projekten och för att välja ut projekten baserat på våra krav. Dataanalysen genomfördes via statistiska tester i SPSS. Resultat: Resultatet visade en signifikant skilland i kvalitet mellan sourcing strategierna. Insourcingprojekt visade sig bidra med högst kvalitet följt av outsourcing och mixad samlokaliserad sourcing projekt. Signifikat lägst kvalitet hade mixad distrubuerad sourcing. Trots icke-signifikanta resultat, visade det sig att produktiviteten var som högst i mixad distribuerad sourcing projekt följt av outsourcing, mixad samlokaliserade sourcing och insourcing projekt. Slutsats: De senaste trenderna inom global mjukvaruutveckling indikerar på att många företag återvänder till insourcing efter outsourcing är motiverade i vårt resultat eftersom insourcing projekt resulterar i högre kvalitet. Trots att outsourcingprojekt har förknippats med låg kvalitet och produktivitet tyder våra resultat på att de är mycket konkurrenskraftiga. Slutligen är mixen av internanställda och tredje part konsulter i en samlokaliserad och distrubuerad miljö förknippad med en sämre kvalitet, och i de samlokaliserade fallet även sämre produktivitet.

Context and Background: Global Software Development involves teams located in different geographical locations, time zones, and cultural contexts working together to accomplish a shared goal or complete a software project. These projects, which are conducted by teams in different locations, have been found to be more risky and challenging than those with teams in the same location. Therefore, it is important to have knowledge of the potential challenges of task allocation in global software development and strategies for addressing them to manage a GSD project successfully. Objective: This thesis aims to identify and tabulate all the Task allocation challenges in Global Software Development and synthesize the mitigation strategies for the challenges identified in task allocation in GSD. To evaluate the challenges that influence the task allocation process in GSD and perform an assessment to find the mitigation strategies for these challenges. Research Method: This is a systematic literature review of studies on empirical research on GSD, covering publications from 1999 to 2022. The focus of this research is specifically on challenges associated with task allocation in GSD projects. A survey was conducted to validate the identified challenges and gather suggestive mitigation strategies. This research aimed to identify task allocation challenges in GSD and suggest mitigation strategies in GSD projects. Results: This research has identified a total of 20 challenges related to task allocation in Global software development based on a review of publications from 1999 to 2022. Additionally, the mitigation strategies for the 20 identified challenges were found in a survey conducted as part of the research. The challenges and mitigation strategies are discussed in the paper.

As globalisation is now a reality for most large organizations, and the competition for most businesses moving faster and becoming tougher, there is a need for engineering projects to deliver results faster in a more complex environment than ever, but also for companies to collaborate to utilize a wider array of competencies and to reach new markets with their products. This case study analyses which difficulties arise in interorganizational requirements engineering, and what organizations can do to alleviate the effects of those difficulties, as well as suggest which actions are most effective to focus on. The conclusion of this study is that the difficulties can be divided into three categories, namely interpersonal, structural and processual. Each category concerns a different set of people and require different actions for increased effectiveness. For the interpersonal category, prioritized efforts should be to establish a shared vocabulary and use techniques to build shared contextual understanding. For structural difficulties, evaluating management and control structures and the implementation of the project’s strategy should be prioritized. In the processual category, codifying existing processes to enable improvements, defining information artefacts and aligning information flows should be of high priority. / Globaliseringens effekter är idag en verklighet för de flesta stora organisationer, och konkurrensen för företag blir hårdare och förändrar sig allt snabbare. Därför blir det allt viktigare för utvecklingsprojekt att anpassa sig till en allt mer komplex miljö och leverera resultat snabbare än tidigare, men också att samarbeta mer med andra företag för att såväl utnyttja bredare kompetens som att nå nya marknader. Den här studien undersöker utmaningarna i interorganisatoriskt kravställningsarbete, vad företag kan göra för att möta de utmaningarna, såväl som att föreslå vilka handlingar som ger mest effekt för ett bättre kravställningsarbete. Slutsatsen av studien är att utmaningarna kan delas in i tre kategorier, nämligen personorienterade, strukturella och processorienterade. Varje kategori rör en viss mängd deltagare i projektet och kräver olika handlingar för ökad effektivitet. För att minska utmaningar i den personorienterade kategorin bör ett projekt prioritera att använda tekniker för att skapa ett gemensamt språkbruk och att använda tekniker för att bygga upp gemensam kontextuell förståelse. För strukturella utmaningar bör det prioriteras att utvärdera styrnings- och kontrollstrukturer, samt hur projektets strategi har implementerats och förankrats bland deltagarna. I den processorienterade kategorin bör det prioriteras att kodifiera existerande processer för att möjliggöra förbättringsarbete, definiera informationsartefakter och att försäkra sig om att informationsflöden är i linje med varandra mellan företagen, så att rätt information möts vid rätt tillfällen.

As globalisation is now a reality for most large organizations, and the competition for most businesses moving faster and becoming tougher, there is a need for engineering projects to deliver results faster in a more complex environment than ever, but also for companies to collaborate to utilize a wider array of competencies and to reach new markets with their products. This case study analyses which difficulties arise in interorganizational requirements engineering, and what organizations can do to alleviate the effects of those difficulties, as well as suggest which actions are most effective to focus on. The conclusion of this study is that the difficulties can be divided into three categories, namely interpersonal, structural and processual. Each category concerns a different set of people and require different actions for increased effectiveness. For the interpersonal category, prioritized efforts should be to establish a shared vocabulary and use techniques to build shared contextual understanding. For structural difficulties, evaluating management and control structures and the implementation of the project’s strategy should be prioritized. In the processual category, codifying existing processes to enable improvements, defining information artefacts and aligning information flows should be of high priority / Globaliseringens effekter är idag en verklighet för de flesta stora organisationer, och konkurrensen för företag blir hårdare och förändrar sig allt snabbare. Därför blir det allt viktigare för utvecklingsprojekt att anpassa sig till en allt mer komplex miljö och leverera resultat snabbare än tidigare, men också att samarbeta mer med andra företag för att såväl utnyttja bredare kompetens som att nå nya marknader. Den här studien undersöker utmaningarna i interorganisatoriskt kravställningsarbete, vad företag kan göra för att möta de utmaningarna, såväl som att föreslå vilka handlingar som ger mest effekt för ett bättre kravställningsarbete. Slutsatsen av studien är att utmaningarna kan delas in i tre kategorier, nämligen personorienterade, strukturella och processorienterade. Varje kategori rör en viss mängd deltagare i projektet och kräver olika handlingar för ökad effektivitet. För att minska utmaningar i den personorienterade kategorin bör ett projekt prioritera att använda tekniker för att skapa ett gemensamt språkbruk och att använda tekniker för att bygga upp gemensam kontextuell förståelse. För strukturella utmaningar bör det prioriteras att utvärdera styrnings- och kontrollstrukturer, samt hur projektets strategi har implementerats och förankrats bland deltagarna. I den processorienterade kategorin bör det prioriteras att kodifiera existerande processer för att möjliggöra förbättringsarbete, definiera informationsartefakter och att försäkra sig om att informationsflöden är i linje med varandra mellan företagen, så att rätt information möts vid rätt tillfällen.

Submitted by CARLA MARIA GOULART DE MORAES (carlagm) on 2015-04-06T17:18:33Z No. of bitstreams: 1 VilsonGartnerComputacao.pdf: 9068377 bytes, checksum: 6ace07d8901f11d83ef8a8c13f4f62c7 (MD5) / Made available in DSpace on 2015-04-06T17:18:33Z (GMT). No. of bitstreams: 1 VilsonGartnerComputacao.pdf: 9068377 bytes, checksum: 6ace07d8901f11d83ef8a8c13f4f62c7 (MD5) Previous issue date: 2011 / CAPES - Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / O Desenvolvimento Distribuído de Software (DDS) é um modelo de desenvolvimento que vem se intensificando nos últimos anos. Também conhecido como Desenvolvimento Global de Software (DGS), esse modelo de desenvolvimento é realizado por equipes em diferentes localizações geográficas. Entre os fatores que contribuem para esse aumento, está a necessidade de negócio das corporações, que buscam redução de custos, recursos qualificados e necessidade de uma presença global. Em outros casos, se deve ao surgimento de novos movimentos de desenvolvimento de software, como a comunidade de software livre, um exemplo bem sucedido de DDS. Apesar da necessidade ou mesmo da conveniência de desenvolver o software de forma distribuída, é extremamente difícil fazê-lo com sucesso. A separação física traz uma série de problemas e desafios interessantes que recém estão começando a ser compreendidas: questões estratégicas, questões culturais, comunicação inadequada, gestão do conhecimento, alocação de tarefas, confiança, questões técnicas, entre outros. Desde que surgiu, o DDS mudou grande parte da tradição do desenvolvimento de software e, para manter o seu mercado, as organizações não podem depender das mesmas competências e tecnologias de engenharia de software utilizadas no desenvolvimento interno. Nesse sentido, o presente trabalho tem por objetivo auxiliar na redução dos problemas e dificuldades trazidos por esse modelo de desenvolvimento, através da implementação de um ambiente de desenvolvimento cujas ferramentas foram definidas com base em estudos e trabalhos relacionados ao tema. / The Distributed Software Development (DSD) is a development model that has been intensified in recent years. Also known as Global Software Development (GSD), this development model is done by teams in different geographical locations. Among the factors that have contributed to this increase, there is the corporations business need of seeking ways to reduce costs, seeking skilled resources and having a global presence. In other cases, it is due to the emergence of new movements in software development, such as the free software community, a successful example of DSD. Despite the need or even desirability of developing software in a distributed way, it is extremely difficult to do this successfully. Physical separation has a number of interesting problems and challenges that are just beginning to be understood: strategic issues, cultural issues, inadequate communication, knowledge management, task allocation, trust, technical issues, among others. DSD has changed much of the tradition of software development since it appeared. Organizations cannot rely on the same skills and software engineering technologies used internally to maintain this new market. In this way, this work aims to help to reduce the problems and difficulties brought by this type of development, through the implementation of a software development environment whose tools were defined based on studies related to the topic.