Workshops on Software Visualization, Evolution and Maintenance最新文献

ConCAD: A Tool for Interactive Detection of Code Anomalies 代码异常的交互式检测工具

Workshops on Software Visualization, Evolution and Maintenance Pub Date : 2022-10-03 DOI: 10.5753/vem.2022.226597

D. Albuquerque, Everton T. Guimarães, M. Perkusich, H. Almeida, A. Perkusich

引用次数: 4

Using Controllers to Adapt Messaging Systems: An Initial Experience 使用控制器调整消息传递系统:初步经验

Workshops on Software Visualization, Evolution and Maintenance Pub Date : 2022-10-03 DOI: 10.5753/vem.2022.226809

N. Rosa, D. Cavalcanti

引用次数: 0

Democracia em Xeque: Um Estudo Comparativo sobre Detecção de Code Smells 民主的挑战:代码气味检测的比较研究

Workshops on Software Visualization, Evolution and Maintenance Pub Date : 2022-10-03 DOI: 10.5753/vem.2022.226562

Henrique Gomes Nunes, Lucas Francisco da Matta Vegi, Victor Pezzi Gazzinelli Cruz, Eduardo Figueiredo

引用次数: 0

Divinator: A Visual Studio Code Extension to Source Code Summarization Divinator:一个Visual Studio代码扩展到源代码摘要

Workshops on Software Visualization, Evolution and Maintenance Pub Date : 2022-10-03 DOI: 10.5753/vem.2022.226187

R. Durelli, Vinicius H. S. Durelli, R. W. Bettio, D. Dias, Alfredo Goldman

引用次数: 0

Como os mantenedores usam GitHub Reactions? Um estudo exploratório 维护人员如何使用GitHub Reactions?探索性研究

Workshops on Software Visualization, Evolution and Maintenance Pub Date : 2022-10-03 DOI: 10.5753/vem.2022.226591

P. Novais, A. Fontão, Hudson Silva Borges, M. Valente

引用次数: 0

Merge Nature: a tool to support research about merge conflicts 合并性质:一个支持合并冲突研究的工具

Workshops on Software Visualization, Evolution and Maintenance Pub Date : 2022-10-03 DOI: 10.5753/vem.2022.226216

Luan Reis Ciribelli, João Pedro Lima, H. S. C. Campos Junior, M. Barros, A. van der Hoek, Leonardo Gresta Paulino Murta, Gleiph Ghiotto

{"title":"Merge Nature: a tool to support research about merge conflicts","authors":"Luan Reis Ciribelli, João Pedro Lima, H. S. C. Campos Junior, M. Barros, A. van der Hoek, Leonardo Gresta Paulino Murta, Gleiph Ghiotto","doi":"10.5753/vem.2022.226216","DOIUrl":"https://doi.org/10.5753/vem.2022.226216","url":null,"abstract":"The modern software development model requires concurrent programming to create more complex programs. As such, existing approaches are able to track and merge the changes made on a code repository, allowing more developers to work collaboratively. Despite these solutions, 10% to 20% of all merges result in conflicts, such as when changes are made on the same file region. Existing studies have analyzed, prevented, predicted, and even automatically resolved merge conflicts. However, they are usually focused on a specific language or on language-independent information from the source-code lines involved in the conflict. This situation hinders the generalization of results. To enrich the information to be used by further studies about merges, we present the Merge Nature Tool, which recreates all project merges and extracts characteristics from conflicts, such as the resolutions adopted by developers, and the language constructs involved in the conflict for Java, C++, and Python files. The tool was evaluated regarding reproducibility and generalization. It was able to reproduce 87.75% of the results of a previous study. The differences can be explained by newly introduced features. On the other hand, regarding generalization, the tool was used to analyze a set of 100 merges from Python projects. The merges were analyzed manually to ensure the reliability of the results. We found that 100% of the data matched the expected result. We expect this tool to facilitate future work regarding merge conflicts. For instance, it may allow comparing the characteristics of merge conflicts from different programming languages.","PeriodicalId":308044,"journal":{"name":"Workshops on Software Visualization, Evolution and Maintenance","volume":"15 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-10-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126421777","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 0

Entendendo o engajamento das comunidades front-end e back-end nos repositórios do GitHub endenddo to engage to das通信的前端和后端nos repositórios do GitHub

Workshops on Software Visualization, Evolution and Maintenance Pub Date : 2022-10-03 DOI: 10.5753/vem.2022.226593

Altino Alves Júnior, Letícia Meireles, Lucas Alves Rossi Figueira, Vítor Marcondes Morais Carmo, H. T. Marques-Neto, Laerte Xavier

引用次数: 0

Avaliação de Ferramentas de Identificação de Dívida Técnica Auto-Admitida 评估自我承认的技术债务识别工具

Workshops on Software Visualization, Evolution and Maintenance Pub Date : 2022-10-03 DOI: 10.5753/vem.2022.226565

T. B. S. Gomes, Diogo Alves de Moura Loiola, Alcemir Rodrigues Santos

{"title":"Avaliação de Ferramentas de Identificação de Dívida Técnica Auto-Admitida","authors":"T. B. S. Gomes, Diogo Alves de Moura Loiola, Alcemir Rodrigues Santos","doi":"10.5753/vem.2022.226565","DOIUrl":"https://doi.org/10.5753/vem.2022.226565","url":null,"abstract":"Gerenciar dívidas técnicas em um projeto é primordial para saúde de projetos de software. A identificação delas, no entanto, não é trivial. Sejam elas, auto-admitidas ou não, existem diversas ferramentas que se propõem a identificá-las na literatura. No entanto, poucos estudos se propuseram a avaliar a intersecção entre suas abordagens. Neste artigo comparamos os resultados obtidos com duas ferramentas de identificação de dívidas técnicas auto-admitidas que utilizam mineração de comentários de código-fonte: eXcomment e DebtHunter. Utilizamos as ferramentas em quatro sistemas de código-aberto e comparamos manualmente a intersecção e a distribuição da classificação dos itens de dívida de cada uma das ferramentas. Verificou-se que dos itens classificados por eXcomment, 7% deles DebtHunter também classifica como dívida e que, dos itens que DebtHunter classifica como dívida, 19, 9% deles eXcomment também classifica. Além disso, apesar de divergirem quanto à quantidade de itens de dívida técnica, as ferramentas parecem convergir quanto aos tipos de dívida presentes nos sistemas avaliados.","PeriodicalId":308044,"journal":{"name":"Workshops on Software Visualization, Evolution and Maintenance","volume":"728 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-10-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134207780","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 0

Empirical investigation of the influence of continuous integration bad practices on software quality 持续集成不良实践对软件质量影响的实证研究

Workshops on Software Visualization, Evolution and Maintenance Pub Date : 2022-10-03 DOI: 10.5753/vem.2022.226816

Ruben Blenicio Tavares Silva, C. Bezerra

{"title":"Empirical investigation of the influence of continuous integration bad practices on software quality","authors":"Ruben Blenicio Tavares Silva, C. Bezerra","doi":"10.5753/vem.2022.226816","DOIUrl":"https://doi.org/10.5753/vem.2022.226816","url":null,"abstract":"Continuous Integration (CI) is a powerful tool to leverage software development in a safe, reliable, and efficient way. However, in day-to-day of software development, bad habits can arise in working with CI, which can make CI not reach its full potential in projects. These bad habits we call CI bad practices. This paper presented an exploratory study on closed-source projects to investigate how CI bad practices can affect software quality. We observe (1) the impact on the quality internal attributes after the implantation of CI, (2) the evolution of software quality indicators over time, and (3) the bad practices considered most harmful to the software quality by the development teams. Our results mean that projects affected by CI bad practices will not necessarily have their quality impaired. However, this does not mean that quality will be maintained or improved over time. Our analysis of the quality indicators has allowed us to observe that, generally, they have remained stable, and the number of quality issues reported has not decreased considerably either. Finally, the quality indicator most affected by the CI bad practices was maintainability, followed by reliability and security. In addition, the vast majority of the bad practices analyzed were classified as having a medium level of effort for resolution. In this sense, we also classify bad practices according to the level of effort/impact on the quality that can help prioritize their resolution.","PeriodicalId":308044,"journal":{"name":"Workshops on Software Visualization, Evolution and Maintenance","volume":"17 1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-10-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125716806","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 0

Exploring Pull Requests in Code Samples 在代码示例中探索拉请求

Workshops on Software Visualization, Evolution and Maintenance Pub Date : 2022-10-03 DOI: 10.5753/vem.2022.226789

Matheus Melo, Gabriel Menezes, B. Cafeo

引用次数: 0