Perspective-based reading of code documents at Robert Bosch GmbH

Despite dramatic changes in software development in the two decades since the term software engineering was coined, software quality deficiencies and cost overruns continue to afflict the software industry. ¹Inspections, developed at IBM by Fagan in the early 1970s [1], can be used to improve upon these problems because they allow the detection and removal of defects after each phase of the software development process. ¹But, in most published inspection processes, individuals performing defect detection are not systematically supported. There, defect detection depends heavily upon factors like chance or experience. Further, there is an ongoing debate in the literature whether or not defect detection is more effective when performed as a group activity and hence should be con ducted in meetings [5],[11],[13],[14]. In this article we introduce Perspective-based Reading (PBR) for code docu ments, a systematic technique to support individual defect detection. ¹PBR offers guidance to indiv idual inspectors for defect detection. This guidance is embod ied within perspective-based algorithmic scenarios which makes individual defect detection independent of experience. ¹ To test this assumption, we tailored and introduced PBR in the inspection proc ess at Robert Bosch GmbH. ¹We conducted two training sessions in the form of a 2x3 fractional factorial experiment in which 11 professional software developers reviewed code documents from three different perspectives. ¹The experimental results are, (1) Perspective-based Reading and the type of document have an influence on individual defect detection, (2) multi-individual inspection meetings were not very useful to detect defects, (3) the overlap of detected defects among inspectors using different perspectives is low, (4) there are no significant differ ences with respect to defect detection between inspectors having experiences in the programming language and/or the application domain and those that do not.