This lecture describes the key concepts of review techniques. In this chapter, the following content will be discussed: Multi-aspects concept: transcendental view, user view, manufacturer’s view, product view, value-based view; software quality: effective software process, useful product, add value for producer and user of a software product; software quality models;. | Review Techniques SEII-Lecture 16 Dr. Muzafar Khan Assistant Professor Department of Computer Science CIIT, Islamabad. 1 Recap Multi-aspects concept Transcendental view, user view, manufacturer’s view, product view, value-based view Software quality Effective software process, useful product, add value for producer and user of a software product Software quality models Garvin’s quality dimensions, McCall’s quality factors, ISO 9126 quality model Software quality dilemma Achieving software quality 2 Software Reviews Filter for software process To err is human People are good at catching others’ errors Three steps Point out needed improvements Conform those parts that are OK Achieve technical work of uniform quality without reviews Different types of reviews 3 Cost Impact of Software Defects Defect and fault are synonymous Primary objective is to find errors Primary benefit is early discovery of errors No propagation in next step Design activities introduce 50-65% of all errors Review techniques are 75% effective to uncover design flaws It leads to reduced cost at later stages 4 Defect Amplification Model 5 Figure source: Software Engineering: A Practitioner’s Approach, R. S. Pressman, 7th ed., p. 419 Example – No Reviews 6 Figure source: Software Engineering: A Practitioner’s Approach, R. S. Pressman, 7th ed., p. 419 Example –Reviews Conducted 7 Figure source: Software Engineering: A Practitioner’s Approach, R. S. Pressman, 7th ed., p. 419 Review Metrics and Their Use [1/2] Each action requires dedicated human effort Project effort is finite Need of metrics to assess effectiveness of each action Review metrics Preparation effort (Ep) Number of person-hours prior to actual review Assessment effort (Ep) Number of person-hours required for actual review 8 Review Metrics and Their Use [2/2] Rework effort (Er) Number of person-hours to correct errors uncovered during the review Work product size (WPS) Size of work reviewed . number of UML models Minor errors found . | Review Techniques SEII-Lecture 16 Dr. Muzafar Khan Assistant Professor Department of Computer Science CIIT, Islamabad. 1 Recap Multi-aspects concept Transcendental view, user view, manufacturer’s view, product view, value-based view Software quality Effective software process, useful product, add value for producer and user of a software product Software quality models Garvin’s quality dimensions, McCall’s quality factors, ISO 9126 quality model Software quality dilemma Achieving software quality 2 Software Reviews Filter for software process To err is human People are good at catching others’ errors Three steps Point out needed improvements Conform those parts that are OK Achieve technical work of uniform quality without reviews Different types of reviews 3 Cost Impact of Software Defects Defect and fault are synonymous Primary objective is to find errors Primary benefit is early discovery of errors No propagation in next step Design activities introduce 50-65% of all errors Review .
