Fagan inspection

Fagan inspection defines[citation needed] a process as a certain activity with pre-specified entry and exit criteria.

Minor defects do not threaten the correct functioning of the software, but may be small errors such as spelling mistakes or unaesthetic positioning of controls in a graphical user interface.

[2] Together with the qualitative benefits mentioned above major "cost improvements" can be reached as the avoidance and earlier detection of errors will reduce the amount of resources needed for debugging in later phases of the project.

In practice very positive results have been reported by large corporations such as IBM,[citation needed] indicating that 80% to 90% of defects can be found and savings in resources up to 25% can be reached.

M. Genuchten[5] for example has been researching the usage of an Electronic Meeting System (EMS) to improve the productivity of the meetings with positive results [6] Other researchers propose the usage of software that keeps a database of detected errors and automatically scans program code for these common errors.

Ron Radice, High Quality, Low Cost Software Inspections, Paradoxicon Publishing (September 21, 2001)