Software Engineering

1
Software Engineering
Dr. Mohamed Fayad, Associate Professor Department
of Computer Science Engineering University of
Nebraska, Lincoln Ferguson Hall, P.O. Box
880115 Lincoln, NE 68588-0115 http//www.cse.unl.e
du/fayad
2
Lesson 35 Software Inspection
2
3
Lesson Objectives

• Learn why inspections are important for creating
  quality objects
• Learn the basics of software inspections
• Understand the differences of inspections vs.
  walkthroughs
• Learn how to run productive value-added
  inspections

4
TESTING WILL NOT CREATE QUALITY OBJECTS
5
THE CRITICAL ROLE OF INSPECTIONS
Defect Worksheet Defects found during
the inspection process.
Inspection Materials
Defect Checklists OOD Diagram trace? etc. etc. etc
.
Defect-Free Materials

• Software Inspections
• Ensure good objects are created early
• Engineer quality instead of test quality
• Increase team building in the new OO culture

6
INSPECTION PROCESS APPLIES TO ALL PHASES OF OOSD

• Software inspections guarantee successful
  completion of each OO software development phase
• Requirements inspection of software object
• Preliminary and Detailed Design of the object
• Implementation and unit test procedures
• Documentation of OO requirements, design, and code

OBJECT-ORIENTED SOFTWARE DEVELOPMENT LIFE CYCLE
Software Manager
Software Requirements Inspection
Preliminary Design Inspection
Software Requirements Analysis
SSE
Software Engineers
Object Preliminary Design
Object Detailed Design
SQA
7
SOFTWARE INSPECTION DEFINITIONS

• Software Inspection -
• Trained personnel follow a defined process with
  the identified goal of finding and reporting
  potential software defects.
• Checklists -
• Tools used to describe the elements of the
  inspection materials that are critical for
  successful exit from the phase.
• Defects -
• Any potential variance from the standard or
  expected practice in an area.
• Defect Worksheet -
• Record of defects found during software
  inspection.

8
SIX STEP INSPECTION PROCESS COVERS OOSD CRITERIA

• 1 Planning inspection material content
• 2 Overview meeting (optional)
• 3 Individual preparation (checklists)
• 4 Inspection meeting (defect worksheet)
• 5 Rework performed by author
• 6 Follow-up verification of rework

9
SOFTWARE INSPECTION VS.WALKTHROUGH

• Software Inspection
• Trained personnel (moderator, reader, inspectors)
• Checklist for inspection roles
• Repeatable process
• Recorded results
• Rework follow-up
• Materials presented by reader
• Walkthrough
• Run by author depend on authors style
• Few traceable results
• No verification of rework
• No specified review criteria (duplication of
  effort)

10
METRICS COLLECTION AND ANALYSIS ENSURES VALUE IS
BEING ADDED

• Increase personnel productivity
• Record Preparation Times
• Track Defect Types by Activity
• Limit Inspection Meeting to Two Hours
• Record Time Spent to Perform Rework
• Review Inspection Process Regularly to Find
  Improvements

11
INSPECTION SUMMARY

• Inspections help engineer quality objects
• Inspections should be applied to all phases of
  object-oriented software development
• Inspections are more rigorous and formal than
  walkthroughs
• Collect metrics to track inspection productivity