This repository has been archived by the owner on Nov 15, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathsol.xml
1771 lines (1771 loc) · 152 KB
/
sol.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://sol.sbc.org.br/lib/pkp/xml/oai2.xsl" ?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/
http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
<responseDate>2022-09-24T20:18:52Z</responseDate>
<request verb="ListRecords" metadataPrefix="oai_dc">https://sol.sbc.org.br/index.php/vem/oai</request>
<ListRecords>
<record>
<header status="deleted">
<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7572</identifier>
<datestamp>2019-09-13T19:11:52Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
</record>
<record>
<header status="deleted">
<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7573</identifier>
<datestamp>2019-09-13T19:11:52Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
</record>
<record>
<header status="deleted">
<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7574</identifier>
<datestamp>2019-09-13T19:11:52Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
</record>
<record>
<header status="deleted">
<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7575</identifier>
<datestamp>2019-09-13T19:11:52Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
</record>
<record>
<header status="deleted">
<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7576</identifier>
<datestamp>2019-09-13T19:11:52Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
</record>
<record>
<header status="deleted">
<identifier>oai:ojs2.sbc-srv01.nuvem.ufrgs.br:article/7577</identifier>
<datestamp>2019-09-13T19:11:52Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/7586</identifier>
<datestamp>2021-10-26T18:25:44Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">How do Technical Factors Affect Developers in Mobile Software Ecosystems</dc:title>
<dc:title xml:lang="pt-BR">How do Technical Factors Affect Developers in Mobile Software Ecosystems</dc:title>
<dc:creator>Steglich, Caio</dc:creator>
<dc:creator>Marczak, Sabrina</dc:creator>
<dc:creator>Santos, Rodrigo</dc:creator>
<dc:creator>Guerra, Luiz</dc:creator>
<dc:creator>Mosmann, Luiz</dc:creator>
<dc:creator>de Souza, Cleidson</dc:creator>
<dc:creator>Figueira Filho, Fernando</dc:creator>
<dc:creator>Perin, Marcelo</dc:creator>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2019-09-25</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7586</dc:identifier>
<dc:identifier>10.5753/vem.2019.7586</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2019</dc:source>
<dc:language>eng</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7586/7461</dc:relation>
<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>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/7587</identifier>
<datestamp>2021-10-26T18:25:44Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<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>
<dc:creator>Soyer Cunha, Warteruzannan</dc:creator>
<dc:creator>Vieira de Camargo, Valter</dc:creator>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2019-09-25</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7587</dc:identifier>
<dc:identifier>10.5753/vem.2019.7587</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2019</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7587/7462</dc:relation>
<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>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/7588</identifier>
<datestamp>2021-10-26T18:25:44Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<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>
<dc:creator>Netto, Dorgival</dc:creator>
<dc:creator>de Holanda, Ana</dc:creator>
<dc:creator>Neves, Flavio</dc:creator>
<dc:creator>Rocha, Cloves</dc:creator>
<dc:creator>Bastos, Helena</dc:creator>
<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>
<dc:description xml:lang="pt-BR">Esta pesquisa visa analisar a influência que a ferramenta de monitoração de desempenho Pivotal tem na relação entre os membros de um time ágil de desenvolvimento. Foi realizado um estudo de caso de cunho etnográfico em uma empresa de desenvolvimento de software, tendo como unidade de análise os membros do time e o gerente de projetos. Identificamos que a ferramenta compartilha com todos as informações, cronogramas e desempenho de cada membro da equipe, permitindo que todos possam acompanhar as etapas do projeto. Além disso, o espírito de união e compartilhamento de conhecimento trazem a sensação de confiança e satisfação entre os indivíduos do time.</dc:description>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2019-09-25</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7588</dc:identifier>
<dc:identifier>10.5753/vem.2019.7588</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2019</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7588/7463</dc:relation>
<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>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/7589</identifier>
<datestamp>2021-10-26T18:25:44Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<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>
<dc:creator>de Rezende Martins, Marcelo</dc:creator>
<dc:creator>Gerosa, Marco Aurélio</dc:creator>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2019-09-25</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7589</dc:identifier>
<dc:identifier>10.5753/vem.2019.7589</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2019</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7589/7464</dc:relation>
<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>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/7579</identifier>
<datestamp>2021-10-26T18:25:44Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="pt-BR">Análise de Sentimentos em Discussões de Issues Reabertas do Github</dc:title>
<dc:creator>Boechat, Gláucya</dc:creator>
<dc:creator>Mota Jr, Joselito</dc:creator>
<dc:creator>Machado, Ivan</dc:creator>
<dc:creator>Mendonça, Manoel</dc:creator>
<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>
<dc:description xml:lang="pt-BR">O comportamento de issues reabertas é uma percepção a ser estudada para analisar o impacto das discussões na continuidade da manutenção de projetos de software. A análise de sentimentos apresenta-se como uma poderosa técnica para auxiliar tal análise. Neste estudo, analisamos 12.996 issues reabertas, contendo discussões, de 80 projetos do Github. Com base na análise dessa massa de dados históricos, buscamos analisar se uma issue fechada tende a ser reaberta a partir da análise de sentimentos das discussões dessa issue. As análises são realizadas através do grau de sentimento dos textos dos comentá- rios das issues. A ferramenta SentiStrength, com suporte aos léxicos da á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 discussões pode afetar diretamente o ciclo de vida da issue, inclusive com suporte à predição sobre a reabertura das issues.</dc:description>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2019-09-25</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7579</dc:identifier>
<dc:identifier>10.5753/vem.2019.7579</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2019</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7579/7454</dc:relation>
<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>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/7580</identifier>
<datestamp>2021-10-26T18:25:44Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">BULNER: BUg Localization with word embeddings and NEtwork Regularization</dc:title>
<dc:title xml:lang="pt-BR">BULNER: BUg Localization with word embeddings and NEtwork Regularization</dc:title>
<dc:creator>Rodrigues Barbosa, Jacson</dc:creator>
<dc:creator>Marcondes Marcacini, Ricardo</dc:creator>
<dc:creator>Britto, Ricardo</dc:creator>
<dc:creator>Soares, Frederico</dc:creator>
<dc:creator>Rezende, Solange</dc:creator>
<dc:creator>M. R. Vincenzi, Auri</dc:creator>
<dc:creator>E. Delamaro, Márcio</dc:creator>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2019-09-25</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/7580</dc:identifier>
<dc:identifier>10.5753/vem.2019.7580</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2019</dc:source>
<dc:language>eng</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/7580/7455</dc:relation>
<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>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/14522</identifier>
<datestamp>2021-10-26T18:14:18Z</datestamp>
<setSpec>vem:ART2</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">Visualizing the Maintainability of Feature Models in SPLs</dc:title>
<dc:title xml:lang="pt-BR">Visualizing the Maintainability of Feature Models in SPLs</dc:title>
<dc:creator>Lima, Luan</dc:creator>
<dc:creator>Uchôa, Anderson</dc:creator>
<dc:creator>Bezerra, Carla</dc:creator>
<dc:creator>Coutinho, Emanuel</dc:creator>
<dc:creator>Rocha, Lincoln</dc:creator>
<dc:subject xml:lang="en-US">Feature model</dc:subject>
<dc:subject xml:lang="en-US">Visualization</dc:subject>
<dc:subject xml:lang="en-US">Maintainability</dc:subject>
<dc:subject xml:lang="pt-BR">Feature model</dc:subject>
<dc:subject xml:lang="pt-BR">Visualization</dc:subject>
<dc:subject xml:lang="pt-BR">Maintainability</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2020-10-19</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14522</dc:identifier>
<dc:identifier>10.5753/vem.2020.14522</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2020</dc:source>
<dc:language>eng</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14522/14368</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/14523</identifier>
<datestamp>2021-10-26T18:14:18Z</datestamp>
<setSpec>vem:ART2</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">Analyzing Technical Debt Identification Strategies</dc:title>
<dc:title xml:lang="pt-BR">Analisando Estratégias para Identificação de Dívidas Técnicas</dc:title>
<dc:creator>Oliveira, Isabela</dc:creator>
<dc:creator>Marques-Neto, Humberto T.</dc:creator>
<dc:creator>Xavier, Laerte</dc:creator>
<dc:subject xml:lang="en-US">Technical Debt</dc:subject>
<dc:subject xml:lang="en-US">Self-Admitted Technical Debt</dc:subject>
<dc:subject xml:lang="en-US">SonarQube</dc:subject>
<dc:subject xml:lang="en-US">SATD</dc:subject>
<dc:subject xml:lang="pt-BR">Dívida Técnica</dc:subject>
<dc:subject xml:lang="pt-BR">Débito Técnico Admitido</dc:subject>
<dc:subject xml:lang="pt-BR">SonarQube</dc:subject>
<dc:subject xml:lang="pt-BR">SATD</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2020-10-19</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14523</dc:identifier>
<dc:identifier>10.5753/vem.2020.14523</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2020</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14523/14369</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/14524</identifier>
<datestamp>2021-10-26T18:14:18Z</datestamp>
<setSpec>vem:ART2</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">Towards an approach to decompose monolithic systems in microservices</dc:title>
<dc:title xml:lang="pt-BR">Proposta de uma abordagem para decompor sistemas monolíticos em microsserviços</dc:title>
<dc:creator>Brasil, Felipe Chateaubriand</dc:creator>
<dc:creator>Terra, Ricardo</dc:creator>
<dc:subject xml:lang="en-US">Architecture</dc:subject>
<dc:subject xml:lang="en-US">Microservices</dc:subject>
<dc:subject xml:lang="en-US">Monolithic</dc:subject>
<dc:subject xml:lang="en-US">Microservices decomposition</dc:subject>
<dc:subject xml:lang="pt-BR">Arquitetura</dc:subject>
<dc:subject xml:lang="pt-BR">Microsserviços</dc:subject>
<dc:subject xml:lang="pt-BR">Monolítico</dc:subject>
<dc:subject xml:lang="pt-BR">Extração de microsserviços</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2020-10-19</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14524</dc:identifier>
<dc:identifier>10.5753/vem.2020.14524</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2020</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14524/14370</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/14525</identifier>
<datestamp>2021-10-26T18:14:18Z</datestamp>
<setSpec>vem:ART2</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">Data-Flow Analysis Heuristic for Vulnerability Detection on Configurable Systems</dc:title>
<dc:title xml:lang="pt-BR">Data-Flow Analysis Heuristic for Vulnerability Detection on Configurable Systems</dc:title>
<dc:creator>Andrade, Gleyberson</dc:creator>
<dc:creator>Cirilo, Elder</dc:creator>
<dc:creator>Durelli, Vinicius</dc:creator>
<dc:creator>Cafeo, Bruno</dc:creator>
<dc:creator>Adachi, Eiji</dc:creator>
<dc:subject xml:lang="en-US">Vulnerability Detection</dc:subject>
<dc:subject xml:lang="en-US">Software Product Lines</dc:subject>
<dc:subject xml:lang="en-US">Sampling Strategies</dc:subject>
<dc:subject xml:lang="pt-BR">Vulnerability Detection</dc:subject>
<dc:subject xml:lang="pt-BR">Software Product Lines</dc:subject>
<dc:subject xml:lang="pt-BR">Sampling Strategies</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2020-10-19</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14525</dc:identifier>
<dc:identifier>10.5753/vem.2020.14525</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2020</dc:source>
<dc:language>eng</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14525/14371</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/14526</identifier>
<datestamp>2021-10-26T18:14:18Z</datestamp>
<setSpec>vem:ART3</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">I want to use this! An analysis of the target audience of code samples.</dc:title>
<dc:title xml:lang="pt-BR">Quero lhe usar! Uma Análise do Público Alvo de Code Samples</dc:title>
<dc:creator>Braga, Willian</dc:creator>
<dc:creator>Menezes, Gabriel</dc:creator>
<dc:creator>Fontão, Awdren</dc:creator>
<dc:creator>Hora, André</dc:creator>
<dc:creator>Cafeo, Bruno</dc:creator>
<dc:subject xml:lang="en-US">Code Samples</dc:subject>
<dc:subject xml:lang="en-US">Stack Overflow</dc:subject>
<dc:subject xml:lang="en-US">Reputation</dc:subject>
<dc:subject xml:lang="en-US">Mining Software Repositories</dc:subject>
<dc:subject xml:lang="en-US">SECO</dc:subject>
<dc:subject xml:lang="pt-BR">Code Sample</dc:subject>
<dc:subject xml:lang="pt-BR">Stack Overflow</dc:subject>
<dc:subject xml:lang="pt-BR">Reputation</dc:subject>
<dc:subject xml:lang="pt-BR">Mineração de repósitorios de software</dc:subject>
<dc:subject xml:lang="pt-BR">ECOS</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2020-10-19</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14526</dc:identifier>
<dc:identifier>10.5753/vem.2020.14526</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2020</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14526/14372</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/14527</identifier>
<datestamp>2021-10-26T18:14:18Z</datestamp>
<setSpec>vem:ART3</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">Validation and construction of a lexical dictionary to assist sentiment analysis in software project repositories</dc:title>
<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>
<dc:creator>Menezes, Hiolanda</dc:creator>
<dc:creator>Boechat, Gláucya</dc:creator>
<dc:creator>Mota Jr, Joselito</dc:creator>
<dc:creator>Machado, Ivan</dc:creator>
<dc:subject xml:lang="en-US">Software Engineering</dc:subject>
<dc:subject xml:lang="en-US">software maintenance</dc:subject>
<dc:subject xml:lang="en-US">sentiment analysis</dc:subject>
<dc:subject xml:lang="en-US">lexicon dictionary</dc:subject>
<dc:subject xml:lang="en-US">polarity</dc:subject>
<dc:subject xml:lang="en-US">validation</dc:subject>
<dc:subject xml:lang="pt-BR">Engenharia de software</dc:subject>
<dc:subject xml:lang="pt-BR">manutenção de software</dc:subject>
<dc:subject xml:lang="pt-BR">Análise de Sentimentos</dc:subject>
<dc:subject xml:lang="pt-BR">polaridade</dc:subject>
<dc:subject xml:lang="pt-BR">dicionário léxico</dc:subject>
<dc:subject xml:lang="pt-BR">validação</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2020-10-19</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14527</dc:identifier>
<dc:identifier>10.5753/vem.2020.14527</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2020</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14527/14373</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/14528</identifier>
<datestamp>2021-10-26T18:14:18Z</datestamp>
<setSpec>vem:ART3</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">Contextual Similarity Among Identifier Names: An Empirical Study</dc:title>
<dc:title xml:lang="pt-BR">Contextual Similarity Among Identifier Names: An Empirical Study</dc:title>
<dc:creator>Gresta, Remo</dc:creator>
<dc:creator>Cirilo, Elder</dc:creator>
<dc:subject xml:lang="en-US">Identifier names</dc:subject>
<dc:subject xml:lang="en-US">Semantic Similarity</dc:subject>
<dc:subject xml:lang="en-US">Word Embedding</dc:subject>
<dc:subject xml:lang="en-US">Empirical Study</dc:subject>
<dc:subject xml:lang="pt-BR">Identifier names</dc:subject>
<dc:subject xml:lang="pt-BR">Semantic Similarity</dc:subject>
<dc:subject xml:lang="pt-BR">Word Embedding</dc:subject>
<dc:subject xml:lang="pt-BR">Empirical Study</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2020-10-19</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14528</dc:identifier>
<dc:identifier>10.5753/vem.2020.14528</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2020</dc:source>
<dc:language>eng</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14528/14374</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/14529</identifier>
<datestamp>2021-10-26T18:14:18Z</datestamp>
<setSpec>vem:ART3</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">DiffMutAnalyze: A tool to assist the analysis of equivalent mutants in mutation test teaching</dc:title>
<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>
<dc:creator>Botelho, Juliana</dc:creator>
<dc:creator>Souza, Maurício</dc:creator>
<dc:creator>Durelli, Vinicius H. S.</dc:creator>
<dc:creator>Durelli, Rafael S.</dc:creator>
<dc:subject xml:lang="en-US">Software testing</dc:subject>
<dc:subject xml:lang="en-US">Mutation Test</dc:subject>
<dc:subject xml:lang="en-US">Mutation analysis</dc:subject>
<dc:subject xml:lang="en-US">DiffMutAnalyze</dc:subject>
<dc:subject xml:lang="en-US">Software testing for education</dc:subject>
<dc:subject xml:lang="pt-BR">Teste de Software</dc:subject>
<dc:subject xml:lang="pt-BR">Teste de Mutação</dc:subject>
<dc:subject xml:lang="pt-BR">Mutantes Equivalentes</dc:subject>
<dc:subject xml:lang="pt-BR">DiffMutAnalyze</dc:subject>
<dc:subject xml:lang="pt-BR">Teste de Software na Educação</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2020-10-19</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14529</dc:identifier>
<dc:identifier>10.5753/vem.2020.14529</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2020</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14529/14375</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/14530</identifier>
<datestamp>2021-10-26T18:14:18Z</datestamp>
<setSpec>vem:FRONT</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">Front Matter</dc:title>
<dc:title xml:lang="pt-BR">Front Matter</dc:title>
<dc:creator>Durelli, Rafael</dc:creator>
<dc:creator>Rocha, Lincoln</dc:creator>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2020-10-19</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14530</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2020</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14530/14376</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/14531</identifier>
<datestamp>2021-10-26T18:14:18Z</datestamp>
<setSpec>vem:BACK</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">Back Matter</dc:title>
<dc:title xml:lang="pt-BR">Back Matter</dc:title>
<dc:creator>Durelli, Rafael</dc:creator>
<dc:creator>Rocha, Lincoln</dc:creator>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2020-10-19</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/14531</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2020</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/14531/14377</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/17210</identifier>
<datestamp>2021-10-04T12:37:49Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">Characterizing the software evolution of smart contracts: An exploratory-descriptive study using GitHub and Etherscan</dc:title>
<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>
<dc:creator>Rodrigues, Alan</dc:creator>
<dc:creator>Araújo, Allysson Allex</dc:creator>
<dc:creator>Paixao, Matheus</dc:creator>
<dc:creator>Soares, Pamella</dc:creator>
<dc:subject xml:lang="en-US">Smart Contracts</dc:subject>
<dc:subject xml:lang="en-US">Mining Repositories</dc:subject>
<dc:subject xml:lang="en-US">Ethereum</dc:subject>
<dc:subject xml:lang="en-US">Etherscan</dc:subject>
<dc:subject xml:lang="en-US">GitHub</dc:subject>
<dc:subject xml:lang="pt-BR">Contratos Inteligentes</dc:subject>
<dc:subject xml:lang="pt-BR">Mineração de Repositórios</dc:subject>
<dc:subject xml:lang="pt-BR">Ethereum</dc:subject>
<dc:subject xml:lang="pt-BR">Etherscan</dc:subject>
<dc:subject xml:lang="pt-BR">GitHub</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2021-09-27</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17210</dc:identifier>
<dc:identifier>10.5753/vem.2021.17210</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2021</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17210/17048</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/17211</identifier>
<datestamp>2021-10-04T12:37:49Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">What do software team managers want from a skills identification?</dc:title>
<dc:title xml:lang="pt-BR">What do software team managers want from a skills identification?</dc:title>
<dc:creator>Flauzino, Matheus A.</dc:creator>
<dc:creator>Souza, Mauricio R. D. A.</dc:creator>
<dc:creator>Durelli, Vinicius H. S.</dc:creator>
<dc:creator>Durelli, Rafael S.</dc:creator>
<dc:subject xml:lang="en-US">skill identification</dc:subject>
<dc:subject xml:lang="en-US">development team</dc:subject>
<dc:subject xml:lang="en-US">team management</dc:subject>
<dc:subject xml:lang="pt-BR">skill identification</dc:subject>
<dc:subject xml:lang="pt-BR">development team</dc:subject>
<dc:subject xml:lang="pt-BR">team management</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2021-09-27</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17211</dc:identifier>
<dc:identifier>10.5753/vem.2021.17211</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2021</dc:source>
<dc:language>eng</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17211/17049</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/17212</identifier>
<datestamp>2021-10-04T12:37:49Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">Mining Motivations for Applying Extract Method: A Preliminary Study</dc:title>
<dc:title xml:lang="pt-BR">Minerando Motivações para Aplicação de Extract Method: Um Estudo Preliminar</dc:title>
<dc:creator>Henrique, Jalisson</dc:creator>
<dc:creator>Dósea, Marcos</dc:creator>
<dc:creator>Sant’Anna, Cláudio</dc:creator>
<dc:subject xml:lang="en-US">Refactoring</dc:subject>
<dc:subject xml:lang="en-US">Extract Method</dc:subject>
<dc:subject xml:lang="en-US">Code metrics</dc:subject>
<dc:subject xml:lang="pt-BR">Refatoração</dc:subject>
<dc:subject xml:lang="pt-BR">Extract Method</dc:subject>
<dc:subject xml:lang="pt-BR">Métricas de código</dc:subject>
<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&nbsp;extract&nbsp;method&nbsp;operations in a real system. For this, we conducted an empirical study in which we mined&nbsp;extract&nbsp;method&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&nbsp;extract&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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2021-09-27</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17212</dc:identifier>
<dc:identifier>10.5753/vem.2021.17212</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2021</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17212/17050</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/17213</identifier>
<datestamp>2021-10-04T12:37:49Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">Investigating vulnerability datasets</dc:title>
<dc:title xml:lang="pt-BR">Investigating vulnerability datasets</dc:title>
<dc:creator>Andrade, Rodrigo</dc:creator>
<dc:creator>Santos, Vinícius</dc:creator>
<dc:subject xml:lang="en-US">Vulnerability</dc:subject>
<dc:subject xml:lang="en-US">Datasets</dc:subject>
<dc:subject xml:lang="en-US">Commits</dc:subject>
<dc:subject xml:lang="en-US">CVE</dc:subject>
<dc:subject xml:lang="pt-BR">Vulnerability</dc:subject>
<dc:subject xml:lang="pt-BR">Datasets</dc:subject>
<dc:subject xml:lang="pt-BR">Commits</dc:subject>
<dc:subject xml:lang="pt-BR">CVE</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2021-09-27</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17213</dc:identifier>
<dc:identifier>10.5753/vem.2021.17213</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2021</dc:source>
<dc:language>eng</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17213/17051</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/17214</identifier>
<datestamp>2021-10-04T12:37:49Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">Revealing Developers’ Arguments on Validating the Incidence of Code Smells: A Focus Group Experience</dc:title>
<dc:title xml:lang="pt-BR">Revealing Developers’ Arguments on Validating the Incidence of Code Smells: A Focus Group Experience</dc:title>
<dc:creator>Junionello, Luis Felipi</dc:creator>
<dc:creator>de Mello, Rafael</dc:creator>
<dc:creator>Oliveira, Roberto</dc:creator>
<dc:creator>Sousa, Leonardo</dc:creator>
<dc:creator>López, Alexander</dc:creator>
<dc:creator>Garcia, Alessandro</dc:creator>
<dc:subject xml:lang="en-US">code smells</dc:subject>
<dc:subject xml:lang="en-US">validation</dc:subject>
<dc:subject xml:lang="en-US">focus group</dc:subject>
<dc:subject xml:lang="pt-BR">code smells</dc:subject>
<dc:subject xml:lang="pt-BR">validation</dc:subject>
<dc:subject xml:lang="pt-BR">focus group</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2021-09-27</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17214</dc:identifier>
<dc:identifier>10.5753/vem.2021.17214</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2021</dc:source>
<dc:language>eng</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17214/17052</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/17215</identifier>
<datestamp>2021-10-04T12:37:49Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">An Analysis of Test Co-Evolution on GitHub Software Projects</dc:title>
<dc:title xml:lang="pt-BR">Uma Análise da Co-Evolução de Teste em Projetos de Software no GitHub</dc:title>
<dc:creator>Miranda, Charles</dc:creator>
<dc:creator>Avelino, Guilherme</dc:creator>
<dc:creator>Santos Neto, Pedro</dc:creator>
<dc:creator>da Silva, Victor</dc:creator>
<dc:subject xml:lang="en-US">Co-evolution</dc:subject>
<dc:subject xml:lang="en-US">test</dc:subject>
<dc:subject xml:lang="en-US">mining software repositories</dc:subject>
<dc:subject xml:lang="en-US">GitHub</dc:subject>
<dc:subject xml:lang="pt-BR">Co-evolução</dc:subject>
<dc:subject xml:lang="pt-BR">teste</dc:subject>
<dc:subject xml:lang="pt-BR">mineração de repositório de software</dc:subject>
<dc:subject xml:lang="pt-BR">GitHub</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2021-09-27</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17215</dc:identifier>
<dc:identifier>10.5753/vem.2021.17215</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2021</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17215/17053</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/17216</identifier>
<datestamp>2021-10-04T12:37:49Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">BOHR - A Tool for Identifying Atoms of Confusion in Java Code</dc:title>
<dc:title xml:lang="pt-BR">BOHR - Uma Ferramenta para a Identificação de Átomos de Confusão em Códigos Java</dc:title>
<dc:creator>Mendes, Wendell</dc:creator>
<dc:creator>Viana, Windson</dc:creator>
<dc:creator>Rocha, Lincoln</dc:creator>
<dc:subject xml:lang="en-US">Code Comprehension</dc:subject>
<dc:subject xml:lang="en-US">Atoms of Confusion</dc:subject>
<dc:subject xml:lang="en-US">Static Code Analysis</dc:subject>
<dc:subject xml:lang="pt-BR">Compreensão de Código</dc:subject>
<dc:subject xml:lang="pt-BR">Átomos de Confusão</dc:subject>
<dc:subject xml:lang="pt-BR">Análise Estática de Código</dc:subject>
<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,&nbsp;BOHR&nbsp;- The Atoms of Confusion Hunter is presented, a tool that aims to: (i) assist the identification of AC in&nbsp;Java&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,&nbsp;BOHR&nbsp;is able to detect 8 of the 13 types of AC pointed out by Langhout and Aniche. A preliminary evaluation of the&nbsp;BOHR&nbsp;was conducted on three real open source systems widely adopted by the&nbsp;Java&nbsp;software development community (Picasso, greenDAO and Socket.IO-client&nbsp;Java).&nbsp; The initial results showed that&nbsp;BOHR&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&nbsp;Java&nbsp;Socket.IO-client.</dc:description>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2021-09-27</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>
<dc:identifier>https://sol.sbc.org.br/index.php/vem/article/view/17216</dc:identifier>
<dc:identifier>10.5753/vem.2021.17216</dc:identifier>
<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>
<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>
<dc:source>0000-0000</dc:source>
<dc:source>10.5753/vem.2021</dc:source>
<dc:language>por</dc:language>
<dc:relation>https://sol.sbc.org.br/index.php/vem/article/view/17216/17054</dc:relation>
</oai_dc:dc>
</metadata>
</record>
<record>
<header>
<identifier>oai:sol.sbc.org.br:article/17217</identifier>
<datestamp>2021-10-04T12:37:49Z</datestamp>
<setSpec>vem:ART</setSpec>
</header>
<metadata>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:title xml:lang="en-US">Readability and Understandability Scores for Snippet Assessment: an Exploratory Study</dc:title>
<dc:title xml:lang="pt-BR">Readability and Understandability Scores for Snippet Assessment: an Exploratory Study</dc:title>
<dc:creator>Dantas, Carlos Eduardo C.</dc:creator>
<dc:creator>Maia, Marcelo A.</dc:creator>
<dc:subject xml:lang="en-US">readability</dc:subject>
<dc:subject xml:lang="en-US">understandability</dc:subject>
<dc:subject xml:lang="en-US">code snippets</dc:subject>
<dc:subject xml:lang="en-US">likert</dc:subject>
<dc:subject xml:lang="en-US">code comprehension</dc:subject>
<dc:subject xml:lang="pt-BR">readability</dc:subject>
<dc:subject xml:lang="pt-BR">understandability</dc:subject>
<dc:subject xml:lang="pt-BR">code snippets</dc:subject>
<dc:subject xml:lang="pt-BR">likert</dc:subject>
<dc:subject xml:lang="pt-BR">code comprehension</dc:subject>
<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>
<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>
<dc:publisher xml:lang="pt-BR">Sociedade Brasileira de Computação - SBC</dc:publisher>
<dc:date>2021-09-27</dc:date>
<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
<dc:format>application/pdf</dc:format>