Using inspections to investigate program correctness

An approach to inspections is proposed that would emphasize the search for correctness. It would hold up to scrutiny to not only what is on the page, but also the thought behind the representation. Inspectors would investigate how the program developed, looking for evidence of disciplined methods in its construction, adequate consideration of the error domain, and the program's ability to withstand years of use and inevitable change. An example inspection is given that uses a program developed according to IBM's design methods. The inspection presents the arguments as a series of questions that the inspectors would ask the author and themselves.<
>