A utilização de uma gestão de portfólio de projetos permite que as empresas possam se adaptar rapidamente frente as turbulências advindas do ambiente interno e externo e com isso, possam rearranjar os projetos para que estes estejam alinhados com estratégia da organização. Entretanto, o modelo tradicional de gerenciamento de portfólio possui procedimentos que não seguem necessariamente essa característica de agilidade e adaptação. Na maioria das vezes os procedimentos são pouco visíveis, extensos e poucas vezes são interativos ou divulgados por todos os níveis hierárquicos das organizações. Dessa maneira o propósito deste trabalho é a aplicação de práticas, métodos e ferramentas ágeis na gestão de portfólio de projetos. Para isto, foi realizada uma revisão sistemática da literatura, a análise crítica do modelo tradicional por 7 especialistas da área e desenvolvimento de um modelo com base na análise das respostas das entrevistas por três especialistas sendo 2 da área acadêmica e 1 profissional da área. Os principais resultados revelam, que a existe uma escassez de trabalhos referentes a utilização de ferramentas ágeis em gestão de portfólio de projetos e na percepção dos entrevistados, a aplicação de práticas, métodos e ferramentas ágeis atende o quesito de gestão visual, melhor interação entre as equipes de trabalho, democratização da informação relativa à tomada de decisão e ferramentas alinhadas com a proposição ágil. / The use of project portfolio management allows companies to adapt quickly to the turbulence arising from the internal and external environment and with that, can rearrange the projects so that they are aligned with the organization's strategy. However, the traditional portfolio management model has procedures that do not necessarily follow this characteristic of agility and adaptation. Most of the time the procedures are barely visible, extensive and are rarely interactive or disseminated by all hierarchical levels of organizations. In this way, the purpose of this work is the incorporation of agile practices, methods and tools in project portfolio management. For this, a systematic review of the literature, the critical analysis of the traditional model by 7 specialists of the area and the development of a model based on the analysis of the answers of the interviews by three specialists were carried out, being 2 of the academic area and 1 professional of the area. The main results show that there is a shortage of work related to the use of agile tools in project portfolio management and the perception of the interviewees, the incorporation of agile practices, methods and tools attends to the question of visual management, better interaction between work teams, democratization of decision-making information and tools aligned with the agile proposition.

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

Context: The problem this thesis address is concerned with experimental software engineering and is associated with validity of the studies with students as subjects. Often in software engineering experiments students are used because students are easily available and are willing to participate in experiment studies, professionals are rarely available to participate in research study and there are several benefits of using students as research subject.The validity of experiments studied with students are questioned because students are less experienced and skilled compared to professionals. Objectives: The goal of this research is to find evidence whether or not the research studies with students as subjects can be trusted to get valid results. Identify factors that influence the results of experiment studies with students. Identify the ways to improve the validity of experiment studies with students. Methods: In this systematic literature review a number of article sources are used, including Compendex, Inspec, IEEE Xplore, ACM Digital Library, and Springer Link. Experiment studies in software engineering are selected after reading titles and abstracts to decide whether the articles are relevant to the subject. Snowball sampling is done to identify several experiment studies that address same research problems. Results: It is found that graduate students serve as good proxies to study professional practices compared to undergraduate students, because there are significant differences between result/findings of studies with undergraduate students as subjects and studies with professionals as subjects. The following factors influencing the results of experiment studies are identified: Number of subjects, Task related knowledge, Motivation levels of subjects, Training provided, Task related experience and Incentives or grades given for participation in the experiment. This study also identifies some problems with the way of conducting and reporting experiments in software engineering. Addressing these problems could improve the validity of experiment studies with students. Conclusion: The results indicate that students can be used to study professional practices but they cannot be said true for all areas and problems of software engineering because the results of experiment studies with different type of subjects in different area and problems are varying. Which means that whether or not students could be used to study a professional practice depends upon the research problems being studied, type of students subjects chosen for the study, difference between students chosen and professionals to whom the results/findings will be generalized. We conclude that graduate students serve as good proxies to study professional practices compared to undergraduate students. The cumulative experience or overall industry or academic experience of subjects does not seem to be affecting the result/findings of experiment studies unless the overall experience includes task related experience. Even though the study identified above mentioned factors that influences the results/findings of experiment studies there still might be few factors which the study might have failed to identify due lack of data. We suggested improvements for reporting that could improve the comparability of studies. / Often in software engineering experiments students are used because students are easily available and are willing to participate in experiment studies, where as professionals are rarely available to participate in research study. This thesis investigates whether it is ok to use students as experiments subjects while studying professional practices. Thesis also investigates the factors which influences the results of experiment studies with students. The derived knowledge from the thesis can assists researchers improve the way of conducting and reporting software engineering experiments, It also aids in improving the comparability of experiment studies.

Context: Software engineering researchers are guided by research principles to conduct any type of research. Though, there are many guidelines to detail how a particular research method can be applied, there is always a necessity to continue and to improve the existing empirical research strategies. The context of this thesis is to address guidelines for conducting controlled experiments in Global Software Engineering (GSE). With this thesis, the state-of-the-art of conducting experiments in GSE research has been explored. Objectives: The goal of this thesis is to analyze the existing experiments in GSE research. Research problems addressed with GSE experiments and the state-of-the-art of overall GSE experiment design need to be analyzed. Appropriate guidelines should be drawn in order to provide strategies to future GSE researchers in mitigating or solving GSE specific experimentation challenges. Methods: A systematic literature review (SLR) is conducted to review all the GSE experiments that are found in the literature. The search process was done on 6 databases. A specific search and quality assessment criterion is used to select these GSE experiments. Furthermore, scientific interviews are conducted with GSE research experts to evaluate a set of guidelines (thesis author’s recommendations) that address the challenges when conducting GSE experiments. Thematic analysis has been performed to analyze the evaluation results and to further improve or implement any suggestions given by the interviewees. Conclusions: The results obtained from the SLR have provided a chance to understand the state-of-the-art and to analyze the challenges or problems when conducting controlled experiments in GSE. The challenges that are identified in GSE controlled experiments are found to be with experiment study-setting, involving subjects and addressing GSE relevant threats to validity in a GSE experiments. 9 guidelines are framed, with each guideline addressing a specific challenge. The final guidelines (that resulted after interviews) provide effective recommendations to GSE researchers when conducting controlled experiments. / +919441308167

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.

Context: Agile/lean development has been successful situations where small teams collaborate over long periods of time with project stakeholders. Unclear is how such teams plan and coordinate their work in such situations where inter-dependencies with other projects exist. In large organizations, scattered teams and complex team structure makes it difficult for every stakeholder to have a clear understanding of project information. These factors make it difficult for large‐scale organizations to adopt the agile/lean development paradigm. Objectives: The goal of conducting this study is to find the information visualization techniques that ease or resolve the challenges of agile development in large-scale organizations. The study reports the challenges of agile development and information visualization techniques in literature and reported by industrial experts. Additionally, proposed a guideline that how information visualization technique can be used to ease or resolve related challenge of agile development. Methods: For this particular study, two research methodologies are used; Systematic Literature Review (SLR) and Industrial Survey. Two SLRs are performed for finding 1) challenges of agile development and 2) information visualization techniques in agile development. Data sources like Engineering Village (Inspec/ Compendex), IEEE Explore digital library, ACM digital library, Science Direct, ISI-Web of knowledge; Scopus were used to select primary study. Industrial survey was conducted in order to obtain empirical evidence to our findings. In survey, mainly questions were related to challenges of agile development and information visualization techniques practiced by industrial experts. Results: 84 different challenges of agile development found in literature and by applying grounded theory we found 9 distinct categories of challenges. There were 55 challenges reported by industrial experts in survey which later grouped into 10 distinct challenges. 45 information visualization techniques found in literature and grouped into 21 distinct technologies. There were 47 different information visualization techniques reported by industrial experts. When we grouped these techniques there were 9 distinct technologies found by applying open, axial and selective coding of grounded theory Conclusions: Systematic Literature Review and Industrial Survey confirmed that information visualization techniques can be used to ease or resolve challenges of agile development. Along with other visualization techniques, Data Flow Diagrams, UML, Use Case Diagrams, Burn Down Charts, Scrum Story Board, Kanban Boards and Gantt Chart are highly reported techniques found through systematic literature review and later confirmed by industrial experts. On the other hand, through survey we found that industrial experts mainly rely on informal and customized information visualization techniques to visualize information.

Context: Bug fixing is the process of ensuring correct source code and is done by developer. Automated debugging and bug fixing solutions minimize human intervention and hence minimize the chance of producing new bugs in the corrected program. Scope and Objectives: In this study we performed a detailed systematic literature review. The scope of work is to identify all those solutions that correct software automatically or semi-automatically. Solutions for automatic correction of software do not need human intervention while semi-automatic solutions facilitate a developer in fixing a bug. We aim to gather all such solutions to fix bugs in design, i.e., code, UML design, algorithms and software architecture. Automated detection, isolation and localization of bug are not in our scope. Moreover, we are only concerned with software bugs and excluding hardware and networking domains. Methods: A detailed systematic literature review (SLR) has been performed. A number of bibliographic sources are searched, including Inspec, IEEE Xplore, ACM digital library, Scopus, Springer Link and Google Scholar. Inclusion/exclusion, study quality assessment, data extraction and synthesis have been performed in depth according to guidelines provided for performing SLR. Grounded theory is used to analyze literature data. To check agreement level between two researchers, Kappa analysis is used. Results: Through SLR we identified 46 techniques. These techniques are classified in automated/semi-automated debugging and bug fixing. Strengths and weaknesses of each of them are identified, along with which types of bugs each can fix and in which language they can be implement. In the end, classification is performed which generate a list of approaches, techniques, tools, frameworks, methods and systems. Along, this classification and categorization we separated bug fixing and debugging on the bases of search algorithms. Conclusion: In conclusion achieved results are all automated/semi-automated debugging and bug fixing solutions that are available in literature. The strengths/benefits and weaknesses/limitations of these solutions are identified. We also recognize type of bugs that can be fixed using these solutions. And those programming languages in which these solutions can be implemented are discovered as well. In the end a detail classification is performed. / alla automatiska / halvautomatiska felsökning och felrättning lösningar som är tillgängliga i litteraturen. De styrkor / fördelar och svagheter / begränsningar av dessa lösningar identifieras. Vi erkänner också typ av fel som kan fastställas med hjälp av dessa lösningar. Och de programmeringsspråk där dessa lösningar kan genomföras upptäcks också. Till slut en detalj klassificering utförs / +46 763 23 93 87, +46 70 966 09 51

Context: Modeling is an important activity, which is used, in different phases of software engineering. Without models and modeling, it is nearly impossible to design and develop software systems, which demands the need for modeling to be taught in software engineering. There exist a number of reported models, methods, tools and languages to teach modeling in software engineering, which suggests the need for a classification and an overview of the area. This research investigates the state of published research on teaching modeling in software engineering in order to provide a systematic overview and classification of these different ways of teaching modeling with an insight on their importance and relevance to this research area. Objectives: The overall goal of the research was achieved with fulfilling the following objectives: understanding how systematic mapping is conducted, developing a systematic mapping process that will properly provide data for investigating the published research, applying the process, and finally reflecting on the results of the mappings, analyzing the importance and evaluating relevance of the published research. Methods: Systematic literature review was used as a tool to understand and inspect how systematic mapping was carried out in the area of software engineering. Based on the results of systematic literature review, new guidelines were formulated to conduct systematic mapping. These guidelines were used to investigate the published research on teaching modeling in software engineering. The results obtained through the systematic mapping were evaluated based on Industrial relevance, Rigor and citation count to examine their importance and identify research gaps. Results: 131 articles were classified into five classes such as Languages, Course Design, Curriculum design, Diagrams, others using semi-manual classification scheme and classification facets such as the type of audience, type of contribution, type of research, type of publication, type of publication year, type of research method and type of study setting. After the evaluation of Industrial relevance, rigor & citation ranking on the obtained results of the classification, 8 processes, 4 tools, 3 methods, 2 measurement-metrics and 1 model were extracted to teach modeling in software engineering. Also, this classification when compared with an existing classification, which is based on interviews and discussions, showed that our classification provides a wider overview with a deeper insight of the different ways to teach modeling in software engineering. Conclusions: Results of this systematic mapping study indicate that there is an increase in the research activity on teaching modeling in software engineering, with Unified Modeling Language (UML) being the widely research area. Much research is emphasized on teaching modeling to students from academia which indicates a research gap in developing methods, models, tools and processes to teach modeling to students/practitioners from the industry. Also, considering the citation ranking, industrial relevance and rigor of the articles, areas such as course design and curriculum development are highly neglected, suggesting the need for more research focus. / Sammanhang : Modellering är en viktig verksamhet , som används i olika faser av programvaruteknik . Utan modeller och modellering , är det nästan omöjligt att utforma och utveckla mjukvarusystem , vilket kräver behovet av modellering för att undervisas i programvaruteknik . Det finns ett antal rapporterade modeller, metoder , verktyg och språk för att undervisa modellering i programvaruteknik , vilket tyder på att det behövs en klassificering och en överblick över området . Denna forskning undersöker tillståndet av publicerad forskning om undervisning modellering i programvaruteknik för att ge en systematisk överblick och klassificering av dessa olika sätt att undervisa modellering med en insikt om deras betydelse och relevans för detta forskningsområde . Mål : Det övergripande målet med forskningen uppnåddes med att uppfylla följande mål : att förstå hur systematisk kartläggning genomförs , att utveckla en systematisk kartläggning process som riktigt kommer att ge data för att undersöka publicerad forskning , tillämpning av processen , och slutligen reflektera över resultaten av de avbildningar, som analyserar betydelsen och utvärdera relevansen av den publicerade forskningen . Metoder : En systematisk litteraturstudie användes som ett verktyg för att förstå och kontrollera hur systematisk kartläggning genomfördes inom området programvaruteknik . Baserat på resultaten av en systematisk litteraturgenomgång har nya riktlinjer som formulerats för att bedriva systematisk kartläggning . Riktlinjerna användes för att undersöka den publicerade forskning om undervisning modellering i programvaruteknik . De resultat som erhållits genom systematisk kartläggning utvärderades baserat på industriell relevans , Rigor och stämningen räkning för att undersöka deras betydelse och identifiera kunskapsluckor . Resultat: 131 artiklar klassificerades i fem klasser , t.ex. språk , kurs Design , Curriculum design, diagram , andra med hjälp av semi - manuell klassificeringssystem och klassificerings fasetter såsom typ av publiken , typ av bidrag , typ av forskning , typ av publikation , typ av årtal , typ av forskningsmetod och typ av studieinställning. Efter utvärderingen av industriell relevans , noggrannhet och stämningen ranking på de erhållna resultaten av klassificeringen , 8 processer , 4 verktyg , 3 metoder , 2 mät - mått och 1 modell extraherades att lära modellering i programvaruteknik . Även denna klassificering i jämförelse med en befintlig klassificering , som bygger på intervjuer och diskussioner , visade att vår klassificering ger en bredare överblick med en djupare insikt om de olika sätten att lära modellering i programvaruteknik . Slutsatser : Resultaten av denna systematiska kartläggning visar att det finns en ökning av forskningsverksamheten på undervisning modellering i programvaruteknik , med Unified Modeling Language ( UML ) är den brett forskningsområde. Mycket forskning framhävs att lära modellering för studenter från den akademiska världen , som indikerar en lucka forskning för att utveckla metoder, modeller , verktyg och processer för att lära modellering för studenter / utövare från branschen . Dessutom , med tanke på stämningen ranking , industriell relevans och noggrannhet av artiklarna , områden som kursdesign och utveckling av läroplaner är mycket eftersatt , vilket tyder på att det behövs mer forskning fokus. / Flat # 503,Sri Krishna Residency, Mangapuram Colony,Vizag, Andhra Pradesh, India- 530017. +9989733724

This literature review seeks to identify the major security issues and their solutions in cloud computing security as well as identifying areas for future research. Utilising a modified version of the approach suggested by Okoli and Schabram (2010) 52 articles were considered for the review, of which 26 were included in the final product. Although many security issues and solutions were identified it has become apparent that much of the research being done only relates to the theoretical side. Thus this review shows that while plenty of issues have been identified future research should focus more on the practical implications of these security risks. / Denna litteraturundersökning identifierar de huvudsakliga säkerhetsbristerna och de lösningar som åtfinns inom litteraturen om datormolnsäkerhet. Undersökningen använder sig av en modifierad version av metoden för litteraturundersökningar som skrivits av Okoli och Schabram (2010). Efter en första litteratursökning identifierades 52 artiklar som relevanta för undersökningen, av dessa 52 användes 26 i slutprodukten. Trots att flera olika säkerhetsbrister och lösningar för dessa identifierades var det uppenbart att mycket av forskningen enbart har teoretiska svar på bristerna. Undersökningen visar således att även om många hot har upptäckts av forskare saknas det forskning av de praktiska konsekvenserna av dessa brister.