Michael Fagan Inspection

Michael fagan created the fagan defect free process of which fagan inspections are a key part to address these requirements.

Michael fagan inspection. It is named after michael fagan who is credited with being the inventor of formal software inspections. The company nearly doubled the number of lines of code shipped for system370 software products since 1976 while the number of defects per thousand lines of code was reduced by two thirds michael fagan pictured. When i speak on what works in software engineering i say that the most powerful technique we have. Michael fagan a history of software inspections inspections are now thirty years old and they continue to improve software quality and maintainability reduce time to delivery and lower development costs.

A fagan inspection is a process of trying to find defects in documents such as source code or formal specifications during various phases of the software development process. Software review was originally proposed by michael fagan at ibm in the early 1970s. Michael fagan is one of the giants of software engineering because of his work on inspections. Now 35 years later we need to ask certain key questions.

Fagan s software review and forms of review structures. This is an inspection technique named after michael fagan who developed it in the mid 1970s. It is named after michael fagan who is credited with being the inventor of formal software inspections. Michael fagan first found software inspections yielded a massive productivity improvement when working for ibm in the early 1970s.

Since introducing the inspection process in 1974 ibm achieved significant improvements in quality.