lecture-13-static-2

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

Info iconThis preview shows pages 1–5. 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 Aims for Today To discuss the cost-effectiveness of static verification http://www To describe the program inspection process To show how static analysis tools may be used To describe and discuss the Cleanroom .umsec.umn.edu Spring 2010 CSci 5802 2 software development process
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 Static Verification Involves analysis of source text by humans or softwar or software Can be carried out on ANY documents produced as part of the software process Discovers errors early in the software process Usually more cos effective than testing for Spring 2010 CSci 5802 3 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 $ 100 COST DEFECTS 1 10 Spring 2010 CSci 5802 4 Data from Gilb, T. and Graham, D. Software Inspection . Addison-Wesley, 1993. TIME Requirements Design Code Integration & Test Release Unit Test
Background image of page 2
lecture 13 - Inspections Spring 2010 CSci 5802 3 Inspections Shorten the Schedule $ Without Inspections RESOURCES 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 inspection detected by informal program inspections More than 90% of program errors may be detectable using more rigorous mathematical program verification The error detection process is not confused by the existence of previous error Spring 2010 CSci 5802 6 by the existence of previous errors
Background image of page 3

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 4 What Are Software Inspections? The purpose of software inspections is to detect defects early in the process in order to detect defects early in the process in order to reduce rework and costs, and to increase quality and productivity Software inspection • a formal process for verifying intellectual products (in-process) by manually examining a Spring 2010 CSci 5802 7 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 Goa Identify defects Reach consensus Reach consensus Goal State of Work Product Process/ Measurements Checklists/ Error Detection Raise issues Final draft Work in progress Work in progress Formal/Required Raise issues Informal/ None required Informal/ None required Required/ Defects Not required/ Not required Not required/ Not required Spring 2010 CSci 5802 8 Participants Process Owner classified Moderator;Reader; Recorder; Author; Inspectors Moderator; Independent
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 16

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

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

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