Open AccessWill it pass? Predicting the outcome of a source code review
Author(s) -
Çağdaş Evren GEREDE,
Zeki MAZAN
Publication year - 2018
Publication title -
turkish journal of electrical engineering and computer sciences
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.225
H-Index - 30
eISSN - 1303-6203
pISSN - 1300-0632
DOI - 10.3906/elk-1707-173
Subject(s) - code review , computer science , source code , process (computing) , code (set theory) , ask price , quality (philosophy) , maturity (psychological) , outcome (game theory) , risk analysis (engineering) , software quality , software , software development , software engineering , process management , psychology , engineering , business , operating system , programming language , finance , developmental psychology , mathematical economics , philosophy , mathematics , set (abstract data type) , epistemology
It has been observed that allowing source code changes to be made only after source code reviews has a positive impact on the quality and lifetime of the resulting software. In some cases, code review processes take quite a long time and this negatively affects software development costs and employee job satisfaction. Establishing mechanisms that predict what kind of feedback reviewers will provide and what revisions they will ask for can reduce the number of times this problem occurs. Thanks to such mechanisms, developers can improve the maturity of their code change requests before the review process starts. In this way, when they start the review, the process may advance quickly and more smoothly. In this study, as a first step towards this goal, we developed a mechanism to identify whether a change proposal would require any revisions or not for approval.
Accelerating Research
Robert Robinson Avenue,
Oxford Science Park, Oxford
OX4 4GP, United Kingdom
Address
John Eccles HouseRobert Robinson Avenue,
Oxford Science Park, Oxford
OX4 4GP, United Kingdom