关于重新检查的工业经验报告 (An Industrial Experience Report on Retro-inspection)

from arxiv, 10 pages. To be published in the Proceedings of the 44th IEEE/ACM International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP 2022)

To reinforce the quality of code delivery, especially to improve future coding quality, one global Information and Communication Technology (ICT) enterprise has institutionalized a retrospective style inspection (namely retro-inspection), which is similar to Fagan inspection but differs in terms of stage, participants, etc. This paper reports an industrial case study that aims to investigate the experiences and lessons from this software practice. To this end, we collected and analyzed various empirical evidence for data triangulation. The results reflect that retro-inspection distinguishes itself from peer code review by identifying more complicated and underlying defects, providing more indicative and suggestive comments. Many experienced inspectors indicate defects together with their rationale behind and offer suggestions for correction and prevention. As a result, retro-inspection can benefit not only quality assurance (like Fagan inspection), but also internal audit, inter-division communication, and competence promotion. On the other side, we identify several lessons of retro-inspection at this stage, e.g., developers' acceptance and organizers' predicament, for next-step improvement of this practice. To be specific, some recommendations are discussed for retro-inspection, e.g., more adequate preparation and more careful publicity. This study concludes that most of the expected benefits of retro-inspection can be empirically confirmed in this enterprise and its value on the progress to continuous maturity can be recognized organization-wide. The experiences on executing this altered practice in a large enterprise provide reference value on code quality assurance to other software organizations.

翻译：为加强代码交付的质量,特别是提高未来的编码质量,一个全球信息和通信技术(信通技术)企业将追溯式检查(即回溯式检查)制度化,这种检查类似于法根检查,但在阶段、参与者等方面存在差异。本文报告工业案例研究,目的是调查从这一软件做法中吸取的经验教训和教训。为此目的,我们收集和分析了数据三角调查的各种经验证据。结果表明,追溯检查通过查明更复杂和潜在的缺陷,提供更具有提示性和建议性的评论,使自己有别于同侪代码审查。许多有经验的检查员指出缺陷及其背后的理由,并提出纠正和预防建议。结果,追溯检查不仅有利于质量保证(如法干检查),还有利于内部审计、跨司交流和增进能力。另一方面,我们找出了本阶段追溯检查的一些经验教训,例如,开发商的接受程度和组织的困境,可以提供这一做法的下一步改进。具体地是,一些建议涉及追溯性参考,以及他们背后的理由和提出纠正和预防的建议。因此,追溯性检查不仅有利于质量保证(如法干检查),还有利于内部审计、跨司沟通沟通和增进能力。另一方面,我们确定本阶段的深思细研究组织的价值。