Föreliggande systematiska litteraturstudie syftade till att samla information och söka evidens för bröstcancerdrabbade kvinnors omvårdnadsbehov från sjuksköterskans i form av stöd för psykiska, sociala eller informativa behov. Sexton vetenskapliga artiklar valdes ut via databasen CINAHL (Cumulative Index to Nursing and Allied Health Literature) och fulltextdatabasen ELIN (Elecronic Library Information Navigator) för vidare granskning. Till sökningen användes sökorden breast*, cancer*, nurs* och support. Alla utvalda artiklar som härrör till syftet kvalitetsbedömdes genom på förhand bestämda granskningskriterier från modifierade förlagor efter Forsberg och Wengström (2003) och Willman, Bahtsevani och Stoltz (2007). Av resultatet framkom det att det fanns stark evidens för att kvinnor med bröstcancer har ett omvårdnadsbehov av socialt stöd, psykiskt stöd och även av information av sjuksköterskan. Omvårdnadsbehov som även kom fram i denna studie är kontinuitet i vården och personliga samtal med sjuksköterskan. Att få utöva sin religiösa tro, sin andlighet och utöva sin kulturella tillhörighet samt likaså känna förtroende är omvårdnadsbehov som blev uppenbarat i resultatet. Resultatet diskuterades utifrån Aaron Antonovskys omvårdnadsteori där känslan av sammanhang är central.

Background: Pain is a common consequence of Spinal Cord Injury (SCI). While research into pain in SCI is vast, examining musculoskeletal pain (MSKP) and low back pain (LBP) are limited. This thesis aims to investigate these categories of pain in incomplete SCI (iSCI). The experience of pain is known to affect quality of life (QoL) and function. The impact of the experience of pain, particularly of LBP, on both the QoL and function are examined in this research. While research in similar fields is predominantly conducted in single nation populations this research is set out to study three different nations. Method: The following were part of this study: • A systematic literature review on the prevalence on chronic back pain (BP), LBP and MSKP in SCI. • A translation, and preliminary validation, into Greek of the Spinal Cord Independence Measure (SCIM version III). • A cross-national survey conducted in the USA, UK and Greece. Questionnaires included the short-form McGill Pain questionnaire (SF-MPQ), EQ-5D and the SCIM III. They were collected either online or via post and 219 questionnaires were analysed. Results: The papers included in the systematic literature review were considerably heterogeneous not allowing meta-analysis to be made. 95% confidence intervals (CI) for the total number of participants in the studies were used. Among people with pain the prevalence of chronic MSKP (CMSKP) was 49% (95%CI 44%, 55%), of chronic BP (CBP) was 47% (95%CI 43%, 50%) and chronic LBP (CLBP) was 49% (95%CI 44%, 55%). GR-SCIM III maintains its unidimensionality and has acceptable internal consistency (α=0.78). Concurrent/criterion validity for the two cross-examined subscales were strong for “self-care” (ρ=-0.78) and moderate for “mobility” (ρ=-0.58). Unidimensionality was also confirmed for the English version of SCIM III, which had accepted internal consistency (α=0.79) and strong concurrent/criterion validity for “self-care” (ρ=-0.75) and moderate for “mobility” (ρ=-0.45). The survey results showed that the prevalence of current LBP is 67.9% (95%CI 61%, 73%) and of MSKP is 38.8% (95%CI 32%, 45%). LBP was of moderate intensity and most commonly described as “aching”. People who report pain, LBP or MSKP reported worse QoL. The impact of LBP on QoL was greater than that of pain in general or MSKP. The increased intensity of LBP correlated with worse function. Among the three participating countries, people from the UK had the worst experience of pain and LBP, classified themselves with the worst health status and reported the worst functional independence. Conclusion: This study offers the first systematic review on CLBP, CBP and CMSKP in SCI. It is unique in using SCIM III by self-report and into Greek. The results show that LBP is highly present in iSCI affecting both QoL and function. Both the GR-SCIM III and the SCIM III are reliable for use, however studies are needed to examine further their psychometric properties. The findings of the study fit with features of the currently used patients’ rehabilitation models.

Arts-based methods are increasingly used to facilitate meta-level learning in management education. Such increased use suggests that these methods are relevant and offer a unique contribution meeting a need in today’s management education. Yet, the literature is not clear on what this unique contribution may be even though it abounds with suggestions of varying quality. To explore this matter, I conduct a systematic literature review focused on arts-based methods, management education, and meta-level learning. I find that the unique contribution of arts-based methods is to foreground the process of making and expressing more refined perceptual distinctions, not to get accurate data, but as integral to our thinking/learning. This finding is important, because it imply that certain (commonly applied) ways of using arts-based methods may limit their potential. Finally, I suggest that future research regarding arts-based methods should focus on exploring the impact the process of learning to make and express more refined perceptual distinctions may have on managerial practice to further understand the relevance of these methods to managers.

Domestic violence is often experienced as a crisis period, and it may impact children’s well-being, everyday functioning and development. To promote these minors’ resilience, social intervention is extremely important. The support and responses attributed to these children are not always adequate for their needs and interests. Considering children’s perspectives on social intervention is crucial to improve and to provide complete social work responses. A systematic literature review was conducted, aiming to analyze how children exposed to domestic violence characterize the barriers and facilitators of social intervention. Through two databases, 8 articles were found, related to adolescents’ perspectives on social intervention in situations of domestic violence. The participants were children aged 12-18 years, who were witnesses of violence between parents or who suffered abuses from one/both parent(s). Findings demonstrated the main factors of social intervention that children recognized as being negative and unhelpful (barriers), and as being positive and helpful (facilitators). The identified barriers were lateness, mistrust, lack of child perspective, passivity, lack of value, malice, boredom, and inaccessibility. On the other hand, the established facilitators were protection, trust, child perspective, active listening, value, accessibility, sympathy, sharing, and information. Implications for social workers are provided, centered on specialized trainings and guidance, and on the use of appropriate methods when intervening with children. Also, the necessity to expand the quantity of research related to the child’s perspective on social intervention is highlighted.

Context: Developer’s within software companies work chosen choice of software development process. Choice of a particular Software Development Process impacts the work environment, end-product and might also have financial risks due to delay in delivering in the final software product. Objectives: we are investigating if the TDD could impact/applicable in large-scale industries. To achieve that we first identify the strengths and challenges while using TDD in large-scale industries. Identify what modifications can enhance the impact of TDD in large-Scale industries. Methods: Systematic Literature Review (SLR) has been used to investigate the application of TDD in large-scale industries. Using the info from SLR we conducted an online survey for validating the results obtained from SLR. As a last step we have conducted semi structured interviews to gather information from developers across industries practicing and practiced TDD. The data from the qualitative and quantitative methods is triangulated by identifying the strengths, challenges and modifications in applying TDD to large-scale industries. Results: The findings from our SLR, results validated from Survey and responses from interview participants show that TDD have both strengths, Challenges and modifications. Conclusions: Some challenges encountered when using TDD in large-scale industries are Negative test cases, linking test case modules of several developers, Communication, Overall idea about project, lack of TDD knowledge for developers practicing TDD, also lack of automation tools supporting the development of unit test-cases.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-07-01T12:47:32Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) 1-Dissertação-Aline Chagas Rodrigues Marques.pdf: 1439805 bytes, checksum: a2700ec0bf27110de6f77a8f906b3e36 (MD5) / Made available in DSpace on 2016-07-01T12:47:32Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) 1-Dissertação-Aline Chagas Rodrigues Marques.pdf: 1439805 bytes, checksum: a2700ec0bf27110de6f77a8f906b3e36 (MD5) Previous issue date: 2015-03-05 / CAPEs / A publicação do Manifesto Ágil mostra um grande valor da interação humana no processo de desenvolvimento de software, conforme pode ser observado em algumas de suas premissas como: "Indivíduos e suas interações", "Colaboração com o cliente", mostrando que estes métodos se preocupam com os fatores humanos que envolvem os processos de desenvolvimento de software. Sendo assim, esta pesquisa visa investigar de que forma os fatores humanos influenciam no processo de desenvolvimento ágil de software, para aumentar as chances de sucesso desses projetos. Para isto, foi conduzida uma revisão sistemática da literatura (RSL) e um survey para atingir esse objetivo. Foram encontrados 12 (doze) fatores humanos como: comunicação, aspectos culturais, liderança, motivação, bem-estar, autonomia, conhecimento, experiência, aprendizado, colaboração, confiança e envolvimento do cliente. Tais fatores impactam, positivamente e/ou negativamente, nas seguintes áreas: desenvolvimento de software, interação do time, sucesso de projetos ágeis e tomada de decisão. Por fim, tanto a RSL quanto o survey permitem confirmar que os fatores humanos mais relevantes dentro de métodos ágeis são Comunicação e Colaboração, o que se relacionam com características relacionadas a “indivíduos e interações entre os membros da equipe” descritas no Manifesto ágil. / The publication of the Agile Manifesto shows a large amount of human interaction in the software development process, as can be seen in some of their assumptions, such as: "Individuals and their interactions", "Customer collaboration," showing that these methods concern themselves with the human factors involved in the software development processes. Thus, this research intends to investigate how human factors influence the agile development process software, to increase the chances of success of these projects. For that, it was conducted a systematic literature review (SLR) and a survey to achieve this goal. It was found 12 human factors, such as: communication, cultural, leadership, motivation, well-being, autonomy, knowledge, experience, learning, collaboration, trust and customer engagement. Such factors impact positively and / or negatively, in the following areas: software development, team interaction, successful agile projects and decision making. Finally, both the RSL and the survey support the assertion that the most relevant human factors within agile methods are Communication and Collaboration, which relate to characteristics related to "individuals and interactions between team members" described in the Agile Manifesto.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2017-04-06T14:40:56Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação[Final] - Thiago Rodrigues Cavalcanti (3).pdf: 3773887 bytes, checksum: c9be5fcff2f29f4495fef60413a169f6 (MD5) / Made available in DSpace on 2017-04-06T14:40:56Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação[Final] - Thiago Rodrigues Cavalcanti (3).pdf: 3773887 bytes, checksum: c9be5fcff2f29f4495fef60413a169f6 (MD5) Previous issue date: 2011-03-15 / O Simpósio Brasileiro de Engenharia de Software (SBES) está na sua 25ª edição em 2011. Ao longo da sua história, vários progressos no campo da engenharia de software foram publicados e debatidos. Durante o Simpósio, os avanços e pesquisas ganham voz e repercutem no meio acadêmico nacional. Entender como a pesquisa de engenharia de software publicada no SBES evoluiu nesse período é o principal objetivo deste trabalho. Os demais objetivos se relacionam com o primeiro diretamente. Compreender quais as áreas de pesquisa e os métodos mais utilizados, e ainda traçar um histórico das abordagens, das unidades de análise e dos gêneros de pesquisa. Neste trabalho ainda quantificamos os artigos publicados em inglês, a quantidade de referências e citações de cada paper. Para entendermos essa evolução foi necessário utilizar algumas classificações difundidas na literatura visando avaliar os trabalhos publicados e os simpósios como um todo. A metodologia utilizada passou pela leitura dos últimos 24 anos do SBES e a consolidação em um formulário de extração. O método inclui ainda detalhes e exemplos dos critérios utilizados, visando dar maior qualidade ao processo. Por fim, uma ferramenta de consolidação automatizada integra os valores encontrados. Os resultados mostram como cada um dos critérios acima definidos evoluiu ao longo do tempo, quais centros de pesquisa têm mais espaço no contexto do SBES e quais aspectos do estudo da engenharia de software podem ser aprimorados. Deste modo, este trabalho ajuda a entender o panorama brasileiro de engenharia de software e demonstra o papel relevante da pesquisa para evolução da ciência. / The Brazilian Symposium on Software Engineering (SBES) is on its 25th edition in 2011. Throughout its history, several improvements in the field of software engineering have been published and discussed. During the Symposium, the advances and researches gained voice and repercussions in the national academic environment. Understanding how software engineering research published in SBES evolved in this period is the main objective of this work. The other objectives are directly related to the first. To understand the areas of research and the methods used, and build a historical analysis of the research approaches, the unit of analysis and the type of research. This work has quantified the articles published in English, the number of references, and citations of each paper. In order to understand this evolution, it was necessary to use some widespread classifications in literature to evaluate the published works and symposia as a whole. The methodology began by reading the last 24 years of SBES and the consolidation in an extraction form. The method also includes details and examples of the criteria employed to give more quality to the process. Finally, an automated consolidation tool integrated the values found. The results show how each of the criteria described above has evolved over time, research centers which have more space in the context of SBES and also which aspects of the study in software engineering can be improved. Thus, this work assists to understand the Brazilian panorama of software engineering and demonstrates the important role of research for science advance.

Context: The Internet has become a vital channel for disseminating and accessing scientific literature for both the academic and industrial research needs. Nowadays, everyone has wide access to scientific literature repositories, which comprise of both “white” and “Grey” literature. The “Grey” literature, as opposed to “white” literature, is non-peer reviewed scientific information that is not available using commercial information sources such as IEEE or ACM. A large number of software engineering researchers are undertaking systematic literature reviews (SLRs) to investigate empirical evidence in software engineering. The key reason to include grey literature during information synthesis is to minimize the risk of any bias in the publication. Using the state of the art non-commercial databases that index information, the researchers can make the rigorous process of searching empirical studies in SLRs easier. This study explains the evidence of Grey literature while performing synthesis in Systematic Literature Reviews. Objectives: The goals of this thesis work are, 1. To identify the extent of usage of Grey Literature in synthesis during systematic literature reviews. 2. To investigate if non-commercial information sources primarily Google Scholar are sufficient for retrieving primary studies for SLRs. Methods: The work consists of a systematic literature review of SLRs and is a tertiary study and meta-analysis. The systematic literature review was conducted on 138 SLRs’ published through 2003 until 2012 (June). The article sources used are IEEEXplore, ACM Digital Library, Springer-Link and Science Direct. Results: For each of the selected article sources such as ACM, IEEEXplore, Springer-link and Science Direct, we have presented results, which describe the extent of the usage of Grey literature. The qualitative results discuss various strategies for systematic evaluation of the Grey literature during systematic literature review. The quantitative results comprise of charts and tables, showing the extent of Grey literature usage. The results from analysis of Google Scholar database describe the total number of primary studies that we are able to find using only Google Scholar database. Conclusion: From the analysis of 138 Systematic Literature Reviews (SLRs’), we conclude that the evidence of Grey literature in SLRs is around 9%. The percentage of Grey literature sources used in information synthesis sections of SLRs is around 93.2%. We were able to retrieve around 96 % of primary studies using Google Scholar database. We conclude that Google Scholar can be a choice for retrieving published studies however; it lacks detailed search options to target wider pool of articles. We also conclude that Grey literature is widely available in this age of information. We have provided guidelines in the form of strategies for systematic evaluation of Grey literature. / Sammanhang: Internet har blivit en viktig kanal för att sprida och få tillgång vetenskaplig litteratur för både akademiska och industriella forskningsbehov. Numera har alla bred tillgång till vetenskaplig litteratur förråd, som omfattar både "vit" och "grå" litteratur. Den "grå" litteratur, som motsats till "vita" litteratur, är icke-vetenskapligt granskad vetenskaplig information som inte är tillgänglig med kommersiella informationskällor såsom IEEE och ACM. Ett stort antal forskare software engineering genomför systematiska litteraturöversikter (systemkameror) för att undersöka empiriska bevis programvaruteknik. Den viktigaste orsaken till att omfatta grå litteratur under Information syntes är att minimera risken för att partiskhet i publikationen. Använda toppmoderna icke-kommersiella databaser som indexerar information kan forskarna göra rigorösa processen att söka empiriska studier i systemkameror lättare. Denna studie förklarar bevis på grå litteratur när de utför syntes i systematiska litteraturöversikter. Mål: Målen med detta examensarbete är, 1. För att identifiera omfattningen av användningen av Grey litteratur i syntes under systematisk litteratur recensioner. 2. För att undersöka om icke-kommersiella informationskällor främst Google Scholar är tillräckliga för att hämta primära studier för systemkameror. Metoder: Verket består av en systematisk litteraturgenomgång av systemkameror och är en tertiär studie och metaanalys. Den systematiska litteraturstudie genomfördes på 138 systemkameror "publiceras via 2003 till 2012 (juni). Artikeln används källorna är IEEEXplore, ACM Digital Library, Springer-Link och Science Direct. Resultat: För vart och ett av de utvalda artikeln källor såsom ACM, IEEEXplore, Springer-länk och Science Direct, har vi presenterat resultat, som beskriver omfattningen av användningen av grå litteratur. De kvalitativa resultaten diskuterar olika strategier för systematisk utvärdering av grå litteratur under systematisk litteraturöversikt. De kvantitativa resultaten består av diagram och tabeller, som visar omfattningen av Grey litteratur användning. Resultaten från analys av Google Scholar-databasen beskriver det totala antalet primära studier som vi kan hitta med enbart Google Scholar databas. Slutsats: Av analysen av 138 systematiska litteraturöversikter (systemkameror) kan vi dra slutsatsen att bevisen för grå litteratur i systemkameror är cirka 9%. Den procentuella andelen Grey litteraturkällor som används i avsnitt informations syntes av systemkameror är cirka 93,2%. Vi kunde hämta omkring 96% av primära studier med Google Scholar databas. Vi drar slutsatsen att Google Scholar kan vara ett val för hämta publicerade studier dock, det saknar detaljerade sökalternativ för att rikta större pool av artiklar. Vi avslutar också att grå litteratur är allmänt tillgänglig i denna tid av information. Vi har försett riktlinjer i form av strategier för systematisk utvärdering av Grey litteratur. / Affan Yasin : Skype id (affan.yasin) Ijlal Hasnain: Skype id (bluesols)

Context: Software development in a setting in which the development sites are dispersed across geographical areas, either close proximity or globally, is fast becoming a widespread trend. This software development arrangement is also known as Global Software Development (GSD) or Distributed Software Development (DSD) or Global Software Engineering (GSE). Projects executed by a dispersed team have been noted as a more risky and challenging venture than projects run with teams under the same roof. Therefore the knowledge of the potential challenges and the probable mitigation strategies for GSD is vital for running a successful project. Objectives: The study entails the identification of GSD related challenges as well as their mitigation strategies. The collected challenges and mitigation strategies are later compiled into checklists. The developed checklists can be incorporated into risk management process particularly risk identification and risk mitigation planning. Methods: This research extends an existing systematic literature study conducted on empirical research on GSD, which was based on a review of publications from 2000 to 2007. The previous research is incorporated in this research and, in addition, papers between 2007 and 2009 are reviewed. In contrast to the previous research was aimed at gathering empirical evidence in GSD, however in this research the focus is specifically on challenges associated with GSD projects as well as the mitigation strategies that can be employed. An industrial survey was also conducted to validate the checklists and determine if the identified challenges and mitigation strategies were pervasive in industry. Furthermore interviews were also conducted to further validate the usefulness and usability of the developed checklists. Result: As a result, from the systematic literature review for publications between 2000 and 2009, a total of 48 challenges and 42 mitigation strategies were identified and placed in two separate categorized checklists. These challenges and mitigation strategies are elaborated in this paper. From the survey result, no additional challenges and 4 strategies were identified in the survey. Meanwhile from the interviews, all interviewees reported that the checklists are useful and easy to use. Conclusion: The absence of new challenges being identified from the study did not merit a conclusion that all possible challenges in GSD have been revealed. Therefore we conclude that more empirical research still needs to be done on identifying the challenges and mitigation strategies associated with GSD settings. Furthermore the checklists can be useful and valuable in identifying challenges and the potential mitigation strategies for communication, control and coordination mechanisms in distributed software development projects.

Context: In the last decade, Agile software development methods were proposed as a response to plan-driven methods. The main aim for this paradigm shift was to cope up with constant changes. Core values that are central to agile methods are described in Agile Manifesto. Agile practices define how agile methods are implemented in practice. Objectives: This study aims to investigate what practices were considered and adopted as part of agile philosophy, and identify evidence on the use of agile practices in reference to what defines agile. Methods: We conducted a systematic literature review. The review includes 186 primary studies published between 2000 and 2010. Quality assessment based on rigor and relevance as identified in the selected papers has been conducted. Non-empirical papers were classified based on themes they addressed. Empirical papers were analyzed based on two factors: 1. if they described the use of agile practices for a software project/product in general, 2. if they described the use of agile practices for a specific purpose/activity Application type, team size and experience of subjects in the primary studies were extracted. The alignment between practices reported in the studies with the core agile values is analyzed. Results: A total of 119 studies were conducted in industry and 67 in academia. Nearly half the papers published by researchers are non-empirical and present analysis of agile practices in various topics. Over half of the empirical papers were focused on evaluation/assessment of a specific aspect of agile. ‘Pair programming’ received most attention in this direction. Among the empirical studies that described agile practices for academic projects, ‘Pair programming’ and ‘Test driven development’ were the most considered practices. Among the 119 studies conducted in industry, 93 studies described the use of agile practices for the overall project/product development while the remaining studies described experiences of single practices like Pair Programming or the modification/adoption of agile for non-software aspects in software projects. Practices adopted have been ranked based on team size, practitioners’ experience and application type. A method for agile assessment based on core agile values is developed and exemplified. Conclusions: Practices that are considered agile vary with context although ‘Pair programming’, ‘Continuous integration’, ‘Refactoring and Testing continuous throughout the project are the most common practices used. ‘Test driven development’ was not highly adopted by practitioners. But it was not clear if test cases were written before code construction in projects where continuous testing was performed. However, this was completely opposite in academic projects. Practices ‘On-site frequently modified. In many of the studies inspected, practices adopted were not aligned with agile values. Although practices related to technical aspects of software development are in place, agile practices that focus aspects like ‘working together’ and ‘motivated individuals’ are often not used in practice. Moreover, many of the studies were not reported to an extent that it was possible to draw any inferences on the usability/applicability, benefits and limitations of the agile practices. To this end, a major implication is to improve the quality of the studies and a need for a common framework to report the results of agile practices’ adoption.