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

Developing and maintaining software is a difficult task, and finding effective methods of understanding software is more necessary now than ever with the last few decades seeing a dramatic climb in the scale of software. Appropriate visualisations may enable greater understanding of the datasets we deal with in software engineering. As an aid for sense-making, visualisation is widely used in daily life (through graphics such as weather maps and road signs), as well as in other research domains, and is thought to be exceedingly beneficial. Unfortunately, there has not been widespread use of the multitude of techniques which have proposed for the software engineering domain. Tag clouds are a simple, text-based visualisation commonly found on the internet. Typically, implementations of tag clouds have not included rich interactive features which are necessary for data exploration. In this thesis, I introduce design considerations and a task set for enabling interaction in a tag cloud visualisation system. These considerations are based on an analysis of challenges in visualising software engineering data, and the perceptive influences of visual properties available in tag clouds. The design and implementation of interactive system Taggle based on these considerations is also presented, along with its broad-based evaluation. Evaluation approaches were informed by a systematic mapping study of previous tag cloud evaluation, providing an overview of existing research in the domain. The design of Taggle was improved following a heuristic evaluation by domain experts. Subsequent evaluations were divided into two parts - experiments focused on the tag cloud visualisation technique itself, and a task-based approach focused on the whole interactive system. As evidenced in the series of evaluative studies, the enhanced tag cloud features incorporated into Taggle enabled faster visual search response time, and the system could be used with minimal training to discover relevant information about an unknown software engineering dataset.

Developing and maintaining software is a difficult task, and finding effective methods of understanding software is more necessary now than ever with the last few decades seeing a dramatic climb in the scale of software. Appropriate visualisations may enable greater understanding of the datasets we deal with in software engineering. As an aid for sense-making, visualisation is widely used in daily life (through graphics such as weather maps and road signs), as well as in other research domains, and is thought to be exceedingly beneficial. Unfortunately, there has not been widespread use of the multitude of techniques which have proposed for the software engineering domain. Tag clouds are a simple, text-based visualisation commonly found on the internet. Typically, implementations of tag clouds have not included rich interactive features which are necessary for data exploration. In this thesis, I introduce design considerations and a task set for enabling interaction in a tag cloud visualisation system. These considerations are based on an analysis of challenges in visualising software engineering data, and the perceptive influences of visual properties available in tag clouds. The design and implementation of interactive system Taggle based on these considerations is also presented, along with its broad-based evaluation. Evaluation approaches were informed by a systematic mapping study of previous tag cloud evaluation, providing an overview of existing research in the domain. The design of Taggle was improved following a heuristic evaluation by domain experts. Subsequent evaluations were divided into two parts - experiments focused on the tag cloud visualisation technique itself, and a task-based approach focused on the whole interactive system. As evidenced in the series of evaluative studies, the enhanced tag cloud features incorporated into Taggle enabled faster visual search response time, and the system could be used with minimal training to discover relevant information about an unknown software engineering dataset.

As software engineering is a socio-technical research field, there is a myriad of research strategies and data sources that researchers need to consider when designing their studies. These choices determine different tradeoffs in terms of generalizability, realism, and control, among other aspects of research quality. It is not possible to create a perfect study, so these strengths and weaknesses are acceptable at the study level; however, when a research community's collective body of work suffers from an imbalance in these tradeoffs it can negatively impact overall research quality. Through this thesis, I investigate the research strategies and data sources that are used by the software engineering research community, and reflect on how this may affect aspects of research quality in our collective body of work. I apply Runkel and McGrath's models of research strategies and data sources to the software engineering domain through a systematic mapping study of three years of International Conference on Software Engineering (ICSE) proceedings and a mixed-methods survey of the authors of these papers. I found that a majority of papers report computational studies relying on trace measures rather than active human participation, showing an imbalance where generalizability and realism are prioritized over control. Through my survey, I confirmed that researcher participants explicitly prioritized realism and generalizability over control, impacting their research design choices. This imbalance in prioritization has the potential to lead to a collective failure to control for extraneous factors in the measurement of human behavior in software development, and without understanding what causes the behaviors we measure, we cannot fully understand why certain approaches and techniques work better than others, thus slowing our ability to advance as a research domain. Therefore, I present a call to action for the community to critically examine and discuss the issues raised by this research, and implement changes to increase the quality and diversity of our future work as a community. / Graduate / 2019-08-08

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-04-07T13:22:15Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) AnselmoLacerdaGomesCInMsc (19-11-2015).pdf: 2341760 bytes, checksum: 06c1abb20d748a6921088b434a7b7cb3 (MD5) / Made available in DSpace on 2016-04-07T13:22:15Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) AnselmoLacerdaGomesCInMsc (19-11-2015).pdf: 2341760 bytes, checksum: 06c1abb20d748a6921088b434a7b7cb3 (MD5) Previous issue date: 2015-08-31 / O Roubo de Identidade Digital (RID) é o roubo de informações que resulta na possibilidade de alguém assumir a identidade da vítima. Em decorrência disso, credenciais de acesso e dados dispostos em qualquer meio eletrônico ficam vulneráveis, como em computadores e em dispositivos móveis. Ultimamente, esses dispositivos têm sido bastante visados pelos atacantes, devido à sensibilidade e pessoalidade dos dados nele armazenados. Senhas, informações bancárias, financeiras e de geolocalização são apenas alguns exemplos de dados expostos a essa vulnerabilidade moderna. O RID é uma prática que pode resultar no êxito de diversos outros crimes associados, por exemplo, estelionato, espionagem, ciberterrorismo e ciberguerra. Suas implicações são sérias, já que o atacante pode assumir o controle de instalações industriais, centros militares, governos e organizações inteiras, sendo imprevisíveis os danos à ordem pública e aos cidadãos. Neste trabalho foi utilizada a metodologia de mapeamento sistemático para identificar quais são os principais incidentes de segurança associados ao RID. Relações e relativizações foram realizadas a fim de mapear as suas principais causas e consequências. A principal contribuição desta dissertação é o mapeamento sistemático de RID. Finalmente, esta dissertação de mestrado objetivou delinear o conhecimento sobre o assunto, de forma atualizada, indicando diretrizes para a minimização ou completa prevenção de incidentes dessa natureza. / The Digital Identity Theft (DIT) is the stealing of information that allows the attacker to take the victim’s identity, somehow. This promotes the access to credentials and data disposed in computers, mobile devices or any electronic environment, making them vulnerable. Recently, mobile devices are being very targeted because of the sensibility and personality of the data found there. Passwords, bank, financial and geolocation information are just some examples of data being exposed by this modern vulnerability. DIT is a practice that may result in the success of many other associated crimes, like embezzlement, espionage, cyberterrorism and cyberwar. Its implications are serious because the attacker can assume the control of industrial facilities, military centres, government and entire organizations, damaging the public order and the people to an unpredictable extent. This work used the systematic mapping methodology to identify which are the main security incidents related to DIT. Relations and relativizations were performed to map its main causes and consequences. Finally, this dissertation aimed to delineate the knowledge on the subject, indicating guidelines to minimize or avoid entirely incidents with this nature.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-06-29T12:16:01Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação - vbc.pdf: 3425848 bytes, checksum: 8e244d83612f4d849475c13a6af455d4 (MD5) / Made available in DSpace on 2016-06-29T12:16:01Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação - vbc.pdf: 3425848 bytes, checksum: 8e244d83612f4d849475c13a6af455d4 (MD5) Previous issue date: 2014-09-01 / A aplicação de Análise de Redes Sociais (SNA – Social Network Analysis) em times de projetos de software tem sido um tópico de pesquisa bastante explorado e usado na última década. A fim de entender as relações entre pessoas, grupos, organizações ou outros tipos de entidades sociais, por meio de grafos e métricas próprias, SNA aparece como uma alternativa para expandir a visão da dinâmica de projetos no campo das relações sociais. Visualizando um projeto representado por um grafo, as entidades sociais são representadas como nós e suas relações como arestas, e análises temporais e/ou atemporais sobre aspectos de projetos, como comunicação, formação de equipe, colaboração, entre outros, podem ser realizadas usando métricas próprias como por exemplo betweenness centrality e densidade. O tipo de projeto mais estudado por pesquisadores que usam Análise de Redes Sociais é o projeto de desenvolvimento de software open source (OSS – Open Source Software). Pela facilidade na obtenção dos dados, armazenados em repositórios online, esta categoria de projeto tem levantado a curiosidade da comunidade acadêmica a fim de investigar suas características. OSS se distingue dos projetos tradicionais (chamados de closed source) pois envolve a participação de vários integrantes de forma espontânea, geralmente de localidade distintas e que nunca tiveram um contato pessoal entre si. Tendo em vista a extensão, em quantidade, de pesquisas que combinam o uso de técnicas de SNA em projetos OSS, esta dissertação tem como objetivo, através de um mapeamento sistemático da literatura, mapear e categorizar estudos diretamente relacionados à análise de redes sociais em projetos de software open source. Por meio de estatística descritiva e análise qualitativa busca-se conhecer quais os principais benefícios e limitações encontrados na aplicação das métricas de análise de redes sociais nos projetos de software OSS, bem como os principais tópicos de pesquisa e fontes de dados utilizadas. O trabalho, em sua síntese, apresenta um diagnóstico da pesquisa atual sobre os temas abordados e colabora com a academia apontando tendências e trabalhos futuros. / The application of Social Network Analysis (SNA) in teams of software projects has been a well researched and used topic in the last decade. In order to understand the relation between people, groups, organizations and other social entities, by the use of its own graphs and metrics, SNA appears to be an alternative to expand the vision of the projects dynamics in the social relation field. Seeing a project represented in a graph, the social entities are represented as dots and its relations as edges, and the temporal and/or timeless analysis about the projects aspects, such as communication, team building, coworking and others, can be performed by the use of own metrics, e.g. betweenness centrality and density. The kind of project most studied by researchers that use Social Network Analysis is the open source (OSS – Open Source Software) software development. This project category has been raising the academic community curiosity to investigate its characteristics since it is easy to obtain the data, stored in online repositories. OSS distinguishes from traditional projects (called closed source) because involves the participation of many spontaneous member, usually from different location and that have never met. As there are many researches that combine the use of SNA techniques in OSS projects, this thesis has the purpose to map and categorize, through a systematic mapping of the literature, studies directly related to the analysis of social network in open source software projects. Using descriptive statistics and qualitative analysis, seeks the main benefits and limitations found on the application of social network analysis metrics in the OSS software projects, as well as the main research topics and the used data source. To sum up, this dissertation presents a diagnose of the research about the covered topics and collaborates with the academy pointing tendencies and future work.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-07-01T11:40:55Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) dissertacao biblioteca revisado.pdf: 2828757 bytes, checksum: 94e8f0f95ebbe83536b00d9b18b31d8c (MD5) / Made available in DSpace on 2016-07-01T11:40:55Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) dissertacao biblioteca revisado.pdf: 2828757 bytes, checksum: 94e8f0f95ebbe83536b00d9b18b31d8c (MD5) Previous issue date: 2015-08-19 / Nos últimos anos, percebe-se um interesse crescente na utilização de metodologias ágeis como estratégia para minimizar os problemas no desenvolvimento de software. Apesar disso, pouco ainda se sabe sobre como a engenharia de requisitos está sendo conduzida em conjunto com essas metodologias. Neste contexto, o objetivo desta pesquisa é investigar como a engenharia de requisitos e as metodologias ágeis vêm sendo utilizadas conjuntamente na prática em projetos de desenvolvimento de software aplicados na indústria. Para isso, foi realizado um mapeamento sistemático da literatura que encontrou 24 estudos primários relevantes, cujos dados foram extraídos e sintetizados. Esse mapeamento identificou as técnicas e processos de engenharia de requisitos que estão sendo mais utilizados no contexto de desenvolvimento ágil e quais os principais problemas e limitações encontradas. Após a execução do mapeamento, verificou-se que a falta de envolvimento do usuário associada às características das atuais técnicas utilizadas para especificar requisitos e suas constantes mudanças são os principais desafios a serem superados. / In recent years, we can see a growing interest in using agile methodologies as a strategy to minimize the problems in software development. Nevertheless, little is known as requirements engineering is being conducted in conjunction with these methodologies. In this context, the objective of this research is to investigate how the requirements engineering and agile methodologies have been used jointly in practice in software development projects applied in the industry. For this, it was conducted a systematic literature mapping that found 24 relevant primary studies, whose data were extracted and synthesized. This mapping identified the most used techniques and process of requirements engineering and what are the main problems and limitations encountered in the context of agile development. After the execution of the mapping, it was found that lack of user involvement associated with the characteristics of current techniques used to specify requirements and their constant changes are the main challenges to overcome.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2017-04-25T12:15:54Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) RASTREABILIDADE ENTRE ARTEFATOS HETEROGÊNEOS DE SOFTWARE - UM MAPEAMENTO SISTEMATICO.pdf: 1372647 bytes, checksum: 04d06da9110f40f9124df63fa92629a6 (MD5) / Made available in DSpace on 2017-04-25T12:15:54Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) RASTREABILIDADE ENTRE ARTEFATOS HETEROGÊNEOS DE SOFTWARE - UM MAPEAMENTO SISTEMATICO.pdf: 1372647 bytes, checksum: 04d06da9110f40f9124df63fa92629a6 (MD5) Previous issue date: 2016-08-26 / Rastreabilidade de artefatos de software tem sido reconhecida como um fator importante para apoiar diversas atividades no processo de desenvolvimento de software. Em geral, o objetivo da rastreabilidade é melhorar a qualidade dos sistemas de software. Ao longo dos últimos anos, as comunidades de engenharia de software têm desenvolvido um grande número de abordagens e técnicas para tratar vários aspectos da rastreabilidade. No entanto, apesar de sua importância e o trabalho resultante de vários anos de pesquisa, estudos empíricos sobre as necessidades e práticas de rastreabilidade em organizações industriais indicam que o suporte a rastreabilidade não é sempre satisfatório. Como resultado, a rastreabilidade é raramente estabelecida nos ambientes industriais existentes, devido a apresentar características distribuídas e heterogêneas. Apesar do amplo reconhecimento de sua importância e de numerosos anos de investigação, até o momento nenhum estudo apresentou uma visão holística dos estudos empíricos que aplicam a rastreabilidade de software, na indústria ou na academia. Como um primeiro esforço neste sentido, o objetivo deste estudo é apresentar um roteiro de investigação das práticas relacionadas à rastreabilidade de software entre artefatos heterogêneos e identificar as questões que ainda estão abertas para novas pesquisas. Através de um Mapeamento Sistemático da Literatura realizado por um único pesquisador os relatos de experimentos foram identificados e caracterizados. Cinco questões de pesquisa foram utilizadas para extrair e sintetizar as evidências encontradas nos estudos empíricos publicados nas diversas fontes científicas da área. Dos 2488 estudos retornados, 37 foram selecionados por atender aos critérios de seleção especificados. Após análise, conclui-se que a eficácia das estratégias de rastreabilidade estabelecidas ainda é muito pontual é pouco eficaz, este fenômeno pode ser atribuído à dificuldade em automatizar a geração das relações de rastreabilidade com semânticas claras e precisas. Tipicamente, na maior parte das abordagens existentes, as relações de rastreabilidade são identificadas de forma automatizada, através da utilização de técnicas de recuperação de informação estabelecidas sobre um conjunto de artefatos de software relacionados aos requisitos, análise e projeto, implementação e testes. Em relação aos principais desafios relatados quanto às práticas estabelecidas foram à confiança e a escalabilidade das abordagens. / Software artifacts Traceability has been recognized as an important factor to support various activities in the software development process. In general, the purpose of tracking is to improve the quality of software systems. Over the past few years, software engineering of communities have developed a number of approaches and techniques for treating various aspects of traceability. However, despite its importance and the resulting work of several years of research, empirical studies on the needs and traceability practices in industrial organizations indicate that support traceability is not always satisfactory. As a result, traceability is rarely established in existing industrial environments due to present distributed and heterogeneous characteristics. Despite the widespread recognition of its importance and many years of research, to date no study has a holistic view of empirical studies that apply to software traceability, industry or academia. As a first effort in this direction, the objective of this study is to present a roadmap for research into the practices related to traceability software across heterogeneous devices and identify the issues that are still open for further research. Through a Systematic Literature mapping performed by a single researcher, experiments reports were identified and characterized. Five research questions were used to extract and synthesize the evidence found in empirical studies published in various scientific sources the area. From 2488 returned studies, 37 were selected for meeting the specified selection criteria. After analysis, it is concluded that the effectiveness of the established traceability strategies is still very punctual is very effective, this phenomenon can be attributed to the difficulty in automating the generation of traceability relationships with clear and precise semantics. Typically, in most existing approaches, the traceability relationships are identified in an automated manner through the use of established information retrieval technique on artifacts level requirements, analysis and design, implementation and testing. However, the main challenges reported when the established practice is, trust and scalability.

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