sol-xml2xlsx.ipynb

{
 "cells": [
  {
   "cell_type": "code",
   "execution_count": 13,
   "metadata": {},
   "outputs": [],
   "source": [
    "import xml.sax\n",
    "import pandas as pd\n",
    "\n",
    "element = {}  # Stores the name and the attributes of the current element\n",
    "publication = {}  # Stores the publication under construction\n",
    "data = []\n",
    "\n",
    "class SOLHandler(xml.sax.ContentHandler):\n",
    "\n",
    "    def startElement(self, name, attrs):\n",
    "        global element\n",
    "        element = {\n",
    "            'name': name,\n",
    "            'attrs': attrs\n",
    "        }\n",
    "\n",
    "    def characters(self, content):\n",
    "        global element, publication\n",
    "\n",
    "        if element:\n",
    "            if element['name'] == 'dc:title' and (element['attrs'].getValue('xml:lang') == 'pt-BR'):\n",
    "                publication['title'] = content\n",
    "            elif element['name'] == 'dc:creator':\n",
    "                author = ' '.join(reversed(content.split(', ')))\n",
    "                publication['authors'] = f'{publication[\"authors\"]}; {author}' if 'authors' in publication else author\n",
    "            elif element['name'] == 'dc:date':\n",
    "                publication['year'] = int(content[0:4])\n",
    "\n",
    "    def endElement(self, name):\n",
    "        global element, publication, data\n",
    "\n",
    "        if name == 'oai_dc:dc':\n",
    "            data.append(publication)\n",
    "            publication = {}\n",
    "\n",
    "        element = None"
   ]
  },
  {
   "cell_type": "code",
   "execution_count": 14,
   "metadata": {},
   "outputs": [
    {
     "name": "stdout",
     "output_type": "stream",
     "text": [
      "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n",
      "<?xml-stylesheet type=\"text/xsl\" href=\"https://sol.sbc.org.br/lib/pkp/xml/oai2.xsl\" ?>\n",
      "<OAI-PMH xmlns=\"http://www.openarchives.org/OAI/2.0/\"\n",
      "\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/\n",
      "\t\thttp://www.openarchives.org/OAI/2.0/OAI-PMH.xsd\">\n",
      "\t<responseDate>2022-09-24T20:18:52Z</responseDate>\n",
      "\t<request verb=\"ListRecords\" metadataPrefix=\"oai_dc\">https://sol.sbc.org.br/index.php/vem/oai</request>\n",
      "\t<ListRecords>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7572</identifier>\n",
      "\t\t\t\t<datestamp>2019-09-13T19:11:52Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7573</identifier>\n",
      "\t\t\t\t<datestamp>2019-09-13T19:11:52Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7574</identifier>\n",
      "\t\t\t\t<datestamp>2019-09-13T19:11:52Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7575</identifier>\n",
      "\t\t\t\t<datestamp>2019-09-13T19:11:52Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7576</identifier>\n",
      "\t\t\t\t<datestamp>2019-09-13T19:11:52Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7577</identifier>\n",
      "\t\t\t\t<datestamp>2019-09-13T19:11:52Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/7586</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:25:44Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">How do Technical Factors Affect Developers in Mobile Software Ecosystems</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">How do Technical Factors Affect Developers in Mobile Software Ecosystems</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Steglich, Caio</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Marczak, Sabrina</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Santos, Rodrigo</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Guerra, Luiz</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Mosmann, Luiz</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>de Souza, Cleidson</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Figueira Filho, Fernando</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Perin, Marcelo</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">A área de Evolução de Software traz os aplicativos para a era da mobilidade, aonde os usuários desejam usar esses aplicativos em seus dispositivos móveis. Um ecossistema de software móvel (MSECO) é o tipo de ecossistema em que os desenvolvedores criam aplicativos para atender aos usuários de tecnologias móveis (por exemplo, Android e iOS). A literatura explica que é fundamental para a sustentabilidade do MSECO a capacidade de atrair e reter pessoas (ou seja, desenvolvedores e usuários) para sobreviver ao longo dos anos. Em um trabalho anterior, realizou-se uma Revisão de Literatura, na qual foram identificados 6 fatores que podem influenciar os desenvolvedores a participar de um MSECO. Neste estudo, apresenta-se um Estudo de Campo que teve como objetivo identificar como esses 6 fatores influenciaram profissionais da área em projetos reais vivenciados pelos mesmos.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">The Software Evolution area brings applications to the Mobile era in which users want to use these applications on their mobile devices. A Mobile Software Ecosystem (MSECO) is the kind of ecosystems in which developers build applications to attend the needs of mobile technologies users (e.g., Android and iOS). Literature explains that the capability to attracting and retaining people (i.e., developers and users) is essencial to MSECO sustainability, i.e., to the MSECO survive along the years. In a previous work, we conducted a literature review that identified 6 factors that may influence developers to participate in an MSECO. In this study, we present a Field Study aiming to understand how these 6 identified factors may have influenced practitioners in real life projects.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2019-09-25</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7586</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2019.7586</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 58-65</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 58-65</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2019</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7586/7461</dc:relation>\n",
      "\t\t\t\t\t<dc:rights xml:lang=\"pt-BR\">Copyright (c) 2019 Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM)</dc:rights>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/7587</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:25:44Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Uma Investigação da Aplicação de Aprendizado de Máquina para Detecção de Smells Arquiteturais</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Soyer Cunha, Warteruzannan</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Vieira de Camargo, Valter</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Uma investigação da aplicação de aprendizado de máquina para detectar os smells arquiteturais God Component (GC) e Unstable Dependency (UD) é apresentada neste trabalho. Dois datasets foram criados com exemplos coletados de sistemas reais. A acurácia, precisão e recall foram avaliadas com um conjunto de 10 algoritmos preditivos. Uma seleção de atributos foi realizada a fim de encontrar os mais relevantes para essa detecção. Os algoritmos AdaBoost e SVM (Support Vector Machine) com kernel linear alcançaram os melhores resultados para o GC e UD, respectivamente. Além disso, observouse que alguns atributos que a princípio não seriam considerados, contribuíram para a precisão da detecção.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2019-09-25</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7587</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2019.7587</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 66-73</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 66-73</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2019</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7587/7462</dc:relation>\n",
      "\t\t\t\t\t<dc:rights xml:lang=\"pt-BR\">Copyright (c) 2019 Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM)</dc:rights>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/7588</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:25:44Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">O Impacto da Utilização da Ferramenta Pivotal Tracker para Monitoração de Desempenho em Times Ágeis de Desenvolvimento de Software</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Netto, Dorgival</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>de Holanda, Ana</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Neves, Flavio</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Rocha, Cloves</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Bastos, Helena</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">This research aims to analyze the influence that the performance monitoring tool Pivotal has on the relationship between the members of a development agile team. An ethnographic case study was conducted in a software development company, with the unit of analysis being team members and the project manager. We realize that the tool shares with all information, schedules, and performance of each team member, allowing everyone to follow the steps of the project. Also, the spirit of unity and knowledge sharing brings a sense of trust and satisfaction among the team members.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Esta pesquisa visa analisar a influência que a ferramenta de monitoração de desempenho Pivotal tem na relação entre os membros de um time ágil de desenvolvimento. Foi realizado um estudo de caso de cunho etnográfico em uma empresa de desenvolvimento de software, tendo como unidade de análise os membros do time e o gerente de projetos. Identificamos que a ferramenta compartilha com todos as informações, cronogramas e desempenho de cada membro da equipe, permitindo que todos possam acompanhar as etapas do projeto. Além disso, o espírito de união e compartilhamento de conhecimento trazem a sensação de confiança e satisfação entre os indivíduos do time.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2019-09-25</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7588</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2019.7588</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 74-81</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 74-81</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2019</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7588/7463</dc:relation>\n",
      "\t\t\t\t\t<dc:rights xml:lang=\"pt-BR\">Copyright (c) 2019 Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM)</dc:rights>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/7589</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:25:44Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Um estudo preliminar sobre o uso de uma arquitetura deep learning para seleção de respostas no problema de recuperação de código-fonte</dc:title>\n",
      "\t\t\t\t\t<dc:creator>de Rezende Martins, Marcelo</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Gerosa, Marco Aurélio</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Dado uma questão e um conjunto de trechos de código-fonte, recuperação de código-fonte ou code retrieval busca encontrar o código que soluciona a dada questão. Este artigo apresenta um estudo preliminar sobre uma nova abordagem para o problema de recuperação de código-fonte, utilizando uma arquitetura deep learning de seleção de respostas. Apresentamos os resultados preliminares do modelo de redes neurais recorrentes bidirecionais (bi-LSTM) com redes neurais convolucionais (CNN) adaptado para o problema de recuperação de código-fonte. Após 20 execuções na amostra de teste, nosso modelo conseguiu atingir uma média MRR de 0,60 ± 0,02 e a medida top-1 o máximo de 51%.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Code retrieval techniques aim to select a code snippet to solve a question given a set of possible solutions. This article presents a preliminary study about a new approach for code retrieval, applying an answer selection deep learning architecture. We present the preliminary results of a bidirectional LSTM with convolutional network model adapted for code retrieval. After 20 runs on a evaluation dataset, our model could achieve a mean MRR of 0.60 ± 0.02 and a top-1 accuracy up to 51%.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2019-09-25</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7589</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2019.7589</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 82-89</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 82-89</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2019</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7589/7464</dc:relation>\n",
      "\t\t\t\t\t<dc:rights xml:lang=\"pt-BR\">Copyright (c) 2019 Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM)</dc:rights>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/7579</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:25:44Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Análise de Sentimentos em Discussões de Issues Reabertas do Github</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Boechat, Gláucya</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Mota Jr, Joselito</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Machado, Ivan</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Mendonça, Manoel</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">The behavior of reopened issues is a perception to be studied to analyze the impact of discussions on the continuity of software project maintenance. Sentiment analysis is presented as a powerful technique to assist such analysis. In this study, we analyzed 12,996 reopened issues, which contained discussions, from 80 Github projects. Based on the analysis of such historical data, we seek to analyze whether a closed issue tends to be reopened from the sentiment analysis of this issue’s discussions. The analyzes are performed through the degree of sentiment of the texts of the comments of the issues. The SentiStrength tool, supported by Software Engineering lexicons, were used to classify the degree of polarity of the texts found. The study identified that the polarity of feelings in discussions can directly affect the issue’s life cycle, including support for the prediction about reopening issues.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">O comportamento de issues reabertas é uma percepção a ser estudada para analisar o impacto das discussões na continuidade da manutenção de projetos de software. A análise de sentimentos apresenta-se como uma poderosa técnica para auxiliar tal análise. Neste estudo, analisamos 12.996 issues reabertas, contendo discussões, de 80 projetos do Github. Com base na análise dessa massa de dados históricos, buscamos analisar se uma issue fechada tende a ser reaberta a partir da análise de sentimentos das discussões dessa issue. As análises são realizadas através do grau de sentimento dos textos dos comentá- rios das issues. A ferramenta SentiStrength, com suporte aos léxicos da área de Engenharia de Software, foi utilizada para classificar o grau de polaridade dos textos encontrados. O estudo identificou que a polaridade dos sentimentos nas discussões pode afetar diretamente o ciclo de vida da issue, inclusive com suporte à predição sobre a reabertura das issues.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2019-09-25</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7579</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2019.7579</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 1-8</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 1-8</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2019</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7579/7454</dc:relation>\n",
      "\t\t\t\t\t<dc:rights xml:lang=\"pt-BR\">Copyright (c) 2019 Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM)</dc:rights>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/7580</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:25:44Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">BULNER: BUg Localization with word embeddings and NEtwork Regularization</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">BULNER: BUg Localization with word embeddings and NEtwork Regularization</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Rodrigues Barbosa, Jacson</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Marcondes Marcacini, Ricardo</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Britto, Ricardo</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Soares, Frederico</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Rezende, Solange</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>M. R. Vincenzi, Auri</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>E. Delamaro, Márcio</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Bug localization (BL) from the bug report is the strategic activity of the software maintaining process. Because BL is a costly and tedious activity, BL techniques information retrieval-based and machine learning-based could aid software engineers. We propose a method for BUg Localization with word embeddings and Network Regularization (BULNER). The preliminary results suggest that BULNER has better performance than two state-of-the-art methods.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Bug localization (BL) from the bug report is the strategic activity of the software maintaining process. Because BL is a costly and tedious activity, BL techniques information retrieval-based and machine learning-based could aid software engineers. We propose a method for BUg Localization with word embeddings and Network Regularization (BULNER). The preliminary results suggest that BULNER has better performance than two state-of-the-art methods.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2019-09-25</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7580</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2019.7580</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 9-16</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 9-16</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2019</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7580/7455</dc:relation>\n",
      "\t\t\t\t\t<dc:rights xml:lang=\"pt-BR\">Copyright (c) 2019 Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM)</dc:rights>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/14522</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:14:18Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART2</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Visualizing the Maintainability of Feature Models in SPLs</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Visualizing the Maintainability of Feature Models in SPLs</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Lima, Luan</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Uchôa, Anderson</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Bezerra, Carla</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Coutinho, Emanuel</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Rocha, Lincoln</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Feature model</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Visualization</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Maintainability</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Feature model</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Visualization</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Maintainability</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">This paper presents data visualizations obtained from the application of 15 measures used to support the maintainability evaluation of Software Product Line (SPL) and Dynamic SPL (DSPL) Feature Models (FMs). To identify these visualizations, we applied a survey to classify a set of 40 measures for evaluating the (D)SPL FMs maintainability. Five visualizations were designed from this classification to analyze the extensibility, static variability, dynamic variability, and structural complexity of the FMs. As result, the experts concluded the designed visualizations assist in FMs maintainability interpretation.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">This paper presents data visualizations obtained from the application of 15 measures used to support the maintainability evaluation of Software Product Line (SPL) and Dynamic SPL (DSPL) Feature Models (FMs). To identify these visualizations, we applied a survey to classify a set of 40 measures for evaluating the (D)SPL FMs maintainability. Five visualizations were designed from this classification to analyze the extensibility, static variability, dynamic variability, and structural complexity of the FMs. As result, the experts concluded the designed visualizations assist in FMs maintainability interpretation.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2020-10-19</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14522</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2020.14522</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 1-8</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 1-8</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2020</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14522/14368</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/14523</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:14:18Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART2</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Analyzing Technical Debt Identification Strategies</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Analisando Estratégias para Identificação de Dívidas Técnicas</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Oliveira, Isabela</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Marques-Neto, Humberto T.</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Xavier, Laerte</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Technical Debt</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Self-Admitted Technical Debt</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">SonarQube</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">SATD</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Dívida Técnica</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Débito Técnico Admitido</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">SonarQube</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">SATD</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Dívidas técnicas são uma constante no desenvolvimento de software. Para lidar com a pressão de entregas rápidas, desenvolvedores constantemente comprometem a qualidade do sistema entregue, postergando seu pagamento para fases posteriores. Com o objetivo de reduzir seus efeitos negativos, diversas soluções são propostas na literatura para identificação, gerenciamento e pagamento destas dívidas. Dentre elas, destacam-se as abordagens baseadas em análise estática (code smells), ou em comentários de código (self-admitted technical debt, ou SATD). Entretanto, ainda não está clara a real interseção entre tais abordagens, tampouco as características das dívidas melhor identificadas por cada uma delas. Neste trabalho, realizou-se uma comparação entre ambas abordagens através da aplicação das ferramentas SonarQube e SATDDetector num conjunto composto por 1.000 repositórios populares do GitHub. Como resultado, verificou-se que a interseção entre elas é de aproximadamente 19%, e que, em 7%, dos casos o SonarQube não é capaz de identificar SATDs. Ademais, as dívidas identificadas por ambas abordagens estão relacionadas à arquivos maiores (em termos de linhas de código), mais complexos (complexidade ciclomática e cognitiva) e com mais code smells.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Technical Debt (TD) is a constant in software development. To deal with the pressure of fast deliveries, developers constantly compromise the quality of the delivered system, postponing TD payment to later stages. In order to reduce its negative effects, several solutions are proposed in the literature for the identification, management and payment of these debts. Among them, we highlight the approaches based on static analysis (code smells), or on code comments (self-admitted technical debt, or SATD). However, the real intersection between such approaches is not yet clear, nor are the characteristics of the debts best identified by each of them. In this work, we perform a comparison between both approaches through the application of SonarQube and SATDDetector in a dataset of 1,000 popular GitHub repositories. As a result, we observe that the intersection between them is approximately 19%, and that in 7% of the cases SonarQube is not able to identify SATDs. In addition, the debts identified by both approaches are related to larger files (in terms of lines of code), more complex (cyclomatic and cognitive complexity) and more smelly (code smells).</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2020-10-19</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14523</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2020.14523</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 9-16</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 9-16</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2020</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14523/14369</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/14524</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:14:18Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART2</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Towards an approach to decompose monolithic systems in microservices</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Proposta de uma abordagem para decompor sistemas monolíticos em microsserviços</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Brasil, Felipe Chateaubriand</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Terra, Ricardo</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Architecture</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Microservices</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Monolithic</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Microservices decomposition</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Arquitetura</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Microsserviços</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Monolítico</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Extração de microsserviços</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">The microservice architecture has been widely adopted in the development of software systems. While the development of new systems occurs naturally, adopting this new architectural style in legacy systems---whose task of migration can be costly, time-consuming, and financially expensive---is a challenging problem. Given this scenario, this article proposes a semi-automatic approach to assist software architects in the task of decomposing monolithic systems in microservices. A preliminary assessment brought promising results since, with few iterations, it obtained a concise set of microservices with greater cohesion (6.98%) and less coupling (5.9%).</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">A arquitetura de microsserviços vem sendo amplamente adotada no desenvolvimento de sistemas de software. Enquanto o desenvolvimento de novos sistemas ocorre de forma natural, adotar esse novo estilo arquitetural em sistemas legados -- cuja tarefa de migração pode ser custosa, demorada e financeiramente cara para se realizar -- é um problema desafiador. Diante desse cenário, este artigo propõe uma abordagem semi-automática para auxiliar arquitetos de software na tarefa de decomposição de sistemas monolíticos em microsserviços. Uma avaliação preliminar trouxe resultados promissores uma vez que, com poucas iterações, obteve um conjunto conciso de microsserviços com maior coesão (6,98%) e menor acoplamento (5,9%). </dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2020-10-19</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14524</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2020.14524</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 17-24</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 17-24</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2020</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14524/14370</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/14525</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:14:18Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART2</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Data-Flow Analysis Heuristic for Vulnerability Detection on Configurable Systems</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Data-Flow Analysis Heuristic for Vulnerability Detection on Configurable Systems</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Andrade, Gleyberson</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Cirilo, Elder</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Durelli, Vinicius</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Cafeo, Bruno</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Adachi, Eiji</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Vulnerability Detection</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Software Product Lines</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Sampling Strategies</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Vulnerability Detection</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Software Product Lines</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Sampling Strategies</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Configurable software systems offer a variety of benefits such as supporting easy configuration of custom behaviours for distinctive needs. However, it is known that the presence of configuration options in source code complicates maintenance tasks and requires additional effort from developers when adding or editing code statements. They need to consider multiple configurations when executing tests or performing static analysis to detect vulnerabilities. Therefore, vulnerabilities have been widely reported in configurable software systems. Unfortunately, the effectiveness of vulnerability detection depends on how the multiple configurations (i.e., samples sets) are selected. In this paper, we tackle the challenge of generating more adequate system configuration samples by taking into account the intrinsic characteristics of security vulnerabilities. We propose a new sampling heuristic based on data-flow analysis for recommending the subset of configurations that should be analyzed individually. Our results show that we can achieve high vulnerability-detection effectiveness with a small sample size.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Configurable software systems offer a variety of benefits such as supporting easy configuration of custom behaviours for distinctive needs. However, it is known that the presence of configuration options in source code complicates maintenance tasks and requires additional effort from developers when adding or editing code statements. They need to consider multiple configurations when executing tests or performing static analysis to detect vulnerabilities. Therefore, vulnerabilities have been widely reported in configurable software systems. Unfortunately, the effectiveness of vulnerability detection depends on how the multiple configurations (i.e., samples sets) are selected. In this paper, we tackle the challenge of generating more adequate system configuration samples by taking into account the intrinsic characteristics of security vulnerabilities. We propose a new sampling heuristic based on data-flow analysis for recommending the subset of configurations that should be analyzed individually. Our results show that we can achieve high vulnerability-detection effectiveness with a small sample size.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2020-10-19</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14525</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2020.14525</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 25-32</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 25-32</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2020</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14525/14371</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/14526</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:14:18Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART3</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">I want to use this! An analysis of the target audience of code samples.</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Quero lhe usar! Uma Análise do Público Alvo de Code Samples</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Braga, Willian</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Menezes, Gabriel</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Fontão, Awdren</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Hora, André</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Cafeo, Bruno</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Code Samples</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Stack Overflow</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Reputation</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Mining Software Repositories</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">SECO</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Code Sample</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Stack Overflow</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Reputation</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Mineração de repósitorios de software</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">ECOS</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Code samples are projects made available by organizations to assist the learning process of features of their products software. There is an increase in the importance that code samples have in the developer community, but little is known about who are using them. The target audience for code samples is believed to be the inexperienced developer, but to start a characterization, the current work presents an empirical study through the analysis of developer statistics on the Stack Overflow. As a result, implications have been generated that can assist organizations to keep code samples relevants to developers.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Code samples são projetos disponibilizados por organizações para auxiliar no aprendizado de funcionalidades de seus produtos. Existe um crescimento na importância dos code samples para a comunidade de desenvolvedores, mas pouco se sabe sobre quem os usam. Acredita-se que o público-alvo dos code samples é o desenvolvedor inexperiente, mas para iniciar uma caracterização, este trabalho apresenta um estudo empírico por meio da análise de estatísticas de desenvolvedores no Stack Overflow. Como resultado, foi gerado um conjunto de implicações que pode auxiliar as organizações a manter os code samples relevantes para os desenvolvedores.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2020-10-19</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14526</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2020.14526</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 33-40</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 33-40</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2020</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14526/14372</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/14527</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:14:18Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART3</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Validation and construction of a lexical dictionary to assist sentiment analysis in software project repositories</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Validação e construção de um dicionário léxico para auxiliar a análise de sentimentos em repositórios de projetos de software</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Menezes, Hiolanda</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Boechat, Gláucya</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Mota Jr, Joselito</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Machado, Ivan</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Software Engineering</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">software maintenance</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">sentiment analysis</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">lexicon dictionary</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">polarity</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">validation</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Engenharia de software</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">manutenção de software</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Análise de Sentimentos</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">polaridade</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">dicionário léxico</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">validação</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Sentiment analysis makes inference about polarities in words that can represent possible emotions. The assertiveness of this classification is important for the results reliability. For this reason, this article investigates, validates and builds the lexicon dictionary, in the context of Software Engineering, using words, emoticons and idiomatic expressions from the SentiStrength-SE tool. An experiment online with 559 questions answered from 48 participants in the Computing area was performed to validate lexical terms agreement from the dictionary. At the end of the data collection, the terms were gathered for validation using a Stack Overflow database to find the results on accuracy, precision, recall and F1-score of the new dictionary. The new lexical dictionary has 79% Accuracy and Precision, with 78% Recall and f1-score with a smaller polarity interval than the original dictionary.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">A análise de sentimentos faz inferência sobre polaridades em palavras que podem representar possíveis emoções. A assertividade dessa classificação é importante para a confiabilidade do resultado esperado. Por esta razão, este trabalho busca investigar, validar e construir um dicionário léxico, no contexto de Engenharia de Software, utilizando como base as palavras, emoticons e expressões idiomáticas da ferramenta SentiStrength-SE. Um experimento com 559 questões respondidas por 48 participantes da área de Computação foi realizado para validação da concordância dos termos léxicos do dicionário. Ao final da coleta dos dados os termos foram reunidos para validação utilizando uma base de dados do Stack Overflow para encontrar os resultados sobre accuracy, precision, recall e F1-score do novo dicionário. O novo dicionário léxico apresenta 79% de acurácia e precisão, com 78% de Recall e F1-score com um intervalo de polaridade menor do que o dicionário original.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2020-10-19</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14527</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2020.14527</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 41-48</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 41-48</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2020</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14527/14373</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/14528</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:14:18Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART3</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Contextual Similarity Among Identifier Names: An Empirical Study</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Contextual Similarity Among Identifier Names: An Empirical Study</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Gresta, Remo</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Cirilo, Elder</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Identifier names</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Semantic Similarity</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Word Embedding</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Empirical Study</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Identifier names</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Semantic Similarity</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Word Embedding</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Empirical Study</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Identifiers are one of the most important sources of domain information in software development. Therefore, it is recognized that the proper use of names directly impacts the code's comprehensibility, maintainability, and quality. Our goal in this work is to expand the current knowledge about names by considering not only their quality but also their contextual similarity. To achieve that, we extracted names of four large scale open-source projects written in Java. Then, we computed the semantic similarity between classes and their attributes/variables using Fasttext, an word embedding algorithm. As a result, we could observe that source code, in general, preserve an acceptable level of contextual similarity, developers avoid to use names out of the default dictionary (e.g., domain), and files with more changes and maintained by distinct contributors tend to have better a contextual similarity.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Identifiers are one of the most important sources of domain information in software development. Therefore, it is recognized that the proper use of names directly impacts the code's comprehensibility, maintainability, and quality. Our goal in this work is to expand the current knowledge about names by considering not only their quality but also their contextual similarity. To achieve that, we extracted names of four large scale open-source projects written in Java. Then, we computed the semantic similarity between classes and their attributes/variables using Fasttext, an word embedding algorithm. As a result, we could observe that source code, in general, preserve an acceptable level of contextual similarity, developers avoid to use names out of the default dictionary (e.g., domain), and files with more changes and maintained by distinct contributors tend to have better a contextual similarity.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2020-10-19</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14528</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2020.14528</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 49-56</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 49-56</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2020</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14528/14374</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/14529</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:14:18Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART3</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">DiffMutAnalyze: A tool to assist the analysis of equivalent mutants in mutation test teaching</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">DiffMutAnalyze: uma ferramenta para auxiliar a análise dos mutantes equivalentes no ensino do teste de mutação</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Botelho, Juliana</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Souza, Maurício</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Durelli, Vinicius H. S.</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Durelli, Rafael S.</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Software testing</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Mutation Test</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Mutation analysis</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">DiffMutAnalyze</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Software testing for education</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Teste de Software</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Teste de Mutação</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Mutantes Equivalentes</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">DiffMutAnalyze</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Teste de Software na Educação</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Mutation testing is a technique that aims to evaluate a test cases and, consequently, to help improve their quality. Mutation testing is a promising technique to assist students in developing skills in software testing. Thus, this article presents the use of the DiffMutAnalyze tool in the academic field. It provides an environment that: (i) promotes the generation of mutants, (ii) the execution of test cases in the mutants generated, (iii) the identification of the detected mutants, and (iv) the availability of the analysis of possible equivalent mutants. DiffMutAnalyze was evaluated with 11 Graduate Students in Computer Science, to support the teaching of mutant testing and to show the practical application of mutation and analysis of mutants. A study was performed with the students to verify the cost of the equivalent mutant analysis, being compared in two ways: (i) by using DiffMutAnalyze; and (ii) through manual analysis, without using DiffMutAnalyze. The results showed a significant time reduction in comparison to the manual analysis.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">O teste de mutação é uma técnica que visa avaliar os casos de teste e, consequentemente, ajudar a melhorar sua qualidade. O teste de mutação é uma técnica promissora para ajudar os alunos a desenvolverem habilidades em testes de software. Assim, este artigo apresenta a utilização da ferramenta DiffMutAnalyze no âmbito acadêmico. Ela fornece um ambiente que: (i) promove a geração de mutantes, (ii) promove a execução de casos de teste nos mutantes gerados, (iii) permite a identificação dos mutantes detectados e (iv) disponibiliza para análise dos possíveis mutantes equivalentes. A DiffMutAnalyze foi avaliada com 11 estudantes de Pós-Graduação em Ciência da Computação, para apoiar o ensino de testes de mutantes e para mostrar a aplicação prática de mutação e análise de mutantes. Foi realizado um estudo, junto aos estudantes, para verificar o custo da análise dos mutantes equivalentes, sendo comparado de duas maneiras: (i) pelo uso da DiffMutAnalyze; e (ii) por meio da análise manual, sem o uso da DiffMutAnalyze. Os resultados mostraram uma redução significativa de tempo em comparação com a análise manual.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2020-10-19</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14529</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2020.14529</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 57-64</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 57-64</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2020</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14529/14375</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/14530</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:14:18Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:FRONT</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Front Matter</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Front Matter</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Durelli, Rafael</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Rocha, Lincoln</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">The 8th Workshop on Software Visualization, Evolution, and Maintenance (VEM 2020) is part of the 11th Brazilian Congress on Software: Theory and Practice (CBSoft 2020), held in virtual mode on October 19, 2020. Its main goal is to foster the integration of the software visualization, evolution and maintenance communities, providing a Brazilian forum where researchers, students, and professionals can present their work and exchange ideas on the principles, practices, and innovations related to their respective areas of interest. The VEM 2020 Program Committee (PC) is composed of 44 active researchers in the areas of software visualization, evolution, and maintenance, who come from several regions of Brazil. The PC members selected eight interesting and promising papers to be presented at VEM 2020 from a total of 12 submissions. Each submission was evaluated by at least three PC members based on their originality, technical quality, and adequacy to the event’s scope.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">The 8th Workshop on Software Visualization, Evolution, and Maintenance (VEM 2020) is part of the 11th Brazilian Congress on Software: Theory and Practice (CBSoft 2020), held in virtual mode on October 19, 2020. Its main goal is to foster the integration of the software visualization, evolution and maintenance communities, providing a Brazilian forum where researchers, students, and professionals can present their work and exchange ideas on the principles, practices, and innovations related to their respective areas of interest. The VEM 2020 Program Committee (PC) is composed of 44 active researchers in the areas of software visualization, evolution, and maintenance, who come from several regions of Brazil. The PC members selected eight interesting and promising papers to be presented at VEM 2020 from a total of 12 submissions. Each submission was evaluated by at least three PC members based on their originality, technical quality, and adequacy to the event’s scope.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2020-10-19</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14530</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; i-x</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; i-x</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2020</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14530/14376</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/14531</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:14:18Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:BACK</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Back Matter</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Back Matter</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Durelli, Rafael</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Rocha, Lincoln</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">The 8th Workshop on Software Visualization, Evolution, and Maintenance (VEM 2020) is part of the 11th Brazilian Congress on Software: Theory and Practice (CBSoft 2020), held in virtual mode on October 19, 2020. Its main goal is to foster the integration of the software visualization, evolution and maintenance communities, providing a Brazilian forum where researchers, students, and professionals can present their work and exchange ideas on the principles, practices, and innovations related to their respective areas of interest. The VEM 2020 Program Committee (PC) is composed of 44 active researchers in the areas of software visualization, evolution, and maintenance, who come from several regions of Brazil. The PC members selected eight interesting and promising papers to be presented at VEM 2020 from a total of 12 submissions. Each submission was evaluated by at least three PC members based on their originality, technical quality, and adequacy to the event’s scope.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">The 8th Workshop on Software Visualization, Evolution, and Maintenance (VEM 2020) is part of the 11th Brazilian Congress on Software: Theory and Practice (CBSoft 2020), held in virtual mode on October 19, 2020. Its main goal is to foster the integration of the software visualization, evolution and maintenance communities, providing a Brazilian forum where researchers, students, and professionals can present their work and exchange ideas on the principles, practices, and innovations related to their respective areas of interest. The VEM 2020 Program Committee (PC) is composed of 44 active researchers in the areas of software visualization, evolution, and maintenance, who come from several regions of Brazil. The PC members selected eight interesting and promising papers to be presented at VEM 2020 from a total of 12 submissions. Each submission was evaluated by at least three PC members based on their originality, technical quality, and adequacy to the event’s scope.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2020-10-19</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14531</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 65</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2020: Anais do VIII Workshop de Visualização, Evolução e Manutenção de Software; 65</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2020</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14531/14377</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/17210</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-04T12:37:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Characterizing the software evolution of smart contracts: An exploratory-descriptive study using GitHub and Etherscan</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Caracterizando a evolução de software de contratos inteligentes: Um estudo exploratório-descritivo utilizando GitHub e Etherscan</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Rodrigues, Alan</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Araújo, Allysson Allex</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Paixao, Matheus</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Soares, Pamella</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Smart Contracts</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Mining Repositories</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Ethereum</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Etherscan</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">GitHub</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Contratos Inteligentes</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Mineração de Repositórios</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Ethereum</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Etherscan</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">GitHub</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Blockchain has been framed as one of the new disruptive internet-based infrastructures. Part of this potential comes from strengthening blockchain public platforms, such as Ethereum, which enable decentralized applications (dApps). These solutions are based on smart contracts (SCs) and face specific constraints that challenge software evolution, such as data immutability and transparent access to the source code. In particular, code transparency can be observed through tools such as Etherscan, which provides public access to a vast amount of information from the SCs deployed in Ethereum. In addition, we can notice organizations in this ecosystem empowering themselves with open source development practices towards the SCs development, including the wide use of GitHub. This enriched scenario motivated us to conduct an exploratory-descriptive study based on mining software repositories to understand the SC software evolution through evaluating the similarity between the version developed on GitHub and the one being used in Ethereum (and auditable via Etherscan). In the light of a quali-quantitative analysis of 27 SCs, this paper contributes 1) by characterizing four patterns that depict different SC evolution behavior and 2) by approaching a string-based experimental method to compare the similarity between SC versions.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Blockchain tem sido enquadrada como uma nova infra-estrutura disruptiva baseada na internet. Parcela desse potencial advém do fortalecimento de plataformas públicas de blockchain, como a Ethereum, as quais viabilizam Aplicações Descentralizadas (dApps). Tais soluções são baseadas em contratos inteligentes (CIs) e lidam com restrições específicas que desafiam a evolução de software, como a imutabilidade de dados e o acesso transparente ao código-fonte. Em particular, a transparência de código pode ser observada através de ferramentas como o Etherscan, a qual provê acesso público a uma vasta quantidade de informações sobre os CIs implantados na Ethereum. Além disso, pode-se observar organizações oriundas desse ecossistema aderindo à prática de desenvolvimento open source dos CIs, incluindo o amplo uso do GitHub. Esse rico cenário motivou a necessidade de conduzir um estudo exploratório-descritivo baseado em mineração de repositórios de software para compreender a evolução de software de CIs através da avaliação de similaridade entre a versão disponível no GitHub e versão utilizada na Ethereum (e auditável via Etherscan). À luz de uma análise quali-quantititativa de 27 CIs, este artigo contribui ao 1) caracterizar quatro padrões que denotam diferentes comportamentos evolutivos dos CIs e 2) abordar um método experimental baseado em string para comparar a similaridade entre diferentes versões de CIs.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2021-09-27</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17210</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2021.17210</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 11-15</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 11-15</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2021</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17210/17048</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/17211</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-04T12:37:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">What do software team managers want from a skills identification?</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">What do software team managers want from a skills identification?</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Flauzino, Matheus A.</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Souza, Mauricio R. D. A.</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Durelli, Vinicius H. S.</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Durelli, Rafael S.</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">skill identification</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">development team</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">team management</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">skill identification</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">development team</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">team management</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Searching for developers with the necessary skills to work effectively on a project is not an easy task for companies. For software team managers, it is important to know their team's experience and what technologies they are using in order to be able to allocate resources optimally. Therefore, in this paper, we decided to study the needs of the managers of a software development company in order to identify their team's skills. We carried out a focus group. We have interviewed 11 managers from a development company (with approximately 75 developers). As result we have mapped 5 issues, 4 possible applications and another 7 needs to create a new methodology for identifying skills. Finally, we conclude that managers are interested in a methodology to identify skills in business flow.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Searching for developers with the necessary skills to work effectively on a project is not an easy task for companies. For software team managers, it is important to know their team's experience and what technologies they are using in order to be able to allocate resources optimally. Therefore, in this paper, we decided to study the needs of the managers of a software development company in order to identify their team's skills. We carried out a focus group. We have interviewed 11 managers from a development company (with approximately 75 developers). As result we have mapped 5 issues, 4 possible applications and another 7 needs to create a new methodology for identifying skills. Finally, we conclude that managers are interested in a methodology to identify skills in business flow.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2021-09-27</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17211</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2021.17211</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 16-20</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 16-20</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2021</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17211/17049</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/17212</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-04T12:37:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Mining Motivations for Applying Extract Method: A Preliminary Study</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Minerando Motivações para Aplicação de Extract Method: Um Estudo Preliminar</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Henrique, Jalisson</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Dósea, Marcos</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Sant’Anna, Cláudio</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Refactoring</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Extract Method</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Code metrics</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Refatoração</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Extract Method</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Métricas de código</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Refactorings are operations performed on source code to improve the software maintainability. The literature contains several studies on refactorings. However there are few studies that investigated the motivations for such refactorings to occur. Our research aims to investigate the motivations behind&amp;nbsp;extract&amp;nbsp;method&amp;nbsp;operations in a real system. For this, we conducted an empirical study in which we mined&amp;nbsp;extract&amp;nbsp;method&amp;nbsp;refactorings and analyzed commit messages in order to capture the motivations behind the refactorings. We also analyzed the relationship between refactorings and the number of lines of code (LOC) of the refactored methods. The results showed 11 different motivations for applying&amp;nbsp;extract&amp;nbsp;method. Furthermore, we also observed that only 35% of the refactorings were intended to improve code quality. We also identified that refactorings intended to improve code quality occurred more frequently in methods with LOC values in the range of 21 to 40 and were less frequent in methods with values between 61 to 80.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">As refatorações são operações realizadas no código fonte visando melhorar a capacidade de manutenção de um sistema de software. Apesar da literatura conter diversos estudos sobre as refatorações, são poucos os trabalhos que investigaram as motivações para tais refatorações ocorrerem. Esta pesquisa buscou investigar as motivações por trás das operações de extract method em um sistema real. Para isso, um estudo experimental foi conduzido, buscando minerar as refatorações do tipo extract method e analisar as mensagens de commit visando capturar as motivações por trás das refatorações. Também foi verificado a relação entre as refatorações e a métrica de número de linhas de código (LOC). Os resultados apontaram 11 motivações diferentes para a utilização do extract method. Além disso, foi visto que apenas 35% das refatorações que ocorreram foram com intenção de melhorar a qualidade do código. Também foi identificado que as refatorações com intenção de melhorar a qualidade do código ocorreram com maior frequência em métodos com valores de LOC na faixa de 21 a 40 e foram menos frequentes em métodos com valores entre 61 a 80.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2021-09-27</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17212</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2021.17212</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 21-25</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 21-25</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2021</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17212/17050</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/17213</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-04T12:37:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Investigating vulnerability datasets</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Investigating vulnerability datasets</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Andrade, Rodrigo</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Santos, Vinícius</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Vulnerability</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Datasets</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Commits</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">CVE</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Vulnerability</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Datasets</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Commits</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">CVE</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Insecure software can cause severe damage to user experience and privacy. Therefore, developers should be able to prevent software vulnerabilities. However, detecting such problems is expensive and time consuming. To mitigate this issue, researchers propose vulnerability datasets to make it easier to investigate its properties. In this work, we investigate one dataset to better understand common vulnerabilities, the authors who introduce them to open-source projects, and commit properties. Thus, we use as case study the Big-Vul dataset to help us answering the six research questions we define for this work. Our preliminary results indicate that the most common vulnerabilities occur in the Chromium project. Furthermore, mostly experienced authors are responsible for introducing these vulnerabilities. Last but not least, we conclude that such findings could help developers on detecting vulnerabilities.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Insecure software can cause severe damage to user experience and privacy. Therefore, developers should be able to prevent software vulnerabilities. However, detecting such problems is expensive and time consuming. To mitigate this issue, researchers propose vulnerability datasets to make it easier to investigate its properties. In this work, we investigate one dataset to better understand common vulnerabilities, the authors who introduce them to open-source projects, and commit properties. Thus, we use as case study the Big-Vul dataset to help us answering the six research questions we define for this work. Our preliminary results indicate that the most common vulnerabilities occur in the Chromium project. Furthermore, mostly experienced authors are responsible for introducing these vulnerabilities. Last but not least, we conclude that such findings could help developers on detecting vulnerabilities.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2021-09-27</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17213</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2021.17213</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 26-30</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 26-30</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2021</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17213/17051</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/17214</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-04T12:37:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Revealing Developers’ Arguments on Validating the Incidence of Code Smells: A Focus Group Experience</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Revealing Developers’ Arguments on Validating the Incidence of Code Smells: A Focus Group Experience</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Junionello, Luis Felipi</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>de Mello, Rafael</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Oliveira, Roberto</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Sousa, Leonardo</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>López, Alexander</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Garcia, Alessandro</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">code smells</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">validation</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">focus group</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">code smells</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">validation</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">focus group</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Identifying code smells is considered a subjective task. Unfortunately, current automated detection tools cannot deal with such subjectivity, requiring human validation. Developers tend to follow different, albeit complementary, strategies when validating the identified smells. Intending to find out developers' arguments when validating the incidence of code smells, we conducted a focus group session with developers familiar with identifying code smells. We distributed them among two groups, in which they had to argue about the incidence of a code smell: either accepting or rejecting its presence. Based on their arguments, we compiled a set of general heuristics that developers follow when validating smells. We then used these heuristics for composing validation items. We understand that the set of validation items proposed may support developers in reflecting on the incidence of code smells. However, further studies are needed for reaching a more comprehensive and optimized set. The experience of this study reveals that conducting focus group sessions is helpful to emerge the tacit knowledge of developers when validating code smells.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Identifying code smells is considered a subjective task. Unfortunately, current automated detection tools cannot deal with such subjectivity, requiring human validation. Developers tend to follow different, albeit complementary, strategies when validating the identified smells. Intending to find out developers' arguments when validating the incidence of code smells, we conducted a focus group session with developers familiar with identifying code smells. We distributed them among two groups, in which they had to argue about the incidence of a code smell: either accepting or rejecting its presence. Based on their arguments, we compiled a set of general heuristics that developers follow when validating smells. We then used these heuristics for composing validation items. We understand that the set of validation items proposed may support developers in reflecting on the incidence of code smells. However, further studies are needed for reaching a more comprehensive and optimized set. The experience of this study reveals that conducting focus group sessions is helpful to emerge the tacit knowledge of developers when validating code smells.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2021-09-27</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17214</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2021.17214</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 31-35</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 31-35</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2021</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17214/17052</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/17215</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-04T12:37:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">An Analysis of Test Co-Evolution on GitHub Software Projects</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Uma Análise da Co-Evolução de Teste em Projetos de Software no GitHub</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Miranda, Charles</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Avelino, Guilherme</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Santos Neto, Pedro</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>da Silva, Victor</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Co-evolution</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">test</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">mining software repositories</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">GitHub</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Co-evolução</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">teste</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">mineração de repositório de software</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">GitHub</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Os sistemas de software evoluem e essa evolução requer modificações em seu código-fonte para a realização de alterações, como correções de bugs, melhorias de desempenho ou adição de novas funcionalidades. Tendo em vista a importância da realização de testes para garantir a qualidade de um software, modificações no código-fonte devem ser acompanhadas de alterações e incrementos do código de teste. Entretanto, testes e a co-evolução desse muitas vezes são negligenciados no desenvolvimento de projetos de software, podendo resultar em maior esforço e custo para manter o projeto. Neste trabalho, através da análise de um grande dataset, composto pelo histórico de desenvolvimento de 3.000 projetos hospedados no Github, investigamos como artefatos de código-fonte e teste evoluem. Através da aplicação de técnicas de clusterização identificamos cinco padrões comuns de crescimento de teste. Adicionalmente, ao contrastar dados dos repositórios identificados com co-evolução e sem coevolução foi observado que os primeiros apresentam maiores níveis de contribuição (commits, colaboradores e forks).</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">The software systems evolve and the evolution requires modifications to its source code to make changes, such as bug fixes, performance improvements, or adding new features. Given the importance of testing to ensure software quality, source code modifications must be accompanied by test code changes and increments. However, testing and its co-evolution are often neglected in the development of software projects, which can result in greater effort and cost to maintain the project. In this work, through the analysis of a large dataset, consisting of the development history of 3,000 projects hosted on Github, we investigate how source code and test artifacts evolve. Through the application of clustering techniques, we identified five common test growth patterns. Additionally, when comparing data from repositories identified with co-evolution and without co-evolution, it was observed that the first ones present higher levels of contribution (commits, collaborators, and forks).</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2021-09-27</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17215</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2021.17215</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 36-40</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 36-40</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2021</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17215/17053</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/17216</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-04T12:37:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">BOHR - A Tool for Identifying Atoms of Confusion in Java Code</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">BOHR - Uma Ferramenta para a Identificação de Átomos de Confusão em Códigos Java</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Mendes, Wendell</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Viana, Windson</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Rocha, Lincoln</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Code Comprehension</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Atoms of Confusion</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Static Code Analysis</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Compreensão de Código</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Átomos de Confusão</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Análise Estática de Código</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">The activity of understanding source code is fundamental in software development and maintenance. In this context, Atoms of Confusion (AC) emerge as the smallest portion of code capable of causing confusion to developers in this process. In this paper,&amp;nbsp;BOHR&amp;nbsp;- The Atoms of Confusion Hunter is presented, a tool that aims to: (i) assist the identification of AC in&amp;nbsp;Java&amp;nbsp;systems; (ii) provide reports on the prevalence of these AC; and (iii) provide an API for the development of new custom search engines for capturing new CA and also improvements in their identifications. In this first version,&amp;nbsp;BOHR&amp;nbsp;is able to detect 8 of the 13 types of AC pointed out by Langhout and Aniche. A preliminary evaluation of the&amp;nbsp;BOHR&amp;nbsp;was conducted on three real open source systems widely adopted by the&amp;nbsp;Java&amp;nbsp;software development community (Picasso, greenDAO and Socket.IO-client&amp;nbsp;Java).&amp;nbsp; The initial results showed that&amp;nbsp;BOHR&amp;nbsp;was able to accurately detect the existing AC in these analyzed systems, correctly pointing out the AC snippets, as well as their type, class name it belonged to, and the line number of its occurrence. In total 105 CA were found, 37 in Picasso, 25 in greenDAO and 43 in the&amp;nbsp;Java&amp;nbsp;Socket.IO-client.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">A atividade de compreensão do código-fonte é fundamental no desenvolvimento e manutenção de software. Nesse contexto, Átomos de Confusão (AC) surgem como a menor porção de código capaz de causar confusão em desenvolvedores nesse processo. Neste artigo, é apresentado o BOHR - The Atoms of Confusion Hunter, uma ferramenta que tem como objetivos: (i) auxiliar a identificação de AC em sistemas Java; (ii) fornecer relatórios sobre a prevalência desses AC; e (iii) fornecer uma API para o desenvolvimento de novos buscadores customizados para a captura de novos AC e, também, melhorias em suas identificações. Nesta primeira versão, o BOHR é capaz de detectar 8 dos 13 tipos de AC apontados por Langhout e Aniche. Uma avaliação preliminar do BOHR foi conduzida em três sistemas reais, de código aberto, largamente adotados pela comunidade de desenvolvimento de softwares Java (Picasso, greenDAO e Socket.IO-client Java). Os resultados iniciais mostraram que o BOHR conseguiu detectar com precisão os AC existentes nesses sistemas analisados, apontando de forma correta os snippets dos AC, assim como o seu tipo, nome da classe que era pertencente e o número da linha de código de sua ocorrência. No total, foram encontrados 105 AC, sendo 37 no Picasso, 25 no greenDAO e 43 no Socket.IO-client Java.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2021-09-27</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17216</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2021.17216</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 41-45</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 41-45</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2021</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17216/17054</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/17217</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-04T12:37:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Readability and Understandability Scores for Snippet Assessment: an Exploratory Study</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Readability and Understandability Scores for Snippet Assessment: an Exploratory Study</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Dantas, Carlos Eduardo C.</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Maia, Marcelo A.</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">readability</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">understandability</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">code snippets</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">likert</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">code comprehension</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">readability</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">understandability</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">code snippets</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">likert</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">code comprehension</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Code search engines usually use readability feature to rank code snippets. There are several metrics to calculate this feature, but developers may have different perceptions about readability. Correlation between readability and understandability features has already been proposed, i.e., developers need to read and comprehend the code snippet syntax, but also understand the semantics. This work investigate scores for understandability and readability features, under the perspective of the possible subjective perception of code snippet comprehension. We find that code snippets with higher readability score has better comprehension than lower ones. The understandability score presents better comprehension in specific situations, e.g. nested loops or if-else chains. The developers also mentioned writability aspects as the principal characteristic to evaluate code snippets comprehension. These results provide insights for future works in code comprehension score optimization.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Code search engines usually use readability feature to rank code snippets. There are several metrics to calculate this feature, but developers may have different perceptions about readability. Correlation between readability and understandability features has already been proposed, i.e., developers need to read and comprehend the code snippet syntax, but also understand the semantics. This work investigate scores for understandability and readability features, under the perspective of the possible subjective perception of code snippet comprehension. We find that code snippets with higher readability score has better comprehension than lower ones. The understandability score presents better comprehension in specific situations, e.g. nested loops or if-else chains. The developers also mentioned writability aspects as the principal characteristic to evaluate code snippets comprehension. These results provide insights for future works in code comprehension score optimization.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2021-09-27</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17217</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2021.17217</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 46-50</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 46-50</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2021</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17217/17055</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/17218</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-04T12:37:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Say my name! An empirical study on the pronounceability of identifier names</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Say my name! An empirical study on the pronounceability of identifier names</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Gresta, Remo</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Cirilo, Elder</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Identifier names</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Phonetic Algorithm</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Pronounceable names</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Identifier names</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Phonetic Algorithm</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Pronounceable names</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Identifiers&amp;nbsp;represent approximately 2/3 of the elements in source code, and their&amp;nbsp;names&amp;nbsp;directly impact code comprehension. Indeed, intention-revealing&amp;nbsp;names&amp;nbsp;make code easier to understand, especially in code review sessions, where developers examine each other's code for mistakes. However, we argue that&amp;nbsp;names&amp;nbsp;should be understandable and&amp;nbsp;pronounceable&amp;nbsp;to enable developers to review and discuss code effectively. Therefore, we carried out an empirical study based on 40 open-source projects to explore the naming practices of developers concerning word complexity and pronounceability. We applied the Word Complexity Measure (WCM) to discover complex&amp;nbsp;names; and analyzed the phonetic similarity among&amp;nbsp;names&amp;nbsp;and hard-to-pronounce English words. As a result, we observed that most of the analyzed&amp;nbsp;names&amp;nbsp;are somewhat composed of hard-to-pronounce words. The overall word complexity score of the projects also tends to be significant. Finally, the results show that the code location impacts the word complexity:&amp;nbsp;names&amp;nbsp;in small scopes tend to be simpler than&amp;nbsp;names&amp;nbsp;declared in large scopes.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Identifiers&amp;nbsp;represent approximately 2/3 of the elements in source code, and their&amp;nbsp;names&amp;nbsp;directly impact code comprehension. Indeed, intention-revealing&amp;nbsp;names&amp;nbsp;make code easier to understand, especially in code review sessions, where developers examine each other's code for mistakes. However, we argue that&amp;nbsp;names&amp;nbsp;should be understandable and&amp;nbsp;pronounceable&amp;nbsp;to enable developers to review and discuss code effectively. Therefore, we carried out an empirical study based on 40 open-source projects to explore the naming practices of developers concerning word complexity and pronounceability. We applied the Word Complexity Measure (WCM) to discover complex&amp;nbsp;names; and analyzed the phonetic similarity among&amp;nbsp;names&amp;nbsp;and hard-to-pronounce English words. As a result, we observed that most of the analyzed&amp;nbsp;names&amp;nbsp;are somewhat composed of hard-to-pronounce words. The overall word complexity score of the projects also tends to be significant. Finally, the results show that the code location impacts the word complexity:&amp;nbsp;names&amp;nbsp;in small scopes tend to be simpler than&amp;nbsp;names&amp;nbsp;declared in large scopes.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2021-09-27</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17218</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2021.17218</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 51-55</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 51-55</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2021</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17218/17056</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/17208</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-04T12:37:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Bad Smells in Javascript - A Mapping Study</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Bad Smells in Javascript - A Mapping Study</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Barros, Aryclenio Xavier</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Adachi, Eiji</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">Javascript</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">bad smells</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">code smells</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">mapping</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">Javascript</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">bad smells</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">code smells</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">mapping</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Javascript is one of the most famous mainstream programming languages nowadays. It has gained considerable practical relevance over the last years, with applications in several areas, such as games, 3D rendering, and, mainly, web development. Like any other software system, systems developed in Javascript need to keep their ability to evolve to remain useful and relevant over time. Empirical evidence has shown that bad smells are possible indicators of problems hindering software evolvability. In this context, this paper presents a mapping study investigating if and to what extent bad smells have been defined for the Javascript language and how the interest in this topic has evolved. Our study identified 26 different types of bad smells investigated in the context of Javascript in 8 different works published between 2013 and 2020. This result suggests that although Javascript has gained practical relevance in recent years, there is still room for further empirical studies defining and evaluating the impact of bad smells on Javascript-based software systems.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Javascript is one of the most famous mainstream programming languages nowadays. It has gained considerable practical relevance over the last years, with applications in several areas, such as games, 3D rendering, and, mainly, web development. Like any other software system, systems developed in Javascript need to keep their ability to evolve to remain useful and relevant over time. Empirical evidence has shown that bad smells are possible indicators of problems hindering software evolvability. In this context, this paper presents a mapping study investigating if and to what extent bad smells have been defined for the Javascript language and how the interest in this topic has evolved. Our study identified 26 different types of bad smells investigated in the context of Javascript in 8 different works published between 2013 and 2020. This result suggests that although Javascript has gained practical relevance in recent years, there is still room for further empirical studies defining and evaluating the impact of bad smells on Javascript-based software systems.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2021-09-27</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17208</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2021.17208</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 1-5</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 1-5</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2021</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17208/17046</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/17209</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-04T12:37:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Assessing the Occurrence of Blocking Operations in Database Schema Evolution: A Case Study</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Assessing the Occurrence of Blocking Operations in Database Schema Evolution: A Case Study</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Lawrence, Willie</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Adachi, Eiji</dc:creator>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">blocking operations</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">database schema</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">schema evolution</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">software evolution</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"en-US\">case study</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">blocking operations</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">database schema</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">schema evolution</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">software evolution</dc:subject>\n",
      "\t\t\t\t\t<dc:subject xml:lang=\"pt-BR\">case study</dc:subject>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">During the evolution of a database schema, some schema-changing operations (e.g., the “ALTER TABLE” command) require the underlying database management system to lock tables until the opera-tion is finished. We call these schema-changing operations blocking operations. During the execution of blocking operations, a soft-ware application may behave abnormally, varying from a slow page loading to an error caused by a web request taking too long to return. Despite their potential negative impact on important qual-ity attributes, blocking operations have not yet been empirically investigated in the context of software evolution. To fill this gap, we conducted a large industrial case study in the context of a Brazilian software company. We analyzed 1,499 atomic schema-changing operations from a period of 6 years to explore which blocking operations the developers frequently performed during the evolution of the database schema of a target system. The intention behind this case study is better understanding the problem in its original context to outline strategies to correct or mitigate it in the future. Our results show that blocking operations were very common, though not all of them seemed to cause observable downtime periods. We also present some mitigating strategies already in use by the devel-opment team of the target system to cope with blocking operation during software evolution, avoiding their negative impact.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">During the evolution of a database schema, some schema-changing operations (e.g., the “ALTER TABLE” command) require the underlying database management system to lock tables until the opera-tion is finished. We call these schema-changing operations blocking operations. During the execution of blocking operations, a soft-ware application may behave abnormally, varying from a slow page loading to an error caused by a web request taking too long to return. Despite their potential negative impact on important qual-ity attributes, blocking operations have not yet been empirically investigated in the context of software evolution. To fill this gap, we conducted a large industrial case study in the context of a Brazilian software company. We analyzed 1,499 atomic schema-changing operations from a period of 6 years to explore which blocking operations the developers frequently performed during the evolution of the database schema of a target system. The intention behind this case study is better understanding the problem in its original context to outline strategies to correct or mitigate it in the future. Our results show that blocking operations were very common, though not all of them seemed to cause observable downtime periods. We also present some mitigating strategies already in use by the devel-opment team of the target system to cope with blocking operation during software evolution, avoiding their negative impact.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2021-09-27</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17209</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2021.17209</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 6-10</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2021: Anais do IX Workshop de Visualização, Evolução e Manutenção de Software; 6-10</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2021</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17209/17047</dc:relation>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/7585</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:25:44Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Análise e melhoria do processo de reengenharia de software: um estudo de caso</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Mendonça de Moraes, Guilherme</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Costa Oliveira, Edgard</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Apesar de muitos autores procurarem relacionar gestão de riscos com fracasso ou sucesso em projetos de reengenharia de software, a união das duas temáticas ainda é um grande desafio para as organizações que contratam ou fornecem produtos e serviços desse tipo. Esse artigo tem por objetivo a análise e melhoria do processo de reengenharia de software por meio da gestão de riscos. A metodologia adotada foi o estudo de caso de um projeto de mudança da tecnologia do software em uma instituição financeira de grande porte, o que resultou na melhoria do processo de reengenharia de software dessa instituição.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Although many authors seek to relate risk management to failure or success in software reengineering projects, the union of the two themes remains a major challenge for organizations that contract or provide such products and services. This article aims to analyze and improve the process of software reengineering through risk management. The methodology adopted was the case study of a project to change the technology of software in a large financial institution, which resulted in the improvement of the software reengineering process in the company.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2019-09-25</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7585</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2019.7585</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 49-57</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 49-57</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2019</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7585/7460</dc:relation>\n",
      "\t\t\t\t\t<dc:rights xml:lang=\"pt-BR\">Copyright (c) 2019 Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM)</dc:rights>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/7578</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:25:44Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:COV</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Prefácio</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Foreword</dc:title>\n",
      "\t\t\t\t\t<dc:creator>Castor, Fernando</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Scaliante Wiese, Igor</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Mensagem da Coordenação do VII Workshop on Software Visualization, Evolution and Maintenance</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2019-09-25</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7578</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; i-xi</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; i-xi</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2019</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7578/7453</dc:relation>\n",
      "\t\t\t\t\t<dc:rights xml:lang=\"pt-BR\">Copyright (c) 2019 Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM)</dc:rights>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/7582</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:25:44Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Uma análise da relação entre code smells e dívida técnica auto-admitida</dc:title>\n",
      "\t\t\t\t\t<dc:creator>de S. Gomes, Felipe Gustavo</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Souto Mendes, Thiago</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>O. Spínola, Rodrigo</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Mendonça, Manoel</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>Farias, Mário</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Code smells indicam possíveis problemas na implementação de um sistema que podem levar à necessidade de refatoração do seu código. Eles podem ser detectados automaticamente e são considerados indicadores de presença de Dívida Técnica (DT). Contudo, estudos indicam que considerar apenas code smells na tarefa de detecção da presença de itens de dívida é insuficiente. É necessário utilizar estratégias de detecção complementares, como a utilização de informações extraídas a partir de comentários de código. Porém, ainda são poucos os estudos sobre a relação entre code smells e DT autoadmitida. Este trabalho analisa três projetos open source para investigar a relação existente, em termos de sobreposição e complementariedade de itens de DT identificados, utilizando detecção via code smells e DT auto-admitida. Os resultados indicam que as informações de comentários podem complementar as informações de code smells e apoiar os desenvolvedores a identificar DT.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Code smells indicam possíveis problemas na implementação de um sistema que podem levar à necessidade de refatoração do seu código. Eles podem ser detectados automaticamente e são considerados indicadores de presença de Dívida Técnica (DT). Contudo, estudos indicam que considerar apenas code smells na tarefa de detecção da presença de itens de dívida é insuficiente. É necessário utilizar estratégias de detecção complementares, como a utilização de informações extraídas a partir de comentários de código. Porém, ainda são poucos os estudos sobre a relação entre code smells e DT autoadmitida. Este trabalho analisa três projetos open source para investigar a relação existente, em termos de sobreposição e complementariedade de itens de DT identificados, utilizando detecção via code smells e DT auto-admitida. Os resultados indicam que as informações de comentários podem complementar as informações de code smells e apoiar os desenvolvedores a identificar DT.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2019-09-25</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7582</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2019.7582</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 25-32</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 25-32</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2019</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7582/7457</dc:relation>\n",
      "\t\t\t\t\t<dc:rights xml:lang=\"pt-BR\">Copyright (c) 2019 Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM)</dc:rights>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/7583</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:25:44Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Clustering Similarity Measures for Architecture Recovery of Evolving Software</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">Clustering Similarity Measures for Architecture Recovery of Evolving Software</dc:title>\n",
      "\t\t\t\t\t<dc:creator>E. U. Silva, Douglas</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>A. Bittencourt, Roberto</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>T. Calumby, Rodrigo</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Automated software architecture recovery of module views from source code is a challenging research issue. Different similarity measures are used to evaluate clustering algorithms in the software architecture recovery of module views. However, few studies seek to evaluate whether such measures accurately capture the similarities between two clusterings. This work presents an evaluation of six clustering similarity measures through the use of intrinsic quality and stability measures and the use of ground truth architectures proposed by developers. The results suggest that the MeCl metric is the most adequate to measure similarity in the context of comparison with ground truth models provided by developers. However, when the architectural models do not exist, the Purity metric shows the best results, as measured by the correlation with the intrinsic Silhouette coefficient.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Automated software architecture recovery of module views from source code is a challenging research issue. Different similarity measures are used to evaluate clustering algorithms in the software architecture recovery of module views. However, few studies seek to evaluate whether such measures accurately capture the similarities between two clusterings. This work presents an evaluation of six clustering similarity measures through the use of intrinsic quality and stability measures and the use of ground truth architectures proposed by developers. The results suggest that the MeCl metric is the most adequate to measure similarity in the context of comparison with ground truth models provided by developers. However, when the architectural models do not exist, the Purity metric shows the best results, as measured by the correlation with the intrinsic Silhouette coefficient.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2019-09-25</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7583</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2019.7583</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 33-40</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 33-40</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2019</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7583/7458</dc:relation>\n",
      "\t\t\t\t\t<dc:rights xml:lang=\"pt-BR\">Copyright (c) 2019 Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM)</dc:rights>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/7584</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:25:44Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"en-US\">How Workspaces Influence Software Development? Preliminary Results of a Systematic Literature Review</dc:title>\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">How Workspaces Influence Software Development? Preliminary Results of a Systematic Literature Review</dc:title>\n",
      "\t\t\t\t\t<dc:creator>G. J. Costa, Victor</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>França, Cesár</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">This work brings to light the preliminary results of a literature review showing what physical elements of workspaces have been studied in software engineering, and what are their known impacts on software development performance. A systematic literature review has been conducted, covering a period of 16 years of publications in software engineering field. Seven dimensions of workspace factors were mapped and we present the impacts of these factors on elements of software development performance, such as communication and collaboration. This article evidences the fact that there is not a generally accepted best model for software development workspaces, and that there is still much room for investigation in this topic</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">This work brings to light the preliminary results of a literature review showing what physical elements of workspaces have been studied in software engineering, and what are their known impacts on software development performance. A systematic literature review has been conducted, covering a period of 16 years of publications in software engineering field. Seven dimensions of workspace factors were mapped and we present the impacts of these factors on elements of software development performance, such as communication and collaboration. This article evidences the fact that there is not a generally accepted best model for software development workspaces, and that there is still much room for investigation in this topic</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2019-09-25</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7584</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2019.7584</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 41-48</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 41-48</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2019</dc:source>\n",
      "\t\t\t\t\t<dc:language>eng</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7584/7459</dc:relation>\n",
      "\t\t\t\t\t<dc:rights xml:lang=\"pt-BR\">Copyright (c) 2019 Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM)</dc:rights>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7566</identifier>\n",
      "\t\t\t\t<datestamp>2019-09-13T19:11:52Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:COV</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7567</identifier>\n",
      "\t\t\t\t<datestamp>2019-09-13T19:11:52Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7568</identifier>\n",
      "\t\t\t\t<datestamp>2019-09-13T19:11:52Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7569</identifier>\n",
      "\t\t\t\t<datestamp>2019-09-13T19:11:52Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7570</identifier>\n",
      "\t\t\t\t<datestamp>2019-09-13T19:11:52Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7571</identifier>\n",
      "\t\t\t\t<datestamp>2019-09-13T19:11:52Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header>\n",
      "\t\t\t\t<identifier>oai:sol.sbc.org.br:article/7581</identifier>\n",
      "\t\t\t\t<datestamp>2021-10-26T18:25:44Z</datestamp>\n",
      "\t\t\t\t<setSpec>vem:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t\t<metadata>\n",
      "\t\t\t\t<oai_dc:dc xmlns:oai_dc=\"http://www.openarchives.org/OAI/2.0/oai_dc/\"\n",
      "\t\t\t\t\txmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n",
      "\t\t\t\t\txmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.openarchives.org/OAI/2.0/oai_dc/\n",
      "\thttp://www.openarchives.org/OAI/2.0/oai_dc.xsd\">\n",
      "\t\t\t\t\t<dc:title xml:lang=\"pt-BR\">Um relato sobre a migração de uma plataforma de offloading para microsserviços</dc:title>\n",
      "\t\t\t\t\t<dc:creator>L. Cândido, Adriano</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>A. M. Trinta, Fernando</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>A. L. Rego, Paulo</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>S Rocha, Lincoln</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>C. Mendonça, Nabor</dc:creator>\n",
      "\t\t\t\t\t<dc:creator>C. Garcia, Vinicius</dc:creator>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"pt-BR\">Os dispositivos móveis estão cada vez mais presentes no dia a dia das pessoas. No entanto, apesar da evolução das novas gerações de smartphones, a quantidade de informações e a complexidade dos procedimentos delegados a esses dispositivos, ainda impõem restrições ao processamento, principalmente relacionado ao consumo de energético. Uma solução que vem sendo utilizada para esse problema é a técnica conhecida como offloading. Nos últimos anos, várias plataformas de suporte ao offloading foram propostas. Este trabalho tem foco em uma dessas plataformas, denominado CAOS. Apesar de realizar tarefas de offloading com êxito, o CAOS ainda apresenta problemas como baixa escalabilidade. Neste estudo, descrevemos o processo de migração do CAOS para uma nova arquitetura baseada em microsserviços, evidenciando as decisões e práticas que foram adotadas nessa jornada.</dc:description>\n",
      "\t\t\t\t\t<dc:description xml:lang=\"en-US\">Mobiledevicesareincreasinglypresentinpeople’sdailylives.However, despite the evolution of new generations of smartphones, the amount of information and the complexity of the procedures delegated to these devices still impose processing restrictions, mainly related to energy consumption. One solution that is being used for this problem is the technique known as offloading. In recent years, several offloading support platforms have been proposed. This paper focuses on one of these platforms, called CAOS. Despite successfully performing offloading tasks, CAOS still has issues such as low scalability. In this study, we describe the process of migrating from CAOS to a new architecture based on microservices, highlighting the decisions and practices that were adopted on this journey.</dc:description>\n",
      "\t\t\t\t\t<dc:publisher xml:lang=\"pt-BR\">Sociedade Brasileira de Computação - SBC</dc:publisher>\n",
      "\t\t\t\t\t<dc:date>2019-09-25</dc:date>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/article</dc:type>\n",
      "\t\t\t\t\t<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>\n",
      "\t\t\t\t\t<dc:format>application/pdf</dc:format>\n",
      "\t\t\t\t\t<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7581</dc:identifier>\n",
      "\t\t\t\t\t<dc:identifier>10.5753/vem.2019.7581</dc:identifier>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"en-US\">Proceedings of the Workshop on Software Visualization, Evolution and Maintenance (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 17-24</dc:source>\n",
      "\t\t\t\t\t<dc:source xml:lang=\"pt-BR\">Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM); 2019: Anais do VII Workshop de Visualização, Evolução e Manutenção de Software; 17-24</dc:source>\n",
      "\t\t\t\t\t<dc:source>0000-0000</dc:source>\n",
      "\t\t\t\t\t<dc:source>10.5753/vem.2019</dc:source>\n",
      "\t\t\t\t\t<dc:language>por</dc:language>\n",
      "\t\t\t\t\t<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7581/7456</dc:relation>\n",
      "\t\t\t\t\t<dc:rights xml:lang=\"pt-BR\">Copyright (c) 2019 Anais do Workshop de Visualização, Evolução e Manutenção de Software (VEM)</dc:rights>\n",
      "\t\t\t\t</oai_dc:dc>\n",
      "\t\t\t</metadata>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/60</identifier>\n",
      "\t\t\t\t<datestamp>2017-06-22T14:18:12Z</datestamp>\n",
      "\t\t\t\t<setSpec>sbbd:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/61</identifier>\n",
      "\t\t\t\t<datestamp>2017-06-22T14:18:16Z</datestamp>\n",
      "\t\t\t\t<setSpec>sbbd:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/62</identifier>\n",
      "\t\t\t\t<datestamp>2017-06-22T14:18:16Z</datestamp>\n",
      "\t\t\t\t<setSpec>sbbd:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/63</identifier>\n",
      "\t\t\t\t<datestamp>2017-06-22T14:18:16Z</datestamp>\n",
      "\t\t\t\t<setSpec>sbbd:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/64</identifier>\n",
      "\t\t\t\t<datestamp>2017-06-22T14:18:16Z</datestamp>\n",
      "\t\t\t\t<setSpec>sbbd:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/65</identifier>\n",
      "\t\t\t\t<datestamp>2017-06-22T14:18:16Z</datestamp>\n",
      "\t\t\t\t<setSpec>sbbd:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/66</identifier>\n",
      "\t\t\t\t<datestamp>2017-06-22T14:18:16Z</datestamp>\n",
      "\t\t\t\t<setSpec>sbbd:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/67</identifier>\n",
      "\t\t\t\t<datestamp>2017-06-22T14:18:16Z</datestamp>\n",
      "\t\t\t\t<setSpec>sbbd:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/145</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/146</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/147</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/148</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/149</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/150</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/151</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/76</identifier>\n",
      "\t\t\t\t<datestamp>2017-06-29T18:28:48Z</datestamp>\n",
      "\t\t\t\t<setSpec>RB-RESD:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/77</identifier>\n",
      "\t\t\t\t<datestamp>2017-06-29T18:28:48Z</datestamp>\n",
      "\t\t\t\t<setSpec>RB-RESD:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/152</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/153</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/154</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/155</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/156</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/157</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/158</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/159</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/160</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/161</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/162</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/163</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:49Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/164</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:54Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/165</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-09T15:22:54Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/166</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/167</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/168</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/169</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/170</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/171</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/172</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/173</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/174</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/175</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/176</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/177</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/178</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/179</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/180</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/181</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/182</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/183</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/184</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/185</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/186</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/187</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/188</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<record>\n",
      "\t\t\t<header status=\"deleted\">\n",
      "\t\t\t\t<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/189</identifier>\n",
      "\t\t\t\t<datestamp>2017-10-14T22:37:37Z</datestamp>\n",
      "\t\t\t\t<setSpec>csbc:ART</setSpec>\n",
      "\t\t\t</header>\n",
      "\t\t</record>\n",
      "\t\t<resumptionToken expirationDate=\"2022-09-25T20:18:52Z\" completeListSize=\"4560\" cursor=\"0\">8b573ebba03c5a33c98f79b46f540ba8</resumptionToken>\n",
      "\t</ListRecords>\n",
      "</OAI-PMH>\n",
      "\n"
     ]
    }
   ],
   "source": [
    "parser = xml.sax.make_parser()\n",
    "parser.setContentHandler(SOLHandler())\n",
    "parser.parse(open('sol.xml', 'r'))\n",
    "print(open('sol.xml', 'r').read())"
   ]
  },
  {
   "cell_type": "code",
   "execution_count": 15,
   "metadata": {},
   "outputs": [
    {
     "data": {
      "text/html": [
       "<div>\n",
       "<style scoped>\n",
       "    .dataframe tbody tr th:only-of-type {\n",
       "        vertical-align: middle;\n",
       "    }\n",
       "\n",
       "    .dataframe tbody tr th {\n",
       "        vertical-align: top;\n",
       "    }\n",
       "\n",
       "    .dataframe thead th {\n",
       "        text-align: right;\n",
       "    }\n",
       "</style>\n",
       "<table border=\"1\" class=\"dataframe\">\n",
       "  <thead>\n",
       "    <tr style=\"text-align: right;\">\n",
       "      <th></th>\n",
       "      <th>title</th>\n",
       "      <th>authors</th>\n",
       "      <th>year</th>\n",
       "    </tr>\n",
       "  </thead>\n",
       "  <tbody>\n",
       "    <tr>\n",
       "      <th>0</th>\n",
       "      <td>How do Technical Factors Affect Developers in ...</td>\n",
       "      <td>Caio Steglich; Sabrina Marczak; Rodrigo Santos...</td>\n",
       "      <td>2019</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>1</th>\n",
       "      <td>Uma Investigação da Aplicação de Aprendizado d...</td>\n",
       "      <td>Warteruzannan Soyer Cunha; Valter Vieira de Ca...</td>\n",
       "      <td>2019</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>2</th>\n",
       "      <td>O Impacto da Utilização da Ferramenta Pivotal ...</td>\n",
       "      <td>Dorgival Netto; Ana de Holanda; Flavio Neves; ...</td>\n",
       "      <td>2019</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>3</th>\n",
       "      <td>Um estudo preliminar sobre o uso de uma arquit...</td>\n",
       "      <td>Marcelo de Rezende Martins; Marco Aurélio Gerosa</td>\n",
       "      <td>2019</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>4</th>\n",
       "      <td>Análise de Sentimentos em Discussões de Issues...</td>\n",
       "      <td>Gláucya Boechat; Joselito Mota Jr; Ivan Machad...</td>\n",
       "      <td>2019</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>5</th>\n",
       "      <td>BULNER: BUg Localization with word embeddings ...</td>\n",
       "      <td>Jacson Rodrigues Barbosa; Ricardo Marcondes Ma...</td>\n",
       "      <td>2019</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>6</th>\n",
       "      <td>Visualizing the Maintainability of Feature Mod...</td>\n",
       "      <td>Luan Lima; Anderson Uchôa; Carla Bezerra; Eman...</td>\n",
       "      <td>2020</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>7</th>\n",
       "      <td>Analisando Estratégias para Identificação de D...</td>\n",
       "      <td>Isabela Oliveira; Humberto T. Marques-Neto; La...</td>\n",
       "      <td>2020</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>8</th>\n",
       "      <td>Proposta de uma abordagem para decompor sistem...</td>\n",
       "      <td>Felipe Chateaubriand Brasil; Ricardo Terra</td>\n",
       "      <td>2020</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>9</th>\n",
       "      <td>Data-Flow Analysis Heuristic for Vulnerability...</td>\n",
       "      <td>Gleyberson Andrade; Elder Cirilo; Vinicius Dur...</td>\n",
       "      <td>2020</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>10</th>\n",
       "      <td>Quero lhe usar! Uma Análise do Público Alvo de...</td>\n",
       "      <td>Willian Braga; Gabriel Menezes; Awdren Fontão;...</td>\n",
       "      <td>2020</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>11</th>\n",
       "      <td>Validação e construção de um dicionário léxico...</td>\n",
       "      <td>Hiolanda Menezes; Gláucya Boechat; Joselito Mo...</td>\n",
       "      <td>2020</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>12</th>\n",
       "      <td>Contextual Similarity Among Identifier Names: ...</td>\n",
       "      <td>Remo Gresta; Elder Cirilo</td>\n",
       "      <td>2020</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>13</th>\n",
       "      <td>DiffMutAnalyze: uma ferramenta para auxiliar a...</td>\n",
       "      <td>Juliana Botelho; Maurício Souza; Vinicius H. S...</td>\n",
       "      <td>2020</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>14</th>\n",
       "      <td>Front Matter</td>\n",
       "      <td>Rafael Durelli; Lincoln Rocha</td>\n",
       "      <td>2020</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>15</th>\n",
       "      <td>Back Matter</td>\n",
       "      <td>Rafael Durelli; Lincoln Rocha</td>\n",
       "      <td>2020</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>16</th>\n",
       "      <td>Caracterizando a evolução de software de contr...</td>\n",
       "      <td>Alan Rodrigues; Allysson Allex Araújo; Matheus...</td>\n",
       "      <td>2021</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>17</th>\n",
       "      <td>What do software team managers want from a ski...</td>\n",
       "      <td>Matheus A. Flauzino; Mauricio R. D. A. Souza; ...</td>\n",
       "      <td>2021</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>18</th>\n",
       "      <td>Minerando Motivações para Aplicação de Extract...</td>\n",
       "      <td>Jalisson Henrique; Marcos Dósea; Cláudio Sant’...</td>\n",
       "      <td>2021</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>19</th>\n",
       "      <td>Investigating vulnerability datasets</td>\n",
       "      <td>Rodrigo Andrade; Vinícius Santos</td>\n",
       "      <td>2021</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>20</th>\n",
       "      <td>Revealing Developers’ Arguments on Validating ...</td>\n",
       "      <td>Luis Felipi Junionello; Rafael de Mello; Rober...</td>\n",
       "      <td>2021</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>21</th>\n",
       "      <td>Uma Análise da Co-Evolução de Teste em Projeto...</td>\n",
       "      <td>Charles Miranda; Guilherme Avelino; Pedro Sant...</td>\n",
       "      <td>2021</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>22</th>\n",
       "      <td>BOHR - Uma Ferramenta para a Identificação de ...</td>\n",
       "      <td>Wendell Mendes; Windson Viana; Lincoln Rocha</td>\n",
       "      <td>2021</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>23</th>\n",
       "      <td>Readability and Understandability Scores for S...</td>\n",
       "      <td>Carlos Eduardo C. Dantas; Marcelo A. Maia</td>\n",
       "      <td>2021</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>24</th>\n",
       "      <td>Say my name! An empirical study on the pronoun...</td>\n",
       "      <td>Remo Gresta; Elder Cirilo</td>\n",
       "      <td>2021</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>25</th>\n",
       "      <td>Bad Smells in Javascript - A Mapping Study</td>\n",
       "      <td>Aryclenio Xavier Barros; Eiji Adachi</td>\n",
       "      <td>2021</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>26</th>\n",
       "      <td>Assessing the Occurrence of Blocking Operation...</td>\n",
       "      <td>Willie Lawrence; Eiji Adachi</td>\n",
       "      <td>2021</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>27</th>\n",
       "      <td>Análise e melhoria do processo de reengenharia...</td>\n",
       "      <td>Guilherme Mendonça de Moraes; Edgard Costa Oli...</td>\n",
       "      <td>2019</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>28</th>\n",
       "      <td>Prefácio</td>\n",
       "      <td>Fernando Castor; Igor Scaliante Wiese</td>\n",
       "      <td>2019</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>29</th>\n",
       "      <td>Uma análise da relação entre code smells e dív...</td>\n",
       "      <td>Felipe Gustavo de S. Gomes; Thiago Souto Mende...</td>\n",
       "      <td>2019</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>30</th>\n",
       "      <td>Clustering Similarity Measures for Architectur...</td>\n",
       "      <td>Douglas E. U. Silva; Roberto A. Bittencourt; R...</td>\n",
       "      <td>2019</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>31</th>\n",
       "      <td>How Workspaces Influence Software Development?...</td>\n",
       "      <td>Victor G. J. Costa; Cesár França</td>\n",
       "      <td>2019</td>\n",
       "    </tr>\n",
       "    <tr>\n",
       "      <th>32</th>\n",
       "      <td>Um relato sobre a migração de uma plataforma d...</td>\n",
       "      <td>Adriano L. Cândido; Fernando A. M. Trinta; Pau...</td>\n",
       "      <td>2019</td>\n",
       "    </tr>\n",
       "  </tbody>\n",
       "</table>\n",
       "</div>"
      ],
      "text/plain": [
       "                                                title  \\\n",
       "0   How do Technical Factors Affect Developers in ...   \n",
       "1   Uma Investigação da Aplicação de Aprendizado d...   \n",
       "2   O Impacto da Utilização da Ferramenta Pivotal ...   \n",
       "3   Um estudo preliminar sobre o uso de uma arquit...   \n",
       "4   Análise de Sentimentos em Discussões de Issues...   \n",
       "5   BULNER: BUg Localization with word embeddings ...   \n",
       "6   Visualizing the Maintainability of Feature Mod...   \n",
       "7   Analisando Estratégias para Identificação de D...   \n",
       "8   Proposta de uma abordagem para decompor sistem...   \n",
       "9   Data-Flow Analysis Heuristic for Vulnerability...   \n",
       "10  Quero lhe usar! Uma Análise do Público Alvo de...   \n",
       "11  Validação e construção de um dicionário léxico...   \n",
       "12  Contextual Similarity Among Identifier Names: ...   \n",
       "13  DiffMutAnalyze: uma ferramenta para auxiliar a...   \n",
       "14                                       Front Matter   \n",
       "15                                        Back Matter   \n",
       "16  Caracterizando a evolução de software de contr...   \n",
       "17  What do software team managers want from a ski...   \n",
       "18  Minerando Motivações para Aplicação de Extract...   \n",
       "19               Investigating vulnerability datasets   \n",
       "20  Revealing Developers’ Arguments on Validating ...   \n",
       "21  Uma Análise da Co-Evolução de Teste em Projeto...   \n",
       "22  BOHR - Uma Ferramenta para a Identificação de ...   \n",
       "23  Readability and Understandability Scores for S...   \n",
       "24  Say my name! An empirical study on the pronoun...   \n",
       "25         Bad Smells in Javascript - A Mapping Study   \n",
       "26  Assessing the Occurrence of Blocking Operation...   \n",
       "27  Análise e melhoria do processo de reengenharia...   \n",
       "28                                           Prefácio   \n",
       "29  Uma análise da relação entre code smells e dív...   \n",
       "30  Clustering Similarity Measures for Architectur...   \n",
       "31  How Workspaces Influence Software Development?...   \n",
       "32  Um relato sobre a migração de uma plataforma d...   \n",
       "\n",
       "                                              authors  year  \n",
       "0   Caio Steglich; Sabrina Marczak; Rodrigo Santos...  2019  \n",
       "1   Warteruzannan Soyer Cunha; Valter Vieira de Ca...  2019  \n",
       "2   Dorgival Netto; Ana de Holanda; Flavio Neves; ...  2019  \n",
       "3    Marcelo de Rezende Martins; Marco Aurélio Gerosa  2019  \n",
       "4   Gláucya Boechat; Joselito Mota Jr; Ivan Machad...  2019  \n",
       "5   Jacson Rodrigues Barbosa; Ricardo Marcondes Ma...  2019  \n",
       "6   Luan Lima; Anderson Uchôa; Carla Bezerra; Eman...  2020  \n",
       "7   Isabela Oliveira; Humberto T. Marques-Neto; La...  2020  \n",
       "8          Felipe Chateaubriand Brasil; Ricardo Terra  2020  \n",
       "9   Gleyberson Andrade; Elder Cirilo; Vinicius Dur...  2020  \n",
       "10  Willian Braga; Gabriel Menezes; Awdren Fontão;...  2020  \n",
       "11  Hiolanda Menezes; Gláucya Boechat; Joselito Mo...  2020  \n",
       "12                          Remo Gresta; Elder Cirilo  2020  \n",
       "13  Juliana Botelho; Maurício Souza; Vinicius H. S...  2020  \n",
       "14                      Rafael Durelli; Lincoln Rocha  2020  \n",
       "15                      Rafael Durelli; Lincoln Rocha  2020  \n",
       "16  Alan Rodrigues; Allysson Allex Araújo; Matheus...  2021  \n",
       "17  Matheus A. Flauzino; Mauricio R. D. A. Souza; ...  2021  \n",
       "18  Jalisson Henrique; Marcos Dósea; Cláudio Sant’...  2021  \n",
       "19                   Rodrigo Andrade; Vinícius Santos  2021  \n",
       "20  Luis Felipi Junionello; Rafael de Mello; Rober...  2021  \n",
       "21  Charles Miranda; Guilherme Avelino; Pedro Sant...  2021  \n",
       "22       Wendell Mendes; Windson Viana; Lincoln Rocha  2021  \n",
       "23          Carlos Eduardo C. Dantas; Marcelo A. Maia  2021  \n",
       "24                          Remo Gresta; Elder Cirilo  2021  \n",
       "25               Aryclenio Xavier Barros; Eiji Adachi  2021  \n",
       "26                       Willie Lawrence; Eiji Adachi  2021  \n",
       "27  Guilherme Mendonça de Moraes; Edgard Costa Oli...  2019  \n",
       "28              Fernando Castor; Igor Scaliante Wiese  2019  \n",
       "29  Felipe Gustavo de S. Gomes; Thiago Souto Mende...  2019  \n",
       "30  Douglas E. U. Silva; Roberto A. Bittencourt; R...  2019  \n",
       "31                   Victor G. J. Costa; Cesár França  2019  \n",
       "32  Adriano L. Cândido; Fernando A. M. Trinta; Pau...  2019  "
      ]
     },
     "execution_count": 15,
     "metadata": {},
     "output_type": "execute_result"
    }
   ],
   "source": [
    "df = pd.DataFrame(data)\n",
    "df.to_excel('sol.xlsx', index=False)\n",
    "df"
   ]
  }
 ],
 "metadata": {
  "kernelspec": {
   "display_name": "Python 3.10.6 ('vem2004-2022-ipJFqA09')",
   "language": "python",
   "name": "python3"
  },
  "language_info": {
   "codemirror_mode": {
    "name": "ipython",
    "version": 3
   },
   "file_extension": ".py",
   "mimetype": "text/x-python",
   "name": "python",
   "nbconvert_exporter": "python",
   "pygments_lexer": "ipython3",
   "version": "3.10.6"
  },
  "orig_nbformat": 4,
  "vscode": {
   "interpreter": {
    "hash": "e0b4d188c6740b86f22827d7e3ed60f52146a1f8e6f7a564c5dab9fbeb32dd39"
   }
  }
 },
 "nbformat": 4,
 "nbformat_minor": 2
}