software project management -->Software inspection

1. Software Inspection
uploaded by : REHMAT ULLAH

2. Software Inspection
•The software inspection process has become an
important part of the software development cycle
•Meetings during which analysis, designs and code
are reviewed by people other than the original
developer.
•The objectives of the inspection process are to find
errors early in the development cycle

3. Inspection team consist of 3-8 members
Include these roles
Moderator: leads the inspection, schedules
meetings, controls the meetings, reports inspection
results.
It should be trained in how to conduct inspections
Author: maintains the work product being
inspected. The author may answer questions asked
about product during the inspection and he also
looks for defects.

4. Reader: Describes the sections of the work product
to the team as they proceed through the inspection.
The reader may paraphrase what is happening in the
product.
Recorder: classifies and records defects and issues
raised during the inspection.
Inspector: attempts to find errors in the product.
All participants actually are acting as inspectors, in
addition to any other responsibilities.

5. Benefits

6. New perspective
• Findingdefects may be easier for people who
haven't seen the artifact before and don’t have
preconceived ideas about its correctness
Knowledge sharing
• Regarding designs and specific software artifacts
• Regarding defect detection practices

7. Find flaws early
• Can dramatically reduce cost of fixing them
• During detail design – even before code is written
• Or code that does not yet have a test harness
• Or code in which testing has found flaws but root causes
are not understood
Reduce rework and testing effort
• Can reduce overall development effort

8. Testing and inspection cannot find all defects
Testing and inspection do not create quality
Development practices create quality

9. Experience with inspection

10. Raytheon
• Reduced"rework" from 41% of cost to 20% of cost
• Reduced effort to fix integration problems by 80%
IBM
• 1 hour of inspection saved 20 hours of testing
• Saved 82 hours of rework if defects in released product
C. Jones
Design/code inspections remove 50-70% of defects
Testing removes 35%

11. References:
•Jonathan Aldrich
Assistant Professor
Institute for Software Research
School of Computer Science
Carnegie Mellon University
jonathan.aldrich@cs.cmu.edu
+1 412 268 7278
•www.cs.cmu.edu/~aldrich/courses/654-
sp07/slides/2-inspection.pdf
•www.processimpact.com

12. Any Question???

13. Thanks