Software Reviews - Overview

Slides:



Advertisements
Similar presentations
Software Testing Technique. Introduction Software Testing is the process of executing a program or system with the intent of finding errors. It involves.
Advertisements

Software Testing. Quality is Hard to Pin Down Concise, clear definition is elusive Not easily quantifiable Many things to many people You'll know it when.
Software Project Management Lecture # 11. Outline Quality Management ( chapter 26 - Pressman )  Software reviews  Formal Inspections & Technical Reviews.
Formal Technical Reviews
Static Technique. Static Technique - Review  A way of testing software work products  Program code, requirement spec., design spec.  Test plan, test.
1 reviews8 Software Reviews, Walkthroughs, and Inspections The standard technique to ensure quality in software development.
Code Inspections CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 23, 2003.
Code Inspections CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 22, 2007.
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
1 Software Inspections and Walkthroughs Author: A. Frank Ackerman Presented by Cynthia Johnson EEL6883.
Design Reviews Peer Reviews. Agenda Peer Reviews Participants of Peer Review Preparation for a Peer Review Session The Peer Review Session Post-peer Review.
1 Software Reviews - FTR SWENET Module QUA2. Formal Technical Review u Features – Formal v Scheduled event v Defined procedure v Reported result – Technical.
Software Quality Chapter Software Quality  How can you tell if software has high quality?  How can we measure the quality of software?  How.
Software Inspections and Walkthroughs By. Adnan khan.
CPIS 357 Software Quality & Testing
S oftware Q uality A ssurance Part One Reviews and Inspections.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
S Q A.
Jump to first page (C) 1998, Arun Lakhotia 1 Quality Assurance: Reviews and Walkthroughs Arun Lakhotia University of Southwestern Louisiana Po Box
CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE
Quality Assurance IS 101Y/CMSC 101Y November 12, 2013 Carolyn Seaman University of Maryland Baltimore County.
Software Testing and Maintenance 1 Code Review  Introduction  How to Conduct Code Review  Practical Tips  Tool Support  Summary.
Software Development Quality Practices Code Reviews Inspections Walkthroughs.
Reviews and Inspections. Types of Evaluations Formal Design Reviews conducted by senior personnel or outside experts uncover potential problems Inspections.
1 Ch. 1: Software Development (Read) 5 Phases of Software Life Cycle: Problem Analysis and Specification Design Implementation (Coding) Testing, Execution.
Software Development Problem Analysis and Specification Design Implementation (Coding) Testing, Execution and Debugging Maintenance.
Validate Scope What we have: Requirement Traceability Matrix Verified Deliverables What we do: Inspection What we get: Accepted Deliverables.
Project Management Organization Scheduling 31 January.
© Michael Crosby and Charles Sacker, 2001 Systematic Software Reviews Software reviews are a “quality improvement process for written material”.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.1.
1 540f07reviews9sep25 Pert and Reviews Reviews S&G Chapter 5.
CSE SW Metrics and Quality Engineering Copyright © , Dennis J. Frailey, All Rights Reserved CSE8314M37 8/20/2001Slide 1 SMU CSE 8314 /
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
Hall, Accounting Information Systems, 8e ©2013 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly.
Static and Integration Testing. Static Testing vs Dynamic Testing  To find defects  This testing includes verification process  without executing.
More SQA Reviews and Inspections. Types of Evaluations  Verification Unit Test, Integration Test, Usability Test, etc  Formal Reviews  aka "formal.
SOFTWARE TESTING LECTURE 9. OBSERVATIONS ABOUT TESTING “ Testing is the process of executing a program with the intention of finding errors. ” – Myers.
CX Introduction to Web Programming Testing.
What is a Functional Spec?  Defines what the functionality will be NOT how it will be implemented  Describes features of the software product product's.
Software Reviews Ashima Wadhwa.
Components of software quality assurance system overview
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Review Techniques SEII-Lecture 16
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
CIS 375 Bruce R. Maxim UM-Dearborn
Unit Testing Tomas Žvirgžda IFM-9/2.
System.
Software Engineering (CSI 321)
Components of software quality assurance system overview
Modern Systems Analysis and Design Third Edition
Chapter 6 Initiating and Planning Systems Development Projects
Chapter 4 Systems Planning and Selection
Lecture 12: Chapter 15 Review Techniques
Peer Reviews 11/21/2018.
Lecture 09:Software Testing
Chapter 4 Systems Planning and Selection
Review.
Final Exam Review SWE 3643 Software Testing.
Agile practices for documentation teams
CS240: Advanced Programming Concepts
Lecture 6 Initiating and Planning Systems Development Projects
Applied Software Project Management
Modern Systems Analysis and Design Third Edition
Chapter # 1 Overview of Software Quality Assurance
Requirements Engineering
Software Reviews.
A Simple SQA Plan.
Chapter 10: Testing and Quality Assurance
Chapter 6 Initiating and Planning Systems Development Projects
3. Software Quality Management
Presentation transcript:

Software Reviews - Overview SWENET Module QUA2

Formal Technical Reviews Overview People Process

Reviews and Inspections What are they? What are their benefits? ?

Reviews and Inspections A family of techniques Walkthroughs Inspections Personal reviews Formal technical reviews Review / inspect To examine closely With an eye toward correction or appraisal People (peers) are the examiners

Purpose Catching errors Improving communication Providing Education Sooner More and different Breaking frame of reference Improving communication Crossing organization boundaries Providing Education Making software visible

Results Catching most errors before test Fewer defects after release Review plus test is much cheaper than just test Sample results: 10x reduction in errors reaching test 50 - 80 % total cost reduction Fewer defects after release Substantial cost savings in maintenance

Results Composite data from H-P (R. Grady) Testing efficiency (defects found / hour) System use .21 Black box .282 White box .322 Reading/inspect. 1.057

Inspections Features Implications Team reviews materials separately Team and producers meet to discuss May review selected product aspects only Implications Focus on important issues If you know what they are More material per meeting Less preparation time

Walkthroughs Features Implications Less formal Producer presents or provides information Implications Larger groups can attend (education) More material per meeting Less preparation time Harder to separate Product and presenter Explanation and justification

Personal Review Features Implications Informal Done by the producer Not as objective Available to any developer Different mindset Need for review Product completion

Formal Technical Review Features Formal Scheduled event Defined procedure Reported result Technical Not schedule Not budget Independent review team Producers not present

Formal Technical Review Implications More preparation time Less material per meeting Product must stand or fall on its own

Summary Highly effective technique Low technology Not used nearly enough DO IT! Personal review Do it now for the project Guidelines for report Two copies