Inspection seeks to compliment testing. Testing and formal verification help to detect errors and determine mathematical correctness, respectively, but it is possible to have error free (mathematically correct) code that is hard to understand and difficult to maintain. In addition to finding errors in code and related software documents, inspection can also help to determine if coding style guidelines are followed, comments in the code are relevant and of appropriate length, naming conventions are clear and consistent, the code can be easily maintained, etc. When it comes to the cost of building and maintaining large software products, these issues are crucial. To the theorem provers, model-checkers, and automated testing tools, these issues are irrelevant.