Understanding and Leveraging Context in Code Review

代码审查，即对源代码更改的手工检查，被认为是软件开发中最有效的QA实践之一，因为它提供了识别软件缺陷和提高软件质量的好处。许多软件公司（例如b谷歌、Microsoft、Shopify、Mozilla）都广泛地采用了代码审查。然而，由于提交的贡献的数量和及时处理它们的需要，许多代码审查过程在本质上变得更加轻量级和不那么正式。审查过程的这种演变增加了让缺陷溜进代码的风险，因为审查者无法检测到所有缺陷。检测缺陷失败的原因之一，以及由此导致的软件质量降低，可以归因于对开发人员工作环境周围环境的理解不足。软件开发环境中的上下文，正如Gail Murphy所定义的，是“关于正在开发的系统以及正在开发系统的环境和过程的信息”。虽然以前的研究广泛地探讨了社会和技术因素对代码审查及其质量的影响，但没有考虑到上下文的概念。哪些类型的上下文与代码审查相关？我们如何捕获、建模和解释各种类型的上下文来支持代码审查任务？我们可以开发什么工具来有效地使用上下文？这个研究计划旨在理解和利用与代码审查相关的各种上下文，以提高其效率和有效性。这项工作的目标是双重的：1)通过从各种开发工件中提取、捕获和建模来更好地理解围绕代码审查过程和实践的上下文，以及2)利用该上下文来开发模型、技术和工具，以支持开发人员的日常任务和活动。这项研究将显著影响加拿大的软件行业，使其在工作过程中更加有效。开发人员在完成日常任务时将得到更好的支持，因为他们的工具将更好地适应与这些任务相关的不同类型的上下文。通过理解和利用代码审查中的上下文，我们的目标是提高过程的效率和有效性，通过减少软件缺陷来增加软件系统的质量，加快开发周期，并提高软件系统的整体可维护性。

Code review, i.e., manual inspection of source code changes, is recognized to be one of the most effective QA practices in software development as it delivers benefits of identifying software defects and improving software quality. Many software companies (e.g., Google, Microsoft, Shopify, Mozilla) have employed code reviews extensively. However, due to the volume of submitted contributions and the need to handle them in a timely manner, many code review processes have become more lightweight and less formal in nature. This evolution of the review process increases the risks of letting defects slip into the code as reviewers are unable to detect all of them. One of the reasons for this failure to detect defects and, as a result, reduced software quality, can be attributed to poor understanding of the context surrounding the developer's working environment. The context in a software development setting, as defined by Gail Murphy, is the "information about the system under development and the environment and process in which the system is being developed". While previous research has extensively explored what factors, both social and technical, impact code review and its quality, the notion of context has not been considered. What kinds of context are relevant to code review? How can we capture, model, and explain various kinds of context to support code review tasks? What tools can we develop to use the context efficiently? This research program aims at understanding and leveraging the kinds of context that are relevant to code review to improve its efficiency and effectiveness. The goal of this work is twofold: 1) to better understand the context surrounding code review processes and practice by extracting, capturing, and modelling it from various development artifacts, and 2) to leverage this context to develop models, techniques, and tools to support developer daily tasks and activities. This research will significantly impact the Canadian software industry by making it more effective in their work processes. Developers will be better supported in completing their daily tasks as their tools will be better tuned to different kinds of context that are relevant to these tasks. By understanding and leveraging context in code review, we aim at improving the efficiency and effectiveness of the process, increasing the quality of the software systems by reducing software defects, speeding up the development cycle, and improving the overall maintainability of the software systems.