A Software Inspection is a formal review of a work product by the work product owner and a team of peers looking for errors, omissions, inconsistencies, and areas of confusion in the work product. A formal inspection is performed according to established procedures and schedules. A typical inspection includes the following stages: Planning, Overview Meeting (Kickoff), Preparation, Inspection Meeting, Rework, and Follow-up. A formal inspection has well-defined roles for participants, such as moderator, recorder, reader, author, and inspector.
See also DACS Gold Practice href="https://www.goldpractices.com/practices/fi/index.php">Formal Inspections.
Best Practices (5)
- This is a listing of sources for best practices for software inspections.
Case Studies (4)
- Case studies on the use of software inspections in real programs or academic exercises
Education and Training (12)
- Education and training opportunities in the area of software inspections
Experts (11)
- People recognized as experts or knowledgeable personnel in the area of software inspections.
Literature (3)
- A collection of electronic and hardcopy articles, white papers, books, conference proceedings, journals, and technical reports on Inspections.
Related Resources (6)
- Resources for more information about software inspections and related topics.
Service Providers/Consultants (10)
- Organizations and people who provide various services in the area of software inspections. These services may include training or tools, so the companies listed here may also be listed under those categories under "Inspections".
DACS Gold Practice Initiative
