Your SlideShare is downloading. ×
software project management Software inspection
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

software project management Software inspection

495
views

Published on

software project management -->Software inspection

software project management -->Software inspection

Published in: Education

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
495
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Software Inspection uploaded by : REHMAT ULLAH
  • 2. Software Inspection•The software inspection process has become animportant part of the software development cycle•Meetings during which analysis, designs and codeare reviewed by people other than the originaldeveloper.•The objectives of the inspection process are to finderrors early in the development cycle
  • 3. Inspection team consist of 3-8 membersInclude these rolesModerator: leads the inspection, schedulesmeetings, controls the meetings, reports inspectionresults.It should be trained in how to conduct inspectionsAuthor: maintains the work product beinginspected. The author may answer questions askedabout product during the inspection and he alsolooks for defects.
  • 4. Reader: Describes the sections of the work productto the team as they proceed through the inspection.The reader may paraphrase what is happening in theproduct.Recorder: classifies and records defects and issuesraised during the inspection.Inspector: attempts to find errors in the product.All participants actually are acting as inspectors, inaddition to any other responsibilities.
  • 5. Benefits
  • 6. New perspective• Findingdefects may be easier for people whohavent seen the artifact before and don’t havepreconceived ideas about its correctnessKnowledge 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 causesare not understoodReduce rework and testing effort• Can reduce overall development effort
  • 8. Testing and inspection cannot find all defectsTesting and inspection do not create qualityDevelopment 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 productC. JonesDesign/code inspections remove 50-70% of defectsTesting 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