Please use this identifier to cite or link to this item: https://doi.org/10.21256/zhaw-20483
Full metadata record
DC FieldValueLanguage
dc.contributor.authorPanichella, Sebastiano-
dc.contributor.authorZaugg, Nik-
dc.date.accessioned2020-09-17T09:43:00Z-
dc.date.available2020-09-17T09:43:00Z-
dc.date.issued2020-09-13-
dc.identifier.issn1382-3256de_CH
dc.identifier.issn1573-7616de_CH
dc.identifier.urihttps://digitalcollection.zhaw.ch/handle/11475/20483-
dc.descriptionSUMMARY of the PAPER: This paper investigates the approaches and tools that, from a "developer's point of view", are still needed to facilitate Modern Code Review (MCR) activities. To that end, we empirically elicited a taxonomy of recurrent review change types that characterize MCR. This by (i) qualitatively and quantitatively analyzing review changes/commits of ten open-source projects; (ii) integrating MCR change types from existing taxonomies available from the literature; and (iii) surveying 52 developers to integrate eventually missing change types in the taxonomy. The results of our study highlight that the availability of new emerging development technologies (e.g., cloud-based technologies) and practices (e.g., continuous delivery) has pushed developers to perform additional activities during MCR and that additional types of feedback are expected by reviewers. Our participants provided also recommendations, specified techniques to employ, and highlighted the data to analyze for building recommender systems able to automate the code review activities composing our taxonomy. In summary, this study sheds some more light on the approaches and tools that are still needed to facilitate MCR activities, confirming the feasibility and usefulness of using summarization techniques during MCR activities. We believe that the results of our work represent an essential step for meeting the expectations of developers and supporting the vision of full or partial automation in MCR. REPLICATION PACKAGE: https://zenodo.org/record/3679402#.XxgSgy17Hxg PREPRINT: https://spanichella.github.io/img/EMSE-MCR-2020.pdfde_CH
dc.description.abstractRecent research has shown that available tools for Modern Code Review (MCR) are still far from meeting the current expectations of developers. The objective of this paper is to investigate the approaches and tools that, from a developer's point of view, are still needed to facilitate MCR activities. To that end, we first empirically elicited a taxonomy of recurrent review change types that characterize MCR. The taxonomy was designed by performing three steps: (i) we generated an initial version of the taxonomy by qualitatively and quantitatively analyzing 211 review changes/commits and 648 review comments of ten open-source projects; then (ii) we integrated into this initial taxonomy, topics, and MCR change types of an existing taxonomy available from the literature; finally, (iii) we surveyed 52 developers to integrate eventually missing change types in the taxonomy. Results of our study highlight that the availability of new emerging development technologies (e.g., cloud-based technologies) and practices (e.g., continuous delivery) has pushed developers to perform additional activities during MCR and that additional types of feedback are expected by reviewers. Our participants provided recommendations, specified techniques to employ, and highlighted the data to analyze for building recommender systems able to automate the code review activities composing our taxonomy. We surveyed 14 additional participants (12 developers and 2 researchers), not involved in the previous survey, 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. Thus, with a study involving 21 additional developers, we qualitatively assess the feasibility and usefulness of leveraging natural language feedback (automation considered critical/feasible to implement) in supporting developers during MCR activities. In summary, this study sheds some more light on the approaches and tools that are still needed to facilitate MCR activities, confirming the feasibility and usefulness of using summarization techniques during MCR activities. We believe that the results of our work represent an essential step for meeting the expectations of developers and supporting the vision of full or partial automation in MCRde_CH
dc.language.isoende_CH
dc.publisherSpringerde_CH
dc.relation.ispartofEmpirical Software Engineeringde_CH
dc.rightshttp://creativecommons.org/licenses/by/4.0/de_CH
dc.subjectCode review process and practicede_CH
dc.subjectAutomated software engineeringde_CH
dc.subjectEmpirical studyde_CH
dc.subject.ddc005: Computerprogrammierung, Programme und Datende_CH
dc.titleAn empirical investigation of relevant changes and automation needs in modern code reviewde_CH
dc.typeBeitrag in wissenschaftlicher Zeitschriftde_CH
dcterms.typeTextde_CH
zhaw.departementSchool of Engineeringde_CH
zhaw.organisationalunitInstitut für Angewandte Informationstechnologie (InIT)de_CH
dc.identifier.doi10.1007/s10664-020-09870-3de_CH
dc.identifier.doi10.21256/zhaw-20483-
zhaw.funding.euNode_CH
zhaw.issue6de_CH
zhaw.originated.zhawYesde_CH
zhaw.pages.end4872de_CH
zhaw.pages.start4833de_CH
zhaw.publication.statuspublishedVersionde_CH
zhaw.volume25de_CH
zhaw.publication.reviewPeer review (Publikation)de_CH
zhaw.webfeedSoftware Systemsde_CH
zhaw.author.additionalNode_CH
zhaw.display.portraitYesde_CH
Appears in collections:Publikationen School of Engineering

Files in This Item:
File Description SizeFormat 
2020_Panichella-Zaugg_Empirical-investigation-modern-code-review.pdf4.67 MBAdobe PDFThumbnail
View/Open


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.