Context: Unified Modeling Language (UML) is a universal and standard modeling language that has been extensively used in software development process. Due to overlap and synchronous nature among different modeling artefacts in UML, several consistency issues have been identified in many software development projects that may lead to project failure. To reduce the level of such threat, over the past decade, a substantial research addressing those problems has been done both in academic and industry. This study is intended to investigate the reported research and to provide a systematic picture on different researched aspects of UML model inconsistencies, using the systematic mapping method. Objectives: The overall goal was to be achieved by fulfilling the following two main objectives: elaborating a proper and justified tool for performing the mapping and later used the tool in order to obtain a systematic and multidimensional picture of the approaches and the performed research in the area relating to different issues considering inconsistencies when using UML in software development. Research Methods: In order to ensure quality of the final foreseen systematic picture of the conducted research, a considerable effort was put first on a preparation of the tool that was used to obtain the mapping. The tool was a rigorous process based on classification methods and mapping guidelines obtained from a systematic literature review on the systematic mapping in software engineering. Then the tool was applied in a systematic way to obtain a number of mappings, followed by the analysis of the obtained results. Results: The systematic literature review resulted in identifying 5 mapping guidelines, 21 classifications, and 2 categorization methods. After analysis of them, a justified mapping process was developed by selecting standard guidelines, appropriate classifications and categorization methods. The mapping process applied for the period of 1999-2012 revealed 198 relevant studies developed by 321 researchers. On the basis this evidences, a number of mappings illustrating the conducted research on UML model inconsistencies ware obtained. The mapping reviled that the published research is mostly focused on rather formal issues such as semantic, syntactic, intramodel, inter-model and evolution problems, while a less attention is placed on more practical on time, and security problems. When the quality of research is concerned, 38% of papers proposed solutions as well as validated them through academic, industry or both, 35% of papers proposed only solutions. When the usage of empirical methods is considered, case studies are most frequently used (in almost half of the relevant papers) and followed by experiments (reported in 15% of papers), while 25% carried works do on report a systematic method used. Conclusions: The findings of systematic mapping study revealed that there are some aspect related to consistency such as time and security that are not given big attention. Identification and in-depth studying of inconsistencies in UML designs along with their dependencies are also missing. Most of the investigations are also academic with no evidence whether these reports produce interest for industry or not. State-of-the-art followed by state-of-the-practice studies related to consistency checking techniques and validating them in real industrial setting could be recommended. / Context: Unified Modeling Language (UML) is a universal and standard modeling language that has been extensively used in software development process. Due to overlap and synchronous nature among different modeling artefacts in UML, several consistency issues have been identified in many software development projects that may lead to project failure. To reduce the level of such threat, over the past decade, a substantial research addressing those problems has been done both in academic and industry. This study is intended to investigate the reported research and to provide a systematic picture on different researched aspects of UML model inconsistencies, using the systematic mapping method. Objectives: The overall goal was to be achieved by fulfilling the following two main objectives: elaborating a proper and justified tool for performing the mapping and later used the tool in order to obtain a systematic and multidimensional picture of the approaches and the performed research in the area relating to different issues considering inconsistencies when using UML in software development. Research Methods: In order to ensure quality of the final foreseen systematic picture of the conducted research, a considerable effort was put first on a preparation of the tool that was used to obtain the mapping. The tool was a rigorous process based on classification methods and mapping guidelines obtained from a systematic literature review on the systematic mapping in software engineering. Then the tool was applied in a systematic way to obtain a number of mappings, followed by the analysis of the obtained results. Results: The systematic literature review resulted in identifying 5 mapping guidelines, 21 classifications, and 2 categorization methods. After analysis of them, a justified mapping process was developed by selecting standard guidelines, appropriate classifications and categorization methods. The mapping process applied for the period of 1999-2012 revealed 198 relevant studies developed by 321 researchers. On the basis this evidences, a number of mappings illustrating the conducted research on UML model inconsistencies ware obtained. The mapping reviled that the published research is mostly focused on rather formal issues such as semantic, syntactic, intramodel, inter-model and evolution problems, while a less attention is placed on more practical on time, and security problems. When the quality of research is concerned, 38% of papers proposed solutions as well as validated them through academic, industry or both, 35% of papers proposed only solutions. When the usage of empirical methods is considered, case studies are most frequently used (in almost half of the relevant papers) and followed by experiments (reported in 15% of papers), while 25% carried works do on report a systematic method used. Conclusions: The findings of systematic mapping study revealed that there are some aspect related to consistency such as time and security that are not given big attention. Identification and in-depth studying of inconsistencies in UML designs along with their dependencies are also missing. Most of the investigations are also academic with no evidence whether these reports produce interest for industry or not. State-of-the-art followed by state-of-the-practice studies related to consistency checking techniques and validating them in real industrial setting could be recommended.

Context: Unified Modeling Language (UML) is a universal and standard modeling language that has been extensively used in software development process. Due to overlap and synchronous nature among different modeling artefacts in UML, several consistency issues have been identified in many software development projects that may lead to project failure. To reduce the level of such threat, over the past decade, a substantial research addressing those problems has been done both in academic and industry. This study is intended to investigate the reported research and to provide a systematic picture on different researched aspects of UML model inconsistencies, using the systematic mapping method. Objectives: The overall goal was to be achieved by fulfilling the following two main objectives: elaborating a proper and justified tool for performing the mapping and later used the tool in order to obtain a systematic and multidimensional picture of the approaches and the performed research in the area relating to different issues considering inconsistencies when using UML in software development. Research Methods: In order to ensure quality of the final foreseen systematic picture of the conducted research, a considerable effort was put first on a preparation of the tool that was used to obtain the mapping. The tool was a rigorous process based on classification methods and mapping guidelines obtained from a systematic literature review on the systematic mapping in software engineering. Then the tool was applied in a systematic way to obtain a number of mappings, followed by the analysis of the obtained results. Results: The systematic literature review resulted in identifying 5 mapping guidelines, 21 classifications, and 2 categorization methods. After analysis of them, a justified mapping process was developed by selecting standard guidelines, appropriate classifications and categorization methods. The mapping process applied for the period of 1999-2012 revealed 198 relevant studies developed by 321 researchers. On the basis this evidences, a number of mappings illustrating the conducted research on UML model inconsistencies ware obtained. The mapping reviled that the published research is mostly focused on rather formal issues such as semantic, syntactic, intramodel, inter-model and evolution problems, while a less attention is placed on more practical on time, and security problems. When the quality of research is concerned, 38% of papers proposed solutions as well as validated them through academic, industry or both, 35% of papers proposed only solutions. When the usage of empirical methods is considered, case studies are most frequently used (in almost half of the relevant papers) and followed by experiments (reported in 15% of papers), while 25% carried works do on report a systematic method used. Conclusions: The findings of systematic mapping study revealed that there are some aspect related to consistency such as time and security that are not given big attention. Identification and in-depth studying of inconsistencies in UML designs along with their dependencies are also missing. Most of the investigations are also academic with no evidence whether these reports produce interest for industry or not. State-of-the-art followed by state-of-the-practice studies related to consistency checking techniques and validating them in real industrial setting could be recommended. / Context: Unified Modeling Language (UML) is a universal and standard modeling language that has been extensively used in software development process. Due to overlap and synchronous nature among different modeling artefacts in UML, several consistency issues have been identified in many software development projects that may lead to project failure. To reduce the level of such threat, over the past decade, a substantial research addressing those problems has been done both in academic and industry. This study is intended to investigate the reported research and to provide a systematic picture on different researched aspects of UML model inconsistencies, using the systematic mapping method. Objectives: The overall goal was to be achieved by fulfilling the following two main objectives: elaborating a proper and justified tool for performing the mapping and later used the tool in order to obtain a systematic and multidimensional picture of the approaches and the performed research in the area relating to different issues considering inconsistencies when using UML in software development. Research Methods: In order to ensure quality of the final foreseen systematic picture of the conducted research, a considerable effort was put first on a preparation of the tool that was used to obtain the mapping. The tool was a rigorous process based on classification methods and mapping guidelines obtained from a systematic literature review on the systematic mapping in software engineering. Then the tool was applied in a systematic way to obtain a number of mappings, followed by the analysis of the obtained results. Results: The systematic literature review resulted in identifying 5 mapping guidelines, 21 classifications, and 2 categorization methods. After analysis of them, a justified mapping process was developed by selecting standard guidelines, appropriate classifications and categorization methods. The mapping process applied for the period of 1999-2012 revealed 198 relevant studies developed by 321 researchers. On the basis this evidences, a number of mappings illustrating the conducted research on UML model inconsistencies ware obtained. The mapping reviled that the published research is mostly focused on rather formal issues such as semantic, syntactic, intramodel, inter-model and evolution problems, while a less attention is placed on more practical on time, and security problems. When the quality of research is concerned, 38% of papers proposed solutions as well as validated them through academic, industry or both, 35% of papers proposed only solutions. When the usage of empirical methods is considered, case studies are most frequently used (in almost half of the relevant papers) and followed by experiments (reported in 15% of papers), while 25% carried works do on report a systematic method used. Conclusions: The findings of systematic mapping study revealed that there are some aspect related to consistency such as time and security that are not given big attention. Identification and in-depth studying of inconsistencies in UML designs along with their dependencies are also missing. Most of the investigations are also academic with no evidence whether these reports produce interest for industry or not. State-of-the-art followed by state-of-the-practice studies related to consistency checking techniques and validating them in real industrial setting could be recommended. / C/o Thalanki Anjaneyulu, H.No.76/119-D5-43, Mahaveer Colony, B.G.Road, Kurnool -518003, Andhra Pradesh, India

No description available.

Unit testing is defined as a test activity usually performed by a developer for the purpose of demonstrating program functionality and meeting the requirements specification of module. Nowadays, unit testing is considered as an integral part in the software development cycle. However, performing unit testing by developers is still considered as a major concern because of the time and cost involved in it. Automation support for unit testing, in the form of various automation tools, could significantly lower the cost of performing unit testing phase as well as decrease the time developer involved in the actual testing. The problem is how to choose the most appropriate tool that will suit developer requirements consisting of cost involved, effort needed, level of automation provided, language support, etc. This research work presents results from a systematic literature review with the aim of finding all unit testing tools with an automation support. In the systematic literature review, we initially identified 1957 studies. After performing several removal stages, 112 primary studies were listed and 24 tools identified in total. Along with the list of tools, we also provide the categorization of all the tools found based on the programming language support, availability (License, Open source, Free), testing technique, level of effort required by developer to use tool, target domain, that we consider as good properties for a developer to make a decision on which tool to use. Additionally, we categorized type of error(s) found by some tools, which could be beneficial for a developer when looking at the tool’s effectiveness. The main intent of this report is to aid developers in the process of choosing an appropriate unit testing tool from categorization table of available tools with automation unit testing support that ease this process significantly. This work could be beneficial for researchers considering to evaluate efficiency and effectiveness of each tool and use this information to eventually build a new tool with the same properties as several others.

Bakgrund: Sjuksköterskan ansågs tidigare vara assistent till läkaren men har idag en egen profession med omvårdnadsansvar. Patienter och anhöriga vänder sig till sjuksköterskan för att få stöd och förtydligande av informationen som just mottagits av läkaren. Syfte: Att beskriva sjuksköterskans erfarenhet av ansvar efter att patient mottagit ett svårt besked i form av diagnosrelaterad information. Metod: Allmän litteraturöversikt enligt Friberg (2017) där nio artiklar med kvalitativ ansats, tre artiklar med kvantitativ ansats och två artiklar med mixad metod analyserats. Resultat: Sjuksköterskan vill ta ansvar då patienten fått svåra besked men kan uppleva sig utesluten genom bland annat bristande kommunikation med läkaren. Trots detta tar sjuksköterskan ansvar när patienten inte förstått beskedet och ser till att patienten får mer information och säkerställer att patienten förstår vad det innebär. Sjuksköterskan blir engagerad i relationen med patienten och kan själv bli emotionellt påverkad när patienten mottar svåra besked. Sjuksköterskor med längre erfarenhet i yrket upplever sig mer trygga i sitt ansvar då patienten mottagit svåra besked. Slutsats: Genom att synliggöra sjuksköterskans ansvar vid svåra besked och när sjuksköterskan är medveten om vad ansvaret innebär och får utrymme att ta ansvaret, minskar risken för att patienten blir övergiven i lidandet. / Background: The nurse has gone from being seen as an assistant to the doctor, to having their own profession with the main responsibility for nursing. Patients and their relatives turn to the nurse for comfort and more information after the doctor has delivered bad news. Aim: To describe nurses' experiences of responsibility after a patient receives bad news related to diagnosis. Method: A general literature review. Results: The nurse wants to take responsibility but due to lack of communication gets inhibited. Despite that the nurse take responsibility and makes sure that the patient gets more information when needed. The nurse also takes responsibility for the patient by being there for them with support. The nurse engages in the relationship with the patient and can therefore get emotionally affected by the bad news the patient receives. Nurses whom have more experience clearly feel more confident with the responsibility that occurs when the patient receives bad news. Conclusion: By highlighting the nurses' responsibilities it could be more valued in a broader perspective and when the nurse is aware of the responsibility for caring, it decreases the risk of abandonment for the patient.

In recent years, food waste has received growing interest from local, national and European policymakers, international organisations, NGOs as well as academics from various disciplinary fields. Increasing concerns about food security and environmental impacts, such as resource depletion and greenhouse gas emissions attributed to food waste, have intensified attention to the topic. While food waste occurs in all stages of the food supply chain, private households have been identified as key actors in food waste generation. However, the evidence on why food waste occurs remains scattered. This paper maps the still small but expanding academic territory of consumer food waste by systematically reviewing empirical studies on food waste practices as well as distilling factors that foster and impede the generation of food waste on the household level. Moreover, we briefly discuss the contributions of different social ontologies, more particularly psychology-related approaches and social practice theory. The analysis reveals food waste as a complex and multi-faceted issue that cannot be attributed to single variables; this also calls for a stronger integration of different disciplinary perspectives. Mapping the determinants of waste generation deepens the understanding of household practices and helps design food waste prevention strategies. Finally, we link the identified factors with a set of policy, business, and retailer options.

Bakgrund : Årligen drabbas ungefär 300 barn av cancer. När ett barn blir sjukt drabbas hela familjen, och därför är det viktigt att vårdpersonal förstår vilka behov av stöd familjen har, samt hur vårdpersonalen kan tillfredsställa dessa behov. Att arbeta familjecentrerat underlättar för vårdpersonalen att se dessa behov, och främjar familjens upplevelse av vården. Syfte : Syftet med denna litteraturöversikt var att undersöka familjens upplevelse av hur livet påverkas när ett barn drabbas av cancer, samt vilket stöd de anger att de behöver av vården. Metod : En litteraturöversikt som baseras på 16 vetenskapliga artiklar. Resultat : Resultatet visade att familjens upplevelser var individuella, men det fanns några karaktäristiska drag. De flesta föräldrarna upplevde chock vid diagnostillfället, och även känslan av skuld över att inte kunna göra något åt situationen. Vardagen förändrades kraftigt för familjen, där bland annat föräldrarna upplevde sig kraftlösa och syskonen kände sorg, både över diagnosen men även på grund av den nedsatta uppmärksamheten de fick av sina föräldrar. Familjen fick anpassa livet efter sjukdomen, där relationerna blev påverkade men även ekonomin. Faktorer som underlättade situationen för familjen var bland annat socialt stöd, och för de som var troende var tron ett stort stöd. Informationen föräldrarna fick angående sjukdomen och behandlingen av vårdpersonalen påverkade deras mående. Slutsats : Familjens upplevelse var känslomässigt omtumlande, känslorna var individuella men många kände bland annat chock och kaos. Familjens upplevelse var att allt vändes upp och ned. Behovet av stöd hos föräldrar och syskon skiljde sig åt. Syskon uppskattar stöd i form av uppmärksamhet och information om deras syskons sjukdom och behandling. Föräldrar vill ha stöd i form av information, att få vara delaktiga och att kunna prata med vårdpersonalen. / Background : Yearly, approximately 300 Swedish children is diagnosed with cancer. When a child gets ill the whole family is involved, and therefore it is important for health care personnel to understand what needs the family has and how to satisfy these needs. To work family-centred facilitates for the health care personnel to see these needs, and promotes the family's experience of care. Aim : The aim of this study was to examine the families’ perceptions of how life is affected when a child is diagnosed with cancer, and what support they indicate they need from healthcare professionals. Method : A review based on 16 scientific articles. Result : The result showed that family experiences were individual, but there were some characteristic features. Most parents experienced shock at the time of diagnosis, and also the feeling of guilt over being unable to do anything about the situation. Everyday life changed dramatically for the family. The parents had feelings like powerless and the siblings felt sadness, both over the diagnosis, but also because of the reduced attention they received from their parents. The family had to adapt life after the disease, where the relationships were affected, but also the economy. Factors that facilitated the situation of the family included social support, and for believers, faith was a great support. The information the parents received of healthcare professionals regarding the disease and the treatment of the sick child affected their way to handle the situation. Conclusion : The family's experience was emotionally turbulent, the feelings were individual, but many felt shock and chaos. The family's experience was that everything was turned upside down. The need for support from parents and siblings was different. Siblings appreciate support in terms of attention and information about their sibling's disease and treatment. Parents want support in the form of information, being involved and being able to talk with healthcare professionals.

Bakgrund: För att sjuksköterskor ska kunna tillhandahålla en god personcentrerad vård krävs ett empatiskt förhållningssätt, vilket kan äventyras om sjuksköterskorna drabbas av compassion fatigue. Compassion fatigue är ett relativt nybildat begrepp som handlar om ett tillstånd i form av att vara för trött för att bry sig samt behöva avstå från att bry sig för att skydda sig själv. Detta kan uppkomma hos sjuksköterskor till följd av att vårda svårt sjuka patienter. Inom vård och omsorg är det vanligt med långtidssjukskrivningar på grund av psykisk ohälsa. Syfte: Syftet med denna litteraturöversikt var att beskriva vilka faktorer som påverkar uppkomst av compassion fatigue hos sjuksköterskor samt även beskriva hur sjuksköterskor upplever att drabbas av compassion fatigue. Metod: En litteraturöversikt där resultatet är baserat på 16 artiklar. Resultat: Resultatet delades upp i två huvudkategorier: faktorer som påverkar uppkomst av compassion fatigue samt sjuksköterskors upplevelse av att drabbas av compassion fatigue. Dessa delades sedan upp i subkategorier där de olika faktorerna och upplevelserna presenterades. Slutsats: Sjuksköterskor och annan vårdpersonal samt studenter bör erbjudas utbildning för att bredda kunskapen om compassion fatigue. Det skulle kunna leda till ett lyckat preventivt arbete, vilket i sin tur skulle resultera i färre sjukskrivningar. / Background: For nurses to be able to provide a high quality personcentered care it takes an empathetic approach., which can be jeopardized as a consequence of compassion fatigue among nurses. Compassion fatigue is a relatively new term which is about a condition of being too tired to care and needing to abstain from caring to protect oneself. This condition can develop among nurses due to caring for critically ill patients. In healthcare it is common with long term sick leave from psychological illness. Aim: The purpose of this literature review was to describe the factors that can influence the occurance of compassion fatigue among nurses, and to further describe how nurses experience the suffering from compassion fatigue. Method: A literature review where the result is based on 16 articles. Result: The result was divided in to two major categories: factors that influence the occurance of compassion fatigue and nurses experiences of suffering from compassion fatigue. These were then divided in to subcategories where the factors and experiences were presented. Conclusion: Nurses, other healthcare providers and students should be offered education to widen their knowledge about compassion fatigue. This could lead to a successful preventive work, which in turn could result in less sick leaves.

Context: Static code analysis is a software verification technique that refers to the process of examining code without executing it in order to capture defects in the code early, avoiding later costly fixations. The lack of realistic empirical evaluations in software engineering has been identified as a major issue limiting the ability of research to impact industry and in turn preventing feedback from industry that can improve, guide and orient research. Studies emphasized rigor and relevance as important criteria to assess the quality and realism of research. The rigor defines how adequately a study has been carried out and reported, while relevance defines the potential impact of the study on industry. Despite the importance of static code analysis techniques and its existence for more than three decades, the number of empirical evaluations in this field are less in number and do not take into account the rigor and relevance into consideration. Objectives: The aim of this study is to contribute toward bridging the gap between static code analysis research and industry by improving the ability of research to impact industry and vice versa. This study has two main objectives. First, developing guidelines for researchers, which will explore the existing research work in static code analysis research to identify the current status, shortcomings, rigor and industrial relevance of the research, reported benefits/limitations of different static code analysis techniques, and finally, give recommendations to researchers to help improve the future research to make it more industrial oriented. Second, developing guidelines for practitioners, which will investigate the adoption of different static code analysis techniques in industry and identify benefits/limitations of these techniques as perceived by industrial professionals. Then cross-analyze the findings of the SLR and the surbvey to draw final conclusions, and finally, give recommendations to professionals to help them decide which techniques to adopt. Methods: A sequential exploratory strategy characterized by the collection and analysis of qualitative data (systematic literature review) followed by the collection and analysis of quantitative data (survey), has been used to conduct this research. In order to achieve the first objective, a thorough systematic literature review has been conducted using Kitchenham guidelines. To achieve the second study objective, a questionnaire-based online survey was conducted, targeting professionals from software industry in order to collect their responses regarding the usage of different static code analysis techniques, as well as their benefits and limitations. The quantitative data obtained was subjected to statistical analysis for the further interpretation of the data and draw results based on it. Results: In static code analysis research, inspection and static analysis tools received significantly more attention than the other techniques. The benefits and limitations of static code analysis techniques were extracted and seven recurrent variables were used to report them. The existing research work in static code analysis field significantly lacks rigor and relevance and the reason behind it has been identified. Somre recommendations are developed outlining how to improve static code analysis research and make it more industrial oriented. From the industrial point of view, static analysis tools are widely used followed by informal reviews, while inspections and walkthroughs are rarely used. The benefits and limitations of different static code analysis techniques, as perceived by industrial professionals, have been identified along with the influential factors. Conclusions: The SLR concluded that the techniques having a formal, well-defined process and process elements have receive more attention in research, however, this doesn’t necessarily mean that technique is better than the other techniques. The experiments have been used widely as a research method in static code analysis research, but the outcome variables in the majority of the experiments are inconsistent. The use of experiments in academic context contributed nothing to improve the relevance, while the inadequate reporting of validity threats and their mitigation strategies contributed significantly to poor rigor of research. The benefits and limitations of different static code analysis techniques identified by the SLR could not complement the survey findings, because the rigor and relevance of most of the studies reporting them was weak. The survey concluded that the adoption of static code analysis techniques in the industry is more influenced by the software life-cycle models in practice in organizations, while software product type and company size do not have much influence. The amount of attention a static code analysis technique has received in research doesn’t necessarily influence its adoption in industry which indicates a wide gap between research and industry. However, the company size, product type, and software life-cycle model do influence professionals perception on benefits and limitations of different static code analysis techniques.

This is a suggestive thesis that aims to investigate the potential within boredom literature to supplement explanations of interaction patterns with jihadist propaganda from the so-called Islamic State (IS). The media strategy of IS has benefited from a comprehensive narrative, and an inclusive approach to production and dissemination of propaganda, which has seen a heavy emphasis on the grass root participation within a loosely structured digital network. The thesis builds on the precept that boredom has been associated with lack of agency, meaning and excitement – three attributes that features prominently in IS propaganda. Through a scoping literature review of published articles on boredom, certain thematic elements was perceived to have an analytical potential with regards to the jihadist propaganda – including boredom proneness, boredom and meaning-seeking, boredom and excitement, and boredom’s relation to violent agency. The study showed a potential for boredom as a concept, via the respective theoretical and methodological frameworks, to broaden our understanding of the interaction with IS propaganda. By investigating boredom as a driving force in the interaction process, it is possible to highlight several aspects of how and why people relate positively to the propaganda – most importantly the connection between boredom and central human emotions, needs and characteristics.