Inspections: In-Person

Software Engineering
1.0x

Inspections: In-Person

Created 3 years ago

Duration 0:05:05
lesson view count 287
Select the file type you wish to download
Slide Content
  1. Inspections: In-Person

    Slide 1 - Inspections: In-Person

    • Emerson Murphy-Hill
    • Creative Commons Attribution 4.0 License.
    • Material Produced by NCSU Software Engineering Faculty.
  2. Software Reviews

    Slide 2 - Software Reviews

    • Process where software artifacts are reviewed by developers, managers, and/or customers for comment or approval [IEEE 1990]
    • Detect errors/inconsistencies
    • Clear intention
    • Design/software meets requirements
    • Developed in uniform manner using standards
  3. Review Benefits

    Slide 3 - Review Benefits

    • More likely to produce high quality, clear work
    • Learn about system and teammates programming techniques
    • Increase “bus number”
  4. Inspection Roles

    Slide 4 - Inspection Roles

    • Author: person who developed artifact
    • Inspectors: inspect artifact. Everyone except the author
    • Moderator: member of the quality assurance team
    • Scribe: takes notes during inspection of issues of interest
    • Reader: person who interprets artifact for inspectors
  5. Inspection (Fagan-style)

    Slide 5 - Inspection (Fagan-style)

    • Inspection Preparation
    • Individual Review
    • Inspection Meeting
    • Defect Correction
    • Substantial Changes?
    • Correction Verification
    • Yes
    • No
  6. Inspection Preparation

    Slide 6 - Inspection Preparation

    • Author prepares artifact and gives to moderator
    • Moderator obtains inspection checklists
    • Moderator distributes materials to inspectors
  7. Individual Review

    Slide 7 - Individual Review

    • Each inspector looks over artifact before inspection meeting
    • Review from check list and own knowledge of the system and requirements
    • Record faults found
    • Record time invested (no more than 2 hours)
    • Reader should prepare to explain their interpretation of the artifact
  8. Inspection Meeting

    Slide 8 - Inspection Meeting

    • Moderator calls meeting to order
    • Reader interprets artifact in sections
    • Inspectors note problems or ask questions
    • Author answers questions
    • Scribes record issues
  9. Inspection Guidelines

    Slide 9 - Inspection Guidelines

    • Do NOT correct defects, instead give a course of action
    • Author answers questions and does NOT justify decisions
    • No personal attacks on authors
    • Focus on important issues, less on style issues
    • Inspection is no longer than 2 hours in one session
  10. What Can You Inspect?

    Slide 10 - What Can You Inspect?

    • Most software artifacts!
    • Requirements
    • Design
    • Black Box Test Plans