Context: Today, most of the software products are built with COTS components. When a new version of these components is available, it is difficult to perform testing as the vendors of the component do not usually provide source code. Various regression testing techniques have been developed, but most of the techniques are based on the source code for change identification. So, the testers are facing different challenges in performing effective testing. Objectives: The goal of this research is to find out the different approaches that are used to identify changes in modified COTS component, analyze the main characteristics of those approaches and investigate how these characteristics can be used in selection and development of CBRT approach. Methods: To fulfill the aims of the research, we have conducted systematic literature review of different CBRT approaches from the year 1993-2010. From systematic literature we found out 32 papers relevant to our study. Data related to our research are extracted from those papers and conclusion is made. The relevant articles were searched in six scientific databases such as IEEE Explore, ACM Digital Library, SpringerLink, Science Direct, Scopus, and Engineering Village. Furthermore, online survey was conducted based on the characteristics of CBRT approaches. This survey was conducted to validate the SLR result. Results: From the systematic Literature Review we have found out 8 different characteristics of CBRT approaches such as applicability, automation, complexity, behavior model used, coverage criteria, strength and weakness, theory used and input. We observe that these are the most important characteristics in CBRT approaches and these approaches should be considered in selecting or developing new CBRT approach. The results from the survey also validate our findings. From survey some more factors were identified. Conclusion: The research develops the state-of-art of CBRT approaches towards future research. The result of this thesis will be helpful for the researchers as well as practitioners who are working on CBRT. The result of the thesis can be considered as a basis for further study. Based on the result of this thesis further study can be done on making a framework based on these characteristics and support component based regression testing. / Nabin Raj Dulal, 139, Jagriti Tole Marg, Balaju-16, Kathmandu , Nepal ph: +97714351087

Context. The use of data warehouses, a specialized class of information systems, by organizations all over the globe, has recently experienced dramatic increase. A Data Warehouse (DW) serves organiza-tions for various important purposes such as reporting uses, strategic decision making purposes, etc. Maintaining the quality of such systems is a difficult task as DWs are much more complex than ordi-nary operational software applications. Therefore, conventional methods of software testing cannot be applied on DW systems. Objectives. The objectives of this thesis study was to investigate the current state of the art in DW testing, to explore various DW testing tools and techniques and the challenges in DW testing and, to identify the improvement opportunities for DW testing process. Methods. This study consists of an exploratory and a confirmatory part. In the exploratory part, a Systematic Literature Review (SLR) followed by Snowball Sampling Technique (SST), a case study at a Swedish government organization and interviews were conducted. For the SLR, a number of article sources were used, including Compendex, Inspec, IEEE Explore, ACM Digital Library, Springer Link, Science Direct, Scopus etc. References in selected studies and citation databases were used for performing backward and forward SST, respectively. 44 primary studies were identified as a result of the SLR and SST. For the case study, interviews with 6 practitioners were conducted. Case study was followed by conducting 9 additional interviews, with practitioners from different organizations in Sweden and from other countries. Exploratory phase was followed by confirmatory phase, where the challenges, identified during the exploratory phase, were validated by conducting 3 more interviews with industry practitioners. Results. In this study we identified various challenges that are faced by the industry practitioners as well as various tools and testing techniques that are used for testing the DW systems. 47 challenges were found and a number of testing tools and techniques were found in the study. Classification of challenges was performed and improvement suggestions were made to address these challenges in order to reduce their impact. Only 8 of the challenges were found to be common for the industry and the literature studies. Conclusions. Most of the identified challenges were related to test data creation and to the need for tools for various purposes of DW testing. The rising trend of DW systems requires a standardized testing approach and tools that can help to save time by automating the testing process. While tools for operational software testing are available commercially as well as from the open source community, there is a lack of such tools for DW testing. It was also found that a number of challenges are also related to the management activities, such as lack of communication and challenges in DW testing budget estimation etc. We also identified a need for a comprehensive framework for testing data warehouse systems and tools that can help to automate the testing tasks. Moreover, it was found that the impact of management factors on the quality of DW systems should be measured. / Shahan (+46 736 46 81 54), Ahmad (+46 727 72 72 11)

Context: Over the recent years, ‘Lean Software Development’ (LSD) has been emerging as a significant practice in the Software Industry. The inherent nature of ‘Lean’ to efficiently handle frequently changing customer needs by minimizing ‘Waste’ is a major success factor in practicing it in the context of ‘Software Engineering’. In simple words, Lean Software Development is the true translation of Lean Manufacturing and Lean IT principles to Software Engineering. This work presents an in-depth analysis on the implication of lean methodologies from both ‘State of Art’ and ‘State of Practice’ in the context of Software Engineering. Objectives: The prime objective of the study is to investigate what methodologies were considered & adopted under lean philosophy and to present relevant evidence on the implication of lean methodologies in reference to what defines ‘lean’ in Software Engineering. An extensive literature review was aimed to find the existing challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were employed by various software organizations to appease their negative impact. Industrial interviews were conducted by interviewing lean experts, with a motive to find the current state of lean implementation in software industry. The outcomes from the systematic literature review (State of Art) and the industry (State of Practice) are comparatively analysed to explore the similarities and differences on the state of lean implication. Finally, a set of guidelines are recommended that would benefit an Industrial Practitioner/Stakeholder/Academic Researcher in practicing the appropriate lean methodology in the context of software engineering. Methods: We conducted a ‘Systematic literature review’ (SLR) by systematically analyzing relevant studies and then interviewed industrial experts to validate our findings. The systematic literature review was conducted according to the guidelines proposed by Dr. Barbara Kitchenham stated in ‘Guidelines for performing Systematic Literature Reviews’ article. The thorough review helped us in identifying various challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were practiced in the context of software engineering. The associated benefits of practicing the lean methodologies are also presented. The extensive review included peer reviewed articles from electronic databases such as IEEE Explore, Inspec, Scopus and ISI. In addition to this, we conducted snowball sampling on the references of the selected articles to avoid the potential risk of losing relevant and valuable information. Also, other potential sources of information such as books, theses/dissertations, white papers and website/blog articles are included as a part of Grey Literature. In this study, the articles related to the implication of lean methodologies in the context of software engineering were considered. The review included 72 primary studies published between 1993 and 2012. The primary studies were selected based on the following criteria: If they presented the challenging factors that negatively influenced the success of software projects. If they depicted the implication of lean mitigation methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) that appeased the negative impact of the identified challenging factors that hampered the success of software projects. If they depicted the implication of lean methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) in general or for a specific development/ Management/ Maintenance improvement activities that lead to the success of software projects in the context of software engineering. If they presented the benefits of practicing lean methodologies in the context of software engineering. The study quality assessment was done based on the quality criteria defined in the ‘Quality assessment criteria checklist’. The data such as Article ID, Article Title, Literature type (Peer- reviewed, Non-peer reviewed), Context of validation of the lean methodology (Industry/Academia), Subjects considered for the study (Researchers/students, Industrial practitioners), Type of article publication (Conference/ Journal/ Books/ Thesis Reports/ Doctoral dissertations/ Other), Research method used in the study (Case Study/ Experiment/ Experience Report/ Not stated/ Secondary Data Analysis/ Literature Review), Context of conducting the research (Industry/ Academia/ Not stated/ Both), Context of validation of the study (Strong/ Medium/ Weak), Publication date & year, Source of the publication, are extracted as a part of Quantitative analysis. The secondary data analysis for both ‘State of Art’ (Systematic literature review) and ‘State of Practice’ (Industry) was carried by performing a generic data analysis designed to answer our research questions. The more specific data such as the challenging factors that negatively influenced the success of software projects, the type of lean contribution presented i.e., the methodology being a Tool, Technique, Practice, Principal, Process or a Method, along with the benefits associated on their implication that helped us to answer our research questions are extracted as a part of qualitative analysis from the selected studies. The industrial interviews were conducted by interviewing potential lean experts who had decent experience in lean software development, to find the current state of lean implication in the software industry. In the end, a comparative analysis was performed to clearly understand the state of convergence and divergence between the results from extensive literature review and the industry with respect to the implication of lean methodologies in the context of software engineering. Results: A total of 72 primary articles were selected for data extraction. 56 articles were selected from the electronic databases that clearly depicted lean implementation in the context of software engineering. 9 articles were selected by conducting snowball sampling i.e. by scrutinizing the references of the selected primary studies and finally the grey literature resulted in 7 articles. Most of the articles discussed about lean implication in the context of software engineering. The depicted lean methodologies were validated in either Industry or Academia. A few articles depicted regarding lean principles and their benefits in the context of software engineering. Most of the selected articles in our study were peer- reviewed. Peer reviewing is a process of evaluating one’s work or performance by an expert in the same field in order to maintain or enhance the quality of work or performance in the particular field. This indicates that the articles considered for data extraction have been reviewed by potential experts in the research domain. Conclusions: This study provided a deeper insight into lean implication in the context of software engineering. The aim of the thesis is to find the challenging factors that negatively influenced the success of software projects. A total of 54 challenges were identified from the literature review. The 72 primary articles selected from various resources yielded 53 lean methodologies. The lean methodologies were grouped into Principles, practices, tools and methods. Mapping between the identified challenges and the mitigation lean methodologies is presented. Industrial interviews were conducted to find the current state of lean implication in software engineering. A total of 30 challenges were identified from the industry. A total of 40 lean methodologies were identified from the interviews. Comparative analysis was done to find the common challenges and mitigation lean methodologies between the State of art and State of practice. Based on the analysis a set of guidelines are presented at the end of the document. The guidelines benefit an industrial practitioner in practicing the appropriate lean methodology. Keywords: Lean Methodology, Lean software development, lean software management, lean software engineering, Systematic literature review, literature review. / Context: Over the recent years, ‘Lean Software Development’ (LSD) has been emerging as a significant practice in the Software Industry. The inherent nature of ‘Lean’ to efficiently handle frequently changing customer needs by minimizing ‘Waste’ is a major success factor in practicing it in the context of ‘Software Engineering’. In simple words, Lean Software Development is the true translation of Lean Manufacturing and Lean IT principles to Software Engineering. This work presents an in-depth analysis on the implication of lean methodologies from both ‘State of Art’ and ‘State of Practice’ in the context of Software Engineering. Objectives: The prime objective of the study is to investigate what methodologies were considered & adopted under lean philosophy and to present relevant evidence on the implication of lean methodologies in reference to what defines ‘lean’ in Software Engineering. An extensive literature review was aimed to find the existing challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were employed by various software organizations to appease their negative impact. Industrial interviews were conducted by interviewing lean experts, with a motive to find the current state of lean implementation in software industry. The outcomes from the systematic literature review (State of Art) and the industry (State of Practice) are comparatively analysed to explore the similarities and differences on the state of lean implication. Finally, a set of guidelines are recommended that would benefit an Industrial Practitioner/Stakeholder/Academic Researcher in practicing the appropriate lean methodology in the context of software engineering. Methods: We conducted a ‘Systematic literature review’ (SLR) by systematically analyzing relevant studies and then interviewed industrial experts to validate our findings. The systematic literature review was conducted according to the guidelines proposed by Dr. Barbara Kitchenham stated in ‘Guidelines for performing Systematic Literature Reviews’ article. The thorough review helped us in identifying various challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were practiced in the context of software engineering. The associated benefits of practicing the lean methodologies are also presented. The extensive review included peer reviewed articles from electronic databases such as IEEE Explore, Inspec, Scopus and ISI. In addition to this, we conducted snowball sampling on the references of the selected articles to avoid the potential risk of losing relevant and valuable information. Also, other potential sources of information such as books, theses/dissertations, white papers and website/blog articles are included as a part of Grey Literature. In this study, the articles related to the implication of lean methodologies in the context of software engineering were considered. The review included 72 primary studies published between 1993 and 2012. The primary studies were selected based on the following criteria: If they presented the challenging factors that negatively influenced the success of software projects. If they depicted the implication of lean mitigation methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) that appeased the negative impact of the identified challenging factors that hampered the success of software projects. If they depicted the implication of lean methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) in general or for a specific development/ Management/ Maintenance improvement activities that lead to the success of software projects in the context of software engineering. If they presented the benefits of practicing lean methodologies in the context of software engineering. The study quality assessment was done based on the quality criteria defined in the ‘Quality assessment criteria checklist’. The data such as Article ID, Article Title, Literature type (Peer- reviewed, Non-peer reviewed), Context of validation of the lean methodology (Industry/Academia), Subjects considered for the study (Researchers/students, Industrial practitioners), Type of article publication (Conference/ Journal/ Books/ Thesis Reports/ Doctoral dissertations/ Other), Research method used in the study (Case Study/ Experiment/ Experience Report/ Not stated/ Secondary Data Analysis/ Literature Review), Context of conducting the research (Industry/ Academia/ Not stated/ Both), Context of validation of the study (Strong/ Medium/ Weak), Publication date & year, Source of the publication, are extracted as a part of Quantitative analysis. The secondary data analysis for both ‘State of Art’ (Systematic literature review) and ‘State of Practice’ (Industry) was carried by performing a generic data analysis designed to answer our research questions. The more specific data such as the challenging factors that negatively influenced the success of software projects, the type of lean contribution presented i.e., the methodology being a Tool, Technique, Practice, Principal, Process or a Method, along with the benefits associated on their implication that helped us to answer our research questions are extracted as a part of qualitative analysis from the selected studies. The industrial interviews were conducted by interviewing potential lean experts who had decent experience in lean software development, to find the current state of lean implication in the software industry. In the end, a comparative analysis was performed to clearly understand the state of convergence and divergence between the results from extensive literature review and the industry with respect to the implication of lean methodologies in the context of software engineering. Results: A total of 72 primary articles were selected for data extraction. 56 articles were selected from the electronic databases that clearly depicted lean implementation in the context of software engineering. 9 articles were selected by conducting snowball sampling i.e. by scrutinizing the references of the selected primary studies and finally the grey literature resulted in 7 articles. Most of the articles discussed about lean implication in the context of software engineering. The depicted lean methodologies were validated in either Industry or Academia. A few articles depicted regarding lean principles and their benefits in the context of software engineering. Most of the selected articles in our study were peer- reviewed. Peer reviewing is a process of evaluating one’s work or performance by an expert in the same field in order to maintain or enhance the quality of work or performance in the particular field. This indicates that the articles considered for data extraction have been reviewed by potential experts in the research domain. Conclusions: This study provided a deeper insight into lean implication in the context of software engineering. The aim of the thesis is to find the challenging factors that negatively influenced the success of software projects. A total of 54 challenges were identified from the literature review. The 72 primary articles selected from various resources yielded 53 lean methodologies. The lean methodologies were grouped into Principles, practices, tools and methods. Mapping between the identified challenges and the mitigation lean methodologies is presented. Industrial interviews were conducted to find the current state of lean implication in software engineering. A total of 30 challenges were identified from the industry. A total of 40 lean methodologies were identified from the interviews. Comparative analysis was done to find the common challenges and mitigation lean methodologies between the State of art and State of practice. Based on the analysis a set of guidelines are presented at the end of the document. The guidelines benefit an industrial practitioner in practicing the appropriate lean methodology. Keywords: Lean Methodology, Lean software development, lean software management, lean software engineering, Systematic literature review, literature review. / 0091-8375920473

Context: Mutation testing is a fault-based technique for measuring the effectiveness of a test set in terms of its ability to detect faults. Mutation testing seeds artificial faults into an application and checks whether a test suite can detect them. If these faults are not found, the test suite is still not considered to be 'good enough'. However, there are also mutations which keep the program semantics unchanged and thus cannot be detected by any test suite. Finding a way to assess these mutations is also known as the equivalent mutant problem (EMP). Objectives: The main objective of this thesis is to conduct a systematic literature review in the field of mutation testing, to identify and classify existing methods for equivalent mutants detection. In addiction, other objectives are: analyze possibilities to improve existing methods for equivalent mutant detection, implement new or improved method and compare it with existing ones. Methods: Based on the systematic literature review method we have went over publications from six electronic databases and one conference proceedings. Standard method was extended by scanning lists of references and some alternative sources: searching in Google Scholar, checking personal websites of relevant authors and contacting all of them. We have performed all the systematic literature review steps such as the protocol development, initial selection, final selection, quality assessment, data extraction and data synthesis. In the second part of this thesis - an experiment, we have implemented four second order mutation testing strategies and compared them each other from four different perspectives: mutants reduction, equivalent mutants reduction, fault detection loss and mutation testing process time reduction. Results: The search identified 17 relevant techniques in 22 articles. Three categories of techniques can be distinguished: detecting (DEM), suggesting (SEM) and avoiding equivalent mutants generation (AEMG). Furthermore, for each technique current state of development and some ideas on how to improve it are provided. The experiment proved that DifferentOperators strategy gives the best results in all four investigated areas. In addition, time for manual mutants classification against equivalence was measured. Assessing one first order mutant takes 11 minutes 49 seconds, while for the second order mutants classification time is 9 minutes 36 seconds in average. Conclusions: After three decades of studies, results obtained for techniques from the DEM group are still far from perfection (best one is detecting 47,63% of equivalent mutants). Thus, new paths for the solution have been developed - SEM and AEMG group. Methods from both categories help in dealing with EMP, however from SEM provide only mutants likely to equivalent, while from AEMG cause some loss of test effectiveness. The conclusion from the experiment is that DifferentOperators strategy gives the best results among all proposed.

Abstract—Background: Software Process Improvement (SPI) maturity models have been developed to assist organizations to enhance software quality. Agile methodologies are used to ensure productivity and quality of a software product. Amongst others they are applied in Small and Medium – sized Enterprises (SMEs). However, little is known about the combination of Agile methodologies and SPI maturity models regarding SMEs and the results that could emerge, as all the current SPI models are addressed to larger organizations and all these improvement models are difficult to be used by Small and Medium – sized firms. Combinations of these methodologies could lead to improvement in the quality of the software products, better project management methodologies and organized software development framework. Objectives: The aim of this study is to identify the main Agile methodologies and SPI maturity models applied in SMEs, the combinations of these methodologies, and the results that could emerge. Through these combinations, new software development frameworks are proposed. What is more, the results of this study can be used as a guide with the appropriate combination for each SME, as a better project management methodology or as improvement in the current software engineering practices. Methods: A Systematic Literature Review was conducted, resulting in 71 selected relevant papers ranging from 2001 to 2013. Besides, a survey has been performed from June 2013 to October 2013, including 49 participants. Results: Seven Agile methodologies and six different SPI maturity models were identified and discussed. Furthermore, the combination of eight different Agile methodologies and Software Process Improvement maturity models is presented, and as well as their benefits and drawbacks that could emerge in Small and Medium – sized firms. Conclusion: The majority of the Agile methodologies and SPI maturity models are addressed to large or very large enterprises. Thus, little research has been conducted for SMEs. The combinations of the Agile methodologies and SPI maturity models are usually performed in experimental stages. However, it has been observed that such type of combination could present numerous benefits, which can also be applicable in SMEs as well. The combinations that are most common are the CMMI and XP, CMMI and Scrum, CMMI and Six Sigma, and the PRINCE2 and DSDM. / 0034-636835645

Context: Software cost and effort estimation are important activities for planning and estimation of software projects. One major player for cost and effort estimation is functional size of software which can be measured in variety of methods. Having several methods for measuring one entity, converting outputs of these methods becomes important. Objectives: In this study we investigate different techniques that have been proposed for conversion between different Functional Size Measurement (FSM) techniques. We addressed conceptual similarities and differences between methods, empirical approaches proposed for conversion, evaluation of the proposed approaches and improvement opportunities that are available for current approaches. Finally, we proposed a new conversion model based on accumulated data. Methods: We conducted a systematic literature review for investigating the similarities and differences between FSM methods and proposed approaches for conversion. We also identified some improvement opportunities for the current conversion approaches. Sources for articles were IEEE Xplore, Engineering Village, Science Direct, ISI, and Scopus. We also performed snowball sampling to decrease chance of missing any relevant papers. We also evaluated the existing models for conversion after merging the data from publicly available datasets. By bringing suggestions for improvement, we developed a new model and then validated it. Results: Conceptual similarities and differences between methods are presented along with all methods and models that exist for conversion between different FSM methods. We also came with three major contributions for existing empirical methods; for one existing method (piecewise linear regression) we used a systematic and rigorous way of finding discontinuity point. We also evaluated several existing models to test their reliability based on a merged dataset, and finally we accumulated all data from literature in order to find the nature of relation between IFPUG and COSMIC using LOESS regression technique. Conclusions: We concluded that many concepts used by different FSM methods are common which enable conversion. In addition statistical results show that the proposed approach to enhance piecewise linear regression model slightly increases model’s test results. Even this small improvement can affect projects’ cost largely. Results of evaluation of models show that it is not possible to say which method can predict unseen data better than others and it depends on the concerns of practitioner that which model should be used. And finally accumulated data confirms that empirical relation between IFPUG and COSMIC is not linear and can be presented by two separate lines better than other models. Also we noted that unlike COSMIC manual’s claim that discontinuity point should be around 200 FP, in merged dataset discontinuity point is around 300 to 400. Finally we proposed a new conversion approach using systematic approach and piecewise linear regression. By testing on new data, this model shows improvement in MMRE and Pred(25). / Javad Amiri: Nabshe Kooche 3, Bolvare shadi, Farhangian 2, Qom, Iran, phone: +989127476593 Vinod Kumar: s/o P.V.Kondala Rao, Main Road Khaji Street Rajahmundry. A.P. India pin: 533101 phone: +917396449336

This study has investigated what current problems exist in the realm of decision making AI. This has been achieved by analyzing current literature between 2010 to 2019. Using a systematic literature review as the research method, the end product shows what problems are the toughest to solve within a certain time period. To conduct this study there had to be a need to conduct this literature review. Due to the fact that there is not any compilation that has specifically targeted the downside and problems that can occur when implementing an artificial intelligence (AI). For these reasons the following research question was conceived: "What are the current problems concerning data analysis conducted by AI?" In order to get a deeper understanding about certain where AI can go wrong, a theoretical framework has been created, explaining a few frequent terms used in the subject area. The primary problem areas were found to be the interpretation, or the misconfiguration, of the data that could cause negative effects, i.e. discrimination.

Bakgrund Ätstörningar är idag vanligt förekommande och betraktas som ett betydande hälsoproblem. Uppskattningsvis lider tio procent av unga kvinnor av någon form av ätstörning. Ätstörningar kännetecknas av att relationen till och synen på mat blivit osund och har ofta ett långdraget sjukdomsförlopp med såväl medicinska som psykologiska komplikationer. Anorexia nervosa är den mest efterforskade typen av ätstörning och den psykiska sjukdom med starkast koppling till förtida död. Behandlingen utförs i multiprofessionella team där sjuksköterskans specifika kompetens och ansvarsområde är evidens- och personcentrerad omvårdnad. I dagsläget saknas nationella riktlinjer för behandling av ätstörningar även om det finns specialiserad ätstörningsvård. Syfte Syftet var att undersöka hur patienter diagnostiserade med anorexia nervosa upplever omvårdnad och behandling. Metod Den metod som användes var en icke-systematisk litteraturöversikt. En sammanställningav relevant befintlig forskning gjordes för att undersöka patienters upplevelser av vården vid anorexia nervosa. Sökningar efter vetenskapliga artiklar genomfördes i databaserna PubMed ochCinahl. En integrerad analys genomfördes och det insamlade materialet presenterades i olika kategorier. Resultat  Tre övergripande kategorier som belyste patienters upplevelser av behandling, behandlare och vårdmötet identifierades. Skapandet av behandlingsallians och patientens möjlighet att påverka behandlingen belystes i flera studier och beskrevs påverka behandlingsutfallet positivt. Flera studier beskrev även behandlarens karaktärsdrag och beteenden samt hur dessa kunde påverka såväl behandling som alliansskapandet. Resultatet kopplades till KASAM då flera möjligheter att stärka patientens upplevelse av meningsfullhet, begriplighet och hanterbarhet beskrivs. Slutsats Det finns ingen entydig faktor som främjar behandlingen vid anorexia nervosa, snarare samverkar ett flertal faktorer i behandlingen. Med mer omfattande kunskap om dessa faktorer kan behandlaren med större framgång stötta patienter i sitt tillfrisknande. / Background Eating disorders are common today and are considered a significant health problem. An estimated ten percent of young women suffer from some form of eating disorder. Eating disorders are characterized by the relationship to and view of food becoming unhealthy and often has a long course of illness with both medical and psychological complications. Anorexia nervosa is the most researched type of eating disorder and the mental illness with the strongest link to premature death. The treatment is performed in multi-professional teams where the nurse's specific competence and area of responsibility is evidence- and person-centered nursing. At present, there are no national guidelines for the treatment of eating disorders, even though there is specialized care for eating disorders. Aim The aim was to explore how patients diagnosed with anorexia nervosa perceive care and treatment. Method The method used was a non-systematic literature study. A compilation of existing, relevant research was made with the aim of studying the care that patients with anorexia nervosa receive. Searches for scientific articles were conducted in the databases PubMed and Cinahl. An integrated analysis was implemented and the gathered material was presented in categories. Results Three main categories emerged that highlighted the patients experiences of the treatment, the caregiver and the encounter with care. The formation of treatment alliances and the patient’s ability to influence the treatment was highlighted in multiple studies and was described as having a positive effect on the treatment outcome. Several studies also described the caregiver’s characteristics and behaviors, as well as how these might affect the treatment as well as the formation of alliances. The result is linked to SOC, as several opportunities to increase the patient’s sense of meaningfulness, comprehensibility and manageability are described. Conclusions There is no unequivocal factor which improves anorexia nervosa treatment, rather a number of interacting factors in the treatment. With more extensive knowledge of these factors, the caregiver can more successfully support patients in their recovery.

Bakgrund: Sjuksköterskor möter dagligen anhöriga till patienter i livets slutskede. Bemötandet är centralt i omvårdnaden och påverkar vårdupplevelsen. Varje person ska bemötas som en individ vilket kan vara utmanande. Eftersom sjuksköterskor ses som omvårdnadsexperter är det väsentligt att lyfta sjuksköterskors erfarenhet av att bemöta anhöriga. Syfte: Att beskriva sjuksköterskors erfarenheter av att bemöta anhöriga till patienter i livets slutskede. Metod: En systematisk litteraturstudie med beskrivande syntes och analys utifrån kvalitativ ansats. Resultat: Två teman. I temat Skapandet av en god relation hittades subteman: ”Att erbjuda stöd och involvering i vårdandet” samt ”Att ha en god kommunikation”. Finnas som psykologiskt stöd, att se varje individ och förbereda anhöriga för dödsfallet belystes. Kommunikation beskrevs central. Bristande kommunikation kunde leda till obehagliga situationer. I temat Professionella utmaningar framkom subteman: ”Att involveras känslomässigt” samt ”Att känna sig otillräcklig”. Det var psykiskt påfrestande att vårda palliativt, erfarenheten ledde till personlig och professionell utveckling. Sjuksköterskorna uttryckte utmaning att hantera sörjande anhöriga och behov av utbildning. Slutsats: Anhöriga involverades i vården och sjuksköterskorna belyste vikten av pålitlighet och kommunikation. Sjuksköterskorna blev ibland konfliktlösare. Maktlöshet, frustration och sorg beskrevs men att vårda palliativt var ett privilegium. / Background: Nurses meet relatives of patients in end-of-life care daily. The treatment’s central to nursing and affects the care-experience. Each person must be treated as an individual, which can be challenging. Since nurses are nursing experts, it’s essential to highlight nurses’ experience with relatives. Aim: To describe nurses' experiences of treating relatives of patients in end-of-life care. Method: A systematic literature study with a descriptive data synthesis. Result: The theme Creating a good relationship, found two sub-themes: “Offering support and involvement in care” and “The importance of communication”. Being a psychological support, seeing every individual and preparing relatives for the coming death was highlighted. Communication was described centrally as lack of communication could lead to unpleasant situations. The theme Professional challenges emerged two sub-themes: “Being emotionally involved” and “Feeling inadequate”. It was psychologically stressful to work in palliative care, but the experience led to personal and professional development. It was challenging to handle grieving relatives and nurses needed further education. Conclusion: The nurses involved relatives in the care and highlighted the importance of reliability and straightforward communication. Powerlessness, frustration and grief was described but also a privilege to provide palliative care.

Bakgrund: I världen insjuknar cirka 10 miljoner människor årligen i demenssjukdom. Demenssjukdom orsakar en gradvis försämring av den kognitiva förmågan och medför behov som kan vara svåra att möta. Personcentrerad vård syftar till att göra personen delaktig i vårdandet och det innebär att ta del av personens livsberättelse, intressen och värderingar. Inom demensvården bör utgångspunkten vara personcentrerad och enligt lag har vårdpersonal en skyldighet att vård ska ges med respekt för människors lika värde. Personer med demenssjukdom och anhöriga beskriver betydelsen av personcentrerad vård och omständigheter som försvårar tillämpningen av personcentrerad vård som arbetssätt. Syfte: Att beskriva vårdpersonals erfarenheter av personcentrerad vård i vårdandet av personer med demenssjukdom. Metod: En systematisk litteraturstudie med kvalitativ ansats. Resultat: Två teman och fem underteman framkom. Tema: Betydelsen av att lära känna personen bakom sjukdomen med undertema: att skapa en relation, att ta del av livsberättelsen och att se individen. Tema: Omständigheter som försvårar personcentrerad vård med undertema: att sakna möjligheter och att sakna kunskap. Slutsats: Vårdpersonalen beskrev betydelsen av att lära känna personen bakom sjukdomen genom att tillämpa personcentrerad vård som arbetssätt. De beskrev även försvårande omständigheter som påverkar tillämpningen av personcentrerad vård i vårdandet av personer med demenssjukdom. / Background: Every year becomes around 10 million people in the world affected by dementia. Dementia causes a gradual deterioration of cognitive ability which causes needs that can be difficult to meet. Person-centered care aims to make the person involved and that means taking part of the person's life story, interests, and values. The starting point in dementia care should be person-centered. According to law, healthcare personnel have an obligation that care should be given with respect for people's equal value. People with dementia and relatives describe the importance of person-centered care and circumstances that make the application of person-centered care more difficult. Aim: To describe the experiences of caregivers in person-centered care in the care of people with dementia. Method: A systematic literature study with a qualitative approach. Results: Two themes and five subthemes emerged. Theme: The importance of getting to know the person behind the disease with subthemes: to create a relationship, to share the life story and to see the individual. Theme: Circumstances that make it more difficult for person-centered care with subthemes: to lack opportunities and to lack knowledge. Conclusion: Caregivers described that person-centered care is important for getting to know the person behind the disease by applying person-centered care as a way of working. They also described aggravating circumstances that affect the application of person-centered care of people with dementia.