DOI: 10.5281/zenodo.3679402
title: spanichella/RP_EMSE_MCR_2019 v.1.0.1 Second release of of the replication Package for the paper "An Empirical Investigation of Relevant Changes and Automation Needs in Modern Code Review".

description: Replication Package for the paper "An Empirical Investigation of Relevant Changes and Automation Needs in Modern Code Review" Structure <pre><code>project_raw_data/ gerrit_review_comments.csv gerrit_review_changes.csv survey_raw_data/ google_forms_survey.pdf google_forms_survey.csv RQ1_taxonomy_mcr/ RQ1_inception_phase/ initial_taxonomy.pdf intermediate_taxonomy.pdf RQ1_definition_phase/ Q1.2_evaluation_survey.csv cram_classified.csv cram.pdf RQ2_automation_needs/ Q2.1-Q2.5_evaluation_survey.xlsx Q2.6-Q2.7_evaluation_survey.xlsx Q2.1-Q2.7_question_index.csv Now "RQ3_automated_support/" contain the results concerning RQ2.1 in the paper. content explained in the README.md file located in "RQ3_automated_support/README.md" </code></pre> Contents of the Replication Package <strong>project-raw-data/</strong> contains the data used for the creation of our taxonomies, it includes information about the ten open-source projects. <code>gerrit_review_comments.csv</code> - information about all in-line review comments used for this paper <code>gerrit_review_changes.csv</code> - information about all patches analyzed that contain the in-line comments <strong>survey_raw_data/</strong> contains information about the survey conducted for the paper. <code>google_forms_survey.pdf</code> - the distributed <em>Google Forms</em> of our survey <code>google_forms_survey.csv</code> - all survey answers obtained from 52 survey participants <strong>RQ1_taxonomy_mcr/</strong> contains information and data about the elicited taxonomies in our paper (RQ1). <strong>RQ1_inception_phase/</strong> <code>initial_taxonomy.pdf</code> - initial taxonomy obtained in the inception phase of our paper <code>intermediate_taxonomy.pdf</code> - intermediate taxonomy after integrating and merging the initial taxonomy with the one by Beller <em>et al</em> [1] <strong>RQ1_definition_phase/</strong> <code>Q1.2_evaluation_survey.csv</code> - relevant survey feedback with additional taxonomy categories integrated into <em>CRAM</em> <code>cram_classified.csv</code> - classified review comments (<code>gerrit_review_comments.csv</code>) into <em>CRAM</em> <code>cram.pdf</code> - <em>CRAM</em> taxonomy <code>cram_classified_with_frequency_information2020.xls</code> - it contain the information used to compute the frequency of CRAM changes, derived by the analysis of the 211 commits <strong>RQ2_automation_needs/</strong> contains the encoded evaluation of the survey question Q2.1-2.7 for RQ2 <code>Q2.1-Q2.5_evaluation_survey.xlsx</code> - the encoded evaluation of the survey questions Q2.1-Q2.5 (used for the <em>Automation Needs</em> Section in the paper) and contains the following sheets: <strong>all Findings</strong>: Very detailed findings matrix distilled from all answers concerning possible automated solutions or general possibilities to achieve automation in MCR. Every feedback was analyzed and decomposed into single findings. These findings are grouped, into categories of our Taxonomy of Code Changes in MCR (CRAM). Red represent in the feedback-text where the corresponding category was distilled from. <strong>unique Findings</strong>: As one participant could mention the same categories/solutions in multiple feedbacks, the following matrix is cleaned of any duplication of participant answers. Multiple feedbacks containing the same information by one participant were removed, leaving only distinct occurances. <strong>aggregated by Solution</strong>: Aggregated feeback clustered into abstracted solutions and the number of times participants mentioned the solution. <strong>aggregated by Taxonomy</strong>: Aggregated feeback grouped by low-level categoried in CRAM. <code>Q2.6-Q2.7_evaluation_survey.xlsx</code> - the encoded evaluation of the survey questions Q2.6-Q2.7 (used for the <em>Automation Needs</em> Section in the paper) and contains the following sheets: <strong>all Findings</strong>: Very detailed findings matrix distilled from all answers concerning possible techniques, approaches and data to achieve automation in MCR. Every feedback was analyzed and decomposed into single findings. These findings are grouped, into categories of our Taxonomy of Code Changes in MCR (CRAM). Red represent in the feedback-text where the corresponding category was distilled from. <strong>unique Findings</strong>: As one participant could mention the same categories/solutions in multiple feedbacks, the following matrix is cleaned of any duplication of participant answers. Multiple feedbacks containing the same information by one participant were removed, leaving only distinct occurances. <strong>aggregated by low-level taxonomy</strong>: Aggregated mentionings of approaches/data by developers in the survey grouped by low-level taxonomy category. <strong>aggregated by high-level taxonomy</strong>: Aggregated mentionings of approaches/data by developers in the survey grouped by high-level taxonomy category. <code>Q2.1-Q2.7_question_index.csv</code> - table of IDs given to each participant-question pair for Q2.1-Q2.7 in order to trace back the feeback. <code>cram_survey-with_criticality_and_feasibility2020.xls</code> and <code>cram_survey-with_relevance_and_completeness_information2020.xls</code>: they contain we results of the survey, involving 14 additional participants (12 developers and 2 researchers), not involved in the aforementioned survey, and performed to qualitatively assess the relevance and completeness of the identified MCR change types as well as assess how critical and feasible to implement are some of the identified techniques to support MCR activities. <strong>RQ2_1_automated_support/</strong> (or <strong>RQ3_automated_support/</strong> )- content explained in the README.md file located in "RP_EMSE_MCR_2019/tree/master/EMSE_MCR_2019/RQ3_automated_support/README.md" References [1] Moritz Beller, Alberto Bacchelli, Andy Zaidman, and Elmar Juergens. 2014. Modern code reviews in open-source projects: which problems do they fix?. In Proceedings of the 11th Working Conference on Mining Software Repositories (MSR 2014). ACM, New York, NY, USA, 202-211. DOI: http://dx.doi.org/10.1145/2597073.2597082