Software Inspections and Walkthroughs

Software Inspections and Walkthroughs

1. Inspections

   • Five-step, formal process
     • Current workflow member provides overview
       • Participants prepare by developing understanding of document and look for faults
         • Inspection led by one participant through entire document.
           • Written report completed with 1 day
           • Document goes through rework to fix faults
             • Moderator performs follow-up checking that all faults are fixed and documentation (including reports) are updated
   • Both good for finding faults early in process
   • Inspection Team Team consists of 3 - 6 members
     • Moderator
       • Member of team performing current workflow
         • Member of team performing next workflow
           • SQA team member
             • One person will serve as reader
               • Leads team through the document
               • One person will serve as recorder
                 • Produces report of all possible faults team finds
   • Detailed metrics
     • Is each fault a minor fault or a major fault
       • Is the fault from not meeting the specification or that actual & formal arguments do not match?
         • Where in the project did the fault arise?
           • How many faults were found per document/LOC?
             • How long did it take to find a fault?

2. Walkthroughs

   • Two-step, informal process
   • Walkthrough team ideally has 4 - 6 people
     • Member of team performing current workflow
       • Member of team performing next workflow
         • Member of SQA team
           • Often includes a client
   • Should NOT contain manager, partner, or boss
   • Walkthroughs must be thoroughly prepared
     • Provide items not understood
       • Provide items that appear to be incorrect