Determining Reviewers for Software Inspection

Provided are techniques for an objective determination of the most appropriate person to conduct a software inspection in a large software development project with multiple components, packages and at in which individuals or small groups are each assigned specific modules. Historical information from testing of software commits is stored. An automated and objective analysis of an entire project including the historical information is performed, revealing connections that would otherwise not be apparent between specific potential reviewers and the commit to be reviewed. Based upon the analysis, the system suggests one or more reviewers for the commit to be reviewed. An appropriate code reviewer may he a person with subject matter expertise (SME) in a related are or have more knowledge of a bigger picture and more context of the project, including knowledge of other components.