Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-08-17T12:14:52Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação_AlexNery_V18 (VFinal_Biblioteca).pdf: 3946748 bytes, checksum: 139ad5265a5a9bfe6cb97a591113354a (MD5) / Made available in DSpace on 2016-08-17T12:14:54Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação_AlexNery_V18 (VFinal_Biblioteca).pdf: 3946748 bytes, checksum: 139ad5265a5a9bfe6cb97a591113354a (MD5) Previous issue date: 2015-02-27 / FACEPE / Contexto – Tem-se observado que o interesse em conduzir estudos empíricos vem aumentando na comunidade de Engenharia de Software, permitindo melhorar a qualidade das pesquisas e acelerar a adoção de novas tecnologias no mercado de software. Para fomentar pesquisas empíricas nesse contexto, é essencial entender os ambientes, diretrizes, processos, ferramentas e outros recursos disponíveis para conduzir tais estudos. Objetivo – Esta pesquisa tem o objetivo de identificar mecanismos de suporte (metodologias, framework, ferramentas, guias, processos, etc.) utilizados para planejar e conduzir estudos empíricos na comunidade de Engenharia de Software Empírica. Além disso, espera-se mapear outras evidências importantes na área, como os métodos empíricos mais utilizados e a evolução, ao longo dos anos, do uso de estratégias e mecanismos de pesquisa empírica. Método – Foi adotado o Estudo de Mapeamento Sistemático, conduzido de acordo com guias e diretrizes de Engenharia de Software Baseada em Evidências. Resultado – Foram identificados 375 mecanismos. Este trabalho fornece um catálogo com informações de todos os mecanismos e em quais estratégias empíricas são aplicados. Serão abordados os mecanismos mais utilizados para guiar os principais métodos empíricos. Este trabalho também discute outras informações relevantes da comunidade de Engenharia de Software Empírica. Observou-se que a maioria dos mecanismos utilizados como referência para guiar estudos empíricos é adotado de outras áreas científicas. Além disso, muitos estudos não aplicam estratégias empíricas e / ou não citam referências para apoiar sua pesquisa. Experimento e estudo de caso são os métodos empíricos mais aplicados. Conclusão – Esta pesquisa evidenciou que a realização de estudos empíricos na Engenharia de Software tem aumentado ao longo dos anos. No entanto, ainda há lacunas a serem preenchidas, como o desenvolvimento de novos ambientes e recursos para auxiliar atividades específicas nessa área. Portanto, um catálogo de mecanismos de suporte, onde e como foram aplicados, é um trunfo importante para a comunidade de Engenharia de Software. Tal recurso pode promover a realização de estudos empíricos, no sentido de auxiliar a escolha sobre quais estratégias e guias usar em uma pesquisa. Além disso, foram identificadas novas perspectivas e lacunas que podem orientar a definição de outras pesquisas voltadas para a melhoria e disseminação de estudos empíricos na área. / Context – It is possible to observe that empirical studies are gaining recognition in the Software Engineering research community, allowing improve quality of researches and accelerate the adoption of new technologies in the software market. In order to foster empirical research in this context, it is essential understand the environments, guidelines, process, tools, and other mechanisms available to conduct such studies. Objective – This research aims to identify support mechanisms (methodology, framework, tool, guidelines, process, etc.) used to plan and to conduct empirical studies in the Empirical Software Engineering community. In addition, it is expected to map other evidence of this area, as the most widely used empirical methods and the evolution of the use of empirical strategies and mechanisms along the years. Method – The method adopted was the Systematic Mapping Study conducted according to guidelines of Evidence-Based Software Engineering. Result - A total of 375 mechanisms were identified. This work provide a catalog with information of all the identified mechanisms and the empirical strategies in which they were used to support. And also describes the most used support mechanisms to guide the main types of empirical strategies in Software Engineering. This study also discusses relevant findings of the Empirical Software Engineering community. It was observed that the most mechanisms used as a reference to guide empirical studies are not specific to this area. Besides, many studies did not apply empirical strategies and/or did not cite any resource to support their research. Experiment and case study are the empirical strategies most applied. Conclusion – This research showed that the performance of empirical studies in Software Engineering has increased over the years. However, there are still gaps to be filled, as the development of support mechanisms to specific activities in this area. Therefore, the list of support mechanisms, where and how they were applied is an important asset to the Software Engineering community. Such asset can foster empirical studies aiding the choice regarding which strategies and mechanisms to use in a research, as well as pointing out examples where they were used, mainly to newcomers researchers. Also, were identified new perspectives and gaps that foster other research for the improvement and dissemination of empirical research in this area.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-08-17T12:23:47Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação_AlexNery_V18 (VFinal_Biblioteca).pdf: 3946748 bytes, checksum: 139ad5265a5a9bfe6cb97a591113354a (MD5) / Made available in DSpace on 2016-08-17T12:23:47Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação_AlexNery_V18 (VFinal_Biblioteca).pdf: 3946748 bytes, checksum: 139ad5265a5a9bfe6cb97a591113354a (MD5) Previous issue date: 2015-02-27 / FACEPE / Contexto – Tem-se observado que o interesse em conduzir estudos empíricos vem aumentando na comunidade de Engenharia de Software, permitindo melhorar a qualidade das pesquisas e acelerar a adoção de novas tecnologias no mercado de software. Para fomentar pesquisas empíricas nesse contexto, é essencial entender os ambientes, diretrizes, processos, ferramentas e outros recursos disponíveis para conduzir tais estudos. Objetivo – Esta pesquisa tem o objetivo de identificar mecanismos de suporte (metodologias, framework, ferramentas, guias, processos, etc.) utilizados para planejar e conduzir estudos empíricos na comunidade de Engenharia de Software Empírica. Além disso, espera-se mapear outras evidências importantes na área, como os métodos empíricos mais utilizados e a evolução, ao longo dos anos, do uso de estratégias e mecanismos de pesquisa empírica. Método – Foi adotado o Estudo de Mapeamento Sistemático, conduzido de acordo com guias e diretrizes de Engenharia de Software Baseada em Evidências. Resultado – Foram identificados 375 mecanismos. Este trabalho fornece um catálogo com informações de todos os mecanismos e em quais estratégias empíricas são aplicados. Serão abordados os mecanismos mais utilizados para guiar os principais métodos empíricos. Este trabalho também discute outras informações relevantes da comunidade de Engenharia de Software Empírica. Observou-se que a maioria dos mecanismos utilizados como referência para guiar estudos empíricos é adotado de outras áreas científicas. Além disso, muitos estudos não aplicam estratégias empíricas e / ou não citam referências para apoiar sua pesquisa. Experimento e estudo de caso são os métodos empíricos mais aplicados. Conclusão – Esta pesquisa evidenciou que a realização de estudos empíricos na Engenharia de Software tem aumentado ao longo dos anos. No entanto, ainda há lacunas a serem preenchidas, como o desenvolvimento de novos ambientes e recursos para auxiliar atividades específicas nessa área. Portanto, um catálogo de mecanismos de suporte, onde e como foram aplicados, é um trunfo importante para a comunidade de Engenharia de Software. Tal recurso pode promover a realização de estudos empíricos, no sentido de auxiliar a escolha sobre quais estratégias e guias usar em uma pesquisa. Além disso, foram identificadas novas perspectivas e lacunas que podem orientar a definição de outras pesquisas voltadas para a melhoria e disseminação de estudos empíricos na área. / Context – It is possible to observe that empirical studies are gaining recognition in the Software Engineering research community, allowing improve quality of researches and accelerate the adoption of new technologies in the software market. In order to foster empirical research in this context, it is essential understand the environments, guidelines, process, tools, and other mechanisms available to conduct such studies. Objective – This research aims to identify support mechanisms (methodology, framework, tool, guidelines, process, etc.) used to plan and to conduct empirical studies in the Empirical Software Engineering community. In addition, it is expected to map other evidence of this area, as the most widely used empirical methods and the evolution of the use of empirical strategies and mechanisms along the years. Method – The method adopted was the Systematic Mapping Study conducted according to guidelines of Evidence-Based Software Engineering. Result - A total of 375 mechanisms were identified. This work provide a catalog with information of all the identified mechanisms and the empirical strategies in which they were used to support. And also describes the most used support mechanisms to guide the main types of empirical strategies in Software Engineering. This study also discusses relevant findings of the Empirical Software Engineering community. It was observed that the most mechanisms used as a reference to guide empirical studies are not specific to this area. Besides, many studies did not apply empirical strategies and/or did not cite any resource to support their research. Experiment and case study are the empirical strategies most applied. Conclusion – This research showed that the performance of empirical studies in Software Engineering has increased over the years. However, there are still gaps to be filled, as the development of support mechanisms to specific activities in this area. Therefore, the list of support mechanisms, where and how they were applied is an important asset to the Software Engineering community. Such asset can foster empirical studies aiding the choice regarding which strategies and mechanisms to use in a research, as well as pointing out examples where they were used, mainly to newcomers researchers. Also, were identified new perspectives and gaps that foster other research for the improvement and dissemination of empirical research in this area.

Submitted by Natalia de Souza Gonçalves (natalia.goncalves@ufpe.br) on 2016-09-28T12:40:17Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertacao - Larissa Falcao - Final - Correcoes Biblioteca - Entrega.pdf: 1172723 bytes, checksum: b0a57a917a5abab25c66870d353d906f (MD5) / Made available in DSpace on 2016-09-28T12:40:17Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertacao - Larissa Falcao - Final - Correcoes Biblioteca - Entrega.pdf: 1172723 bytes, checksum: b0a57a917a5abab25c66870d353d906f (MD5) Previous issue date: 2016-02-18 / CNPq / Software Engineering professionals need to have information about new support mechanisms to decide, not at random, what option is best adapting it needs. One way of obtaining this information is through empirical studies that make the mechanisms used to support the design and development of software, be evaluated in practice. Thus, scientific research through experiments and empirical studies are fundamental during the evaluation of any new technology to software development. In this context, researchers perform experiments to check their proposals under controlled conditions. Therefore, experiments are an important category of empirical studies and are the classical approach for identifying cause-effect relationships. The goal of this dissertation is qualitatively and quantitatively characterizes and analyze human-centric experiments in software engineering, published in three journals andthree conferences proceedings from 2003 to 2013. To reach this objective was performed a systematic mapping study that includes all full papers published at EASE, ESEM, ICSE, ESEJ, JSS, TSE. Based on manual searches in those important conferences and journals in Software Engineering, were analyzed 3671 papers. 244 primary studies were identified as relevant, reporting experiments. In these experiments, we obtained qualitative and quantified data about authors and institutions, subjects, tasks performed, environment, replication and threats to validity. From the analysis performed, this work conclude that despite guidelines exist now, there is a large gap in the report of the experiments. The main contribution of this work is to provide the reporting status of human-centric software engineering experiments and how this field has matured. This work also proposes a list of information that an experiment report expected to have. / Profissionais de engenharia de software precisam ter informações sobre os novos mecanismos de apoio, a fim de decidir sem ser ao acaso, qual é a melhor opção que se adapta ao que se precisa. Uma maneira de obter essas informações é através de estudos empíricos, que permitem que os mecanismos utilizados para apoiar a concepção e desenvolvimento de software sejam avaliados na prática. Assim, a pesquisa científica através de experimentos e estudos empíricos são de fundamental importância na avaliação de qualquer nova tecnologia para desenvolvimento de software. Pesquisadores realizam experimentos para verificar as suas propostas sob condições controladas. Portanto, os experimentos são uma categoria importante de estudos empíricos e são a abordagem clássica para identificar relações de causaefeito. O objetivo deste trabalho é caracterizar qualitativa e quantitativamente, e analisar experimentos centrados em humanos em engenharia de software, publicados em três jornais e três conferências de 2003 a 2013. Para atingir este objetivo foi realizado um estudo de mapeamento sistemático que inclui todos os artigos completos publicados no EASE, ESEM, ICSE, ESEJ, JSS, TSE. Com base em pesquisas manuais nessas importantes conferências e periódicos em Engenharia de Software, foram analisados 3671 artigos. 244 estudos primários foram identificados como relevantes, relatando experimentos. Nesses experimentos foram obtidos dados qualitativos e quantificados sobre autores e instituições, participantes, tarefas realizadas, o ambiente, replicação e ameaças à validade. A partir da análise realizada, este trabalho conclui que apesar dos guias existirem agora, há uma grande lacuna no relatório desses experimentos. A principal contribuição deste trabalho é fornecer o status dos relatórios de experimentos centrados em humanos em engenharia de software e como este campo amadureceu. Este trabalho também propõe uma lista de informações que um relatório de experimento deve ter.

Context: Software reuse is considered as the key to a successful software development because of its potential to reduce the time to market, increase quality and reduce costs. This increase in demand made the software organizations to envision the use of software reusable assets which can also help in solving recurring problems. Till now, software reuse is confined to reuse of source code in the name of code scavenging. Now a day, software organizations are extending the concepts of software reuse to other life cycle objects as they realized that reuse of source code alone does not save money. The academia has put forward some assets as reusable and presented methods or approaches for reusing them. Also, for a successful software reuse the organizations should assess the value of reuse and keep track on their reuse programs. The other area which is vital for software reuse is the maintenance. Maintenance of reusable software has direct impact on the cost of the software. In this regard, academia has presented a number of techniques, methods, metrics and models for assessing the value of reuse and for maintaining the reusable software. Objectives: In our thesis, we investigate on the reusable assets and the methods/ approaches that are put forward by the academia for reusing those assets. Also a systematic mapping study is performed to investigate what techniques, methods, models and metrics for assessing the value of reuse and for maintaining the reused software are proposed and we also investigate their validation status as well. Methods: The databases like IEEE Xplore, ACM digital library, Inspec, Springer and Google scholar were used to search for the relevant studies for our systematic mapping study. We followed basic inclusion criteria along with detailed inclusion/exclusion criteria for selecting the appropriate article. Results: Through our systematic mapping study, we could summarize the list of 14 reusable assets along with the approaches/methods for reusing them. Taxonomy for assessing the value of reuse and taxonomy for maintaining the reusable software are presented. We also presented the methods/metrics/models/techniques for measuring reuse to assess its value and for maintaining the reusable software along with their validation status and areas in focus. Conclusion: We conclude that, there is a need for defining a standard set of reusable assets that are commonly accepted by the researchers in the field of software reuse. Most metrics/models/methods/approaches presented for assessing the value of reuse and for maintaining the reuse software are academically validated. Efforts have to be put on industrially validating them using the real data.

Context and background: Requirements engineering(RE) is a first and a very important phase in any software development which helps in building a suitable and customer satisfactory product. In the past few years, the use of Agile software development has become popular in the industry. Customer communication plays an important role in any software development life cycle. Customers state the requirements needed to develop a product in the Requirements Engineering phase. A project is likely to fail due to problems in customer communication during the RE phase. Objective: This thesis aims to study the Customer communication challenges in Agile requirements engineering, prioritize these challenges, and also find out the mitigation strategies to overcome these challenges. Research Method: A systematic mapping study is conducted to find out the customer communication challenges. Based on the data collected from the systematic mapping study, a survey is conducted to find out the mitigation strategies to overcome the customer communication challenges faced in the RE phase and also prioritize these challenges. Results: Based on the data collected from the systematic mapping study, a total of 18 customer communication challenges are identified. In the second step, a survey is conducted based on the identified challenges. The prioritization of these challenges is done by calculating the risk analysis of the challenges from the survey data. And finally, mitigation strategies are mentioned to overcome all the identified 18 challenges.

In 2016, the Japanese Council for Science, Technology and Innovation (CSTI) proposed a project about sustainable smart societies known as Society 5.0. Society 5.0 advocates the use of advances in computer science and software engineering such as internet of things, artificial intelligence, augmented and virtual reality, as a way of resolving societal issues such as reducing the number of deaths in everyday traffic, reducing the amount of greenhouse gas emissions, and so forth. In this thesis, we report on the planning, execution, and results of a systematic mapping study aiming at understanding the role of software engineering in Society 5.0. To this end, we focus on identifying the main software engineering technologies enabling Society 5.0 as well as the main software engineering open challenges hampering its realisation. Starting from an initial set of 829 peer-reviewed publications and by means of a rigorous selection process, we selected a final set of 58 primary studies, which we analysed following a meticulous data extraction, analysis, and synthesis process. The selected primary studies described a set of 13 software engineering technologies acting as enablers of Society 5.0. The application of these technologies comes with technical challenges. In this respect, the selected primary studies identified 9 software engineering open challenges hampering the realisation of Society 5.0.

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

In 2015, the United Nations (UN) put forward 17 Sustainable Development Goals (SDGs) to beachieved by 2030. Each member state should spare no effort to fulfill the goals for better lives. Thefirst objective of this study was to explore how Big Data could be used to monitor the progress,including the opportunities and challenges that such novel technologies brought. Previous studieswere reviewed critically for the first objective. The second objective was to find out what datainfrastructures were helpful in monitoring the achievement of SDG 7. A systematic mapping studywas performed to accomplish the second objective. 53 SDG-related academic papers were obtained.Their research data and where they were sourced from were manually analyzed and categorized togenerate data infrastructures for SDG 7. Besides, the automated qualitative coding was conductedbased on the manual structure to verify the manually identified data infrastructures and comparetheir frequencies in the selected papers. The methodology of combining manual and automatedqualitative analysis proposed in this study helped find a list of SDG 7 related data infrastructures.Although there were differences between the manual and automated results, the World Bank, UNdatabases, Eurostat, and IEA were considered the most frequently referred data sources; electricitydata and satellite imagery were regarded as the most commonly used data types.

This action research study investigated the feasibility of a novice teacher using concept maps as assessments in secondary science classes. The subjects in this study were the researcher, a novice pre-service science teacher, and students (n=35) in two classes of mixed-grade Foundations in Physics and Chemistry. This study tracked student and teacher experiences over an instructional unit in astronomy. All students received a 50-minute lesson on concept mapping, one class received three additional concept mapping lessons during the unit, then all students took a unit test with a paired short answer and concept map question. Student surveys were conducted to gather student feedback, and teacher reflective journaling was used to track teacher data. Data were analyzed using descriptive statistics. The results indicated that the extra concept mapping lessons did not result in higher scores on the concept maps or the paired short answer responses. The teacher journaling revealed that using concept mapping as an assessment tool was possible for a novice teacher. Advantages and barriers were identified.

Made available in DSpace on 2015-05-14T12:36:48Z (GMT). No. of bitstreams: 1 arquivototal.pdf: 4346482 bytes, checksum: 66ecee23f8ca75e6ea5bba135cfa9a42 (MD5) Previous issue date: 2014-01-22 / Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / Background: With the growing popularity of cloud computing, an challenge seen in this discipline is the management of faults that may occur in such big infrastructures that, because of its size, has a greater chance of ocurring faults, errors and failures. A work that maps the solutions already created by researchers efficiently should help visualizing gaps over those research fields. Aims: This work aims to find research gaps in the cloud computing and fault management domains, aside from building a social network of researchers in the area. Method: We conducted a systematic mapping study to collect, filter and classify scientific works in this area. The 4535 scientific papers found on major search engines were filtered and the remaining 166 papers were classified according to a taxonomy described in this work. Results: We found that IaaS is most explored in the selected studies. The main dependability functions explored were Tolerance and Removal, and the attributes were Reliability and Availability. Most papers had been classified by research type as Solution Proposal. Conclusion: This work summarizes and classifies the research effort conducted on fault management in cloud computing, providing a good starting point for further research in this area. / Fundamentação: Com o grande crescimento da popularidade da computação em nuvens, observa-se que um desafio dessa área é gerenciar falhas que possam ocorrer nas grandes infra-estruturas computacionais construídas para dar suporte à computação como serviço. Por serem extensas, possuem maior ocorrência de faltas, falhas e erros. Um trabalho que mapeie as soluções já criadas por pesquisadores de maneira simples e eficiente pode ajudar a visualizar oportunidades e saturações nesta área de pesquisa. Objetivos: Este trabalho visa mapear de forma sistemática todo o esforço de pesquisa aplicado ao gerênciamento de faltas em computação em nuvem de forma a facilitar a identificação de áreas pouco exploradas e que pode eventualmente representar novas oportunidades de pesquisa. Metodologia: Para este trabalho utiliza-se a metodologia de pesquisa baseada em evidências, através do método de mapeamento sistemático, sendo a pesquisa construída em três etapas de seleção de estudos. Método: Conduzimos um mapeamento sistemático para coletar, filtrar e classificar trabalhos científicos na área. Foram inicialmente coletados 4535 artigos científicos nos grandes engenhos de busca que, após três etapas de filtragem, acabaram sendo reduzidos a 166 artigos. Estes artigos restantes foram classificados de acordo com a taxonomia definida neste trabalho. Resultados: Observa-se que IaaS é a área mais explorada nos estudos selecionados. As funções de gerência de falhas mais exploradas são Tolerância e Remoção, e os atributos são Confiabilidade e Disponibilidade. A maioria dos trabalhos foram classificados como tipo de pesquisa de Proposta de Solução. Conclusão: Este trabalho sumariza e classifica o esforço de pesquisa conduzido em Gerenciamento de Faltas em Computação em Nuvens, provendo um ponto de partida para pesquisas futuras nesta área.