Applying Inspection to Object‐Oriented Code

The benefits of the object‐oriented paradigm are widely cited. At the same time, inspection is deemed to be the most cost‐effective means of detecting defects in software products. Why then, is there no published experience, let alone quantitative data, on the application of inspection to object‐oriented systems? This paper describes the facilities of the object‐oriented paradigm and the issues that these raise when inspecting object‐oriented code. Several problems are caused by the disparity between the static code structure and its dynamic runtime behaviour. The large number of small methods in object‐oriented systems can also cause problems. This is followed by a description of three areas which may help mitigate problems found. Firstly, the use of various programming techniques may assist in making object‐oriented code easier to inspect. Secondly, improved program documentation can help the inspector understand the code under inspection. Finally, tool support can help the inspector analyse the dynamic behaviour of the code. In conclusion, while both the object‐oriented paradigm and inspection provide excellent benefits on their own, combining the two may be a difficult exercise, requiring extensive support if it is to be successful.