lecture-13-static-6 - lecture 13 Inspections Spring 2010...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
lecture 13 - Inspections Spring 2010 CSci 5802 1 CSci 5802 Software Engineering II Inspections Chapter 18 ht Aims for Today To discuss the cost-effectiveness of static verification To describe the program inspection process To show how static analysis tools may be tp://www.umsec.umn.edu Spring 2010 CSci 5802 2 To show how static analysis tools may be used To describe and discuss the Cleanroom software development process Static Verification Involves analysis of source text by humans or software Can be carried out on ANY documents produced as part of the software process Spring 2010 CSci 5802 3 Discovers errors early in the software process Usually more cost-effective than testing for defect detection at the unit and module level Allows defect detection to be combined with other quality checks Software Industry Standard Cost Ratio to Fix a Defect Defects cost less to fix when detected earlier in the process $ DEFECTS 10 100 Spring 2010 CSci 5802 4 Data from Gilb, T. and Graham, D. Software Inspection . Addison-Wesley, 1993. TIME Requirements Design Code Integration & Test Release COST 1 Unit Test Inspections Shorten the Schedule RESOURCES $ Without Inspections With Inspections Spring 2010 CSci 5802 5 Adapted from Fagan, M. “Advances in Software Inspections”, IEEE Transactions on Software Engineering, July 1986 Requirements Design Code Release Unit Test Integration & Test SCHEDULE Static Verification Effectiveness More than 60% of program errors can be detected by informal program inspections More than 90% of program errors may be detectable using more rigorous mathematical Spring 2010 CSci 5802 6 program verification The error detection process is not confused by the existence of previous errors
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
lecture 13 - Inspections Spring 2010 CSci 5802 2 What Are Software Inspections? The purpose of software inspections is to detect defects early in the process in order to reduce rework and costs, and to increase quality and productivity Spring 2010 CSci 5802 7 Software inspection • a formal process for verifying intellectual products (in-process) by manually examining a work product, a piece at a time, by small teams of trained peers to detect defects, to ensure that the product is correct and conforms to standards, product specifications, and requirements What’s the Difference? Characteristics Inspections Reviews Walk-Throughs Goal State of Work Product Identify defects Reach consensus Raise issues Final draft Work in progress Work in progress Reach consensus Raise issues Spring 2010 CSci 5802 8 Process/ Measurements Checklists/ Error Detection Participants Process Owner Formal/Required Informal/ None required Informal/ None required Required/ Defects classified Not required/ Not required Not required/ Not required Moderator;Reader; Recorder; Author; Inspectors Moderator; Independent verification Author Author Author; Reviewers Author; Reviewers Inspection Pre-conditions
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 10/21/2011 for the course CSCI 5802 taught by Professor Heimdahl,m during the Spring '08 term at Minnesota.

Page1 / 6

lecture-13-static-6 - lecture 13 Inspections Spring 2010...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online