© 2000 Hans Schaefer Slide no. 1 Integration between reviews and test Can you save test work after inspections? Self assessment about how you do inspections.

Slides:

Advertisements

Similar presentations

Chapter 24 Quality Management.

Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 2.

The ROI of Testing Presented By: Shaun Bradshaw Questcon Technologies The ROI of Testing Presented By: Shaun Bradshaw Questcon Technologies.

©Ian Sommerville 2000Software Engineering. Chapter 22Slide 1 Chapter 22 Verification and Validation.

Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.

Information systems Integrity Protection. Facts on fraud  UK computer fraud 400 Million £  on companies  avg case £  France.

© 1999, 2005 Hans Schaefer Slide no. 1 Testing in Darkness: Late and without specifications Testing in Darkness How to discover test requirements and stay.

SE 450 Software Processes & Product Metrics Reliability: An Introduction.

Debugging CPSC 315 – Programming Studio Fall 2008.

©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.

Software Development Overview CPSC 315 – Programming Studio Spring 2009.

(c) 2007 Mauro Pezzè & Michal Young Ch 1, slide 1 Software Test and Analysis in a Nutshell.

Software Development Overview CPSC 315 – Programming Studio Spring 2008.

Swami NatarajanJuly 14, 2015 RIT Software Engineering Reliability: Introduction.

 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.

High Level: Generic Test Process (from chapter 6 of your text and earlier lesson) Test Planning & Preparation Test Execution Goals met? Analysis & Follow-up.

1 Software Inspections and Walkthroughs Author: A. Frank Ackerman Presented by Cynthia Johnson EEL6883.

What is a Systematic review?. Systematic review  Combination of the best research projects in a specific area Selecting Identifying Synthesizing  Health.

Software Integration and Documenting

©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.

Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management 1.

©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.

Software Inspections and Walkthroughs By. Adnan khan.

Quality Planning & Defect Estimation

Slide 6.1 CHAPTER 6 TESTING. Slide 6.2 Overview l Quality issues l Nonexecution-based testing l Execution-based testing l What should be tested? l Testing.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Verification and Validation.

University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.

CLEANROOM SOFTWARE ENGINEERING.

Objectives Understand the basic concepts and definitions relating to testing, like error, fault, failure, test case, test suite, test harness. Explore.

CS 501: Software Engineering Fall 1999 Lecture 16 Verification and Validation.

Validation Metrics. Metrics are Needed to Answer the Following Questions How much time is required to find bugs, fix them, and verify that they are fixed?

Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.

Verification and Validation Chapter 22 of Ian Sommerville’s Software Engineering.

Software Testing Course Shmuel Ur

Software testing techniques 2.Verification and validation From I. Sommerville textbook Kaunas University of Technology.

©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.

These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.1.

©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Chapter 19 Verification and Validation.

CS.436 Software Engineering By Ajarn..Sutapart Sappajak,METC,MSIT Chapter 13 Verification and validation Slide 1 1 Chapter 13 Verification and Validation.

Software Testing. What is Testing? The process consisting of all life cycle activities, both static and dynamic, concerned with planning, preparation.

Slide 6.1 © The McGraw-Hill Companies, 2002 Object-Oriented and Classical Software Engineering Fifth Edition, WCB/McGraw-Hill, 2002 Stephen R. Schach

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Software Verification, Validation and Testing.

©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Chapter 19 Verification and Validation.

Verification and Validation

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Bzupages.com Verification and Validation.

Verification and Validation Assuring that a software system meets a user's needs.

Software Engineering, 8th edition Chapter 22 1 Courtesy: ©Ian Somerville 2006 April 27 th, 2009 Lecture # 19 Verification and Validation.

© 2001 Hans Schaefer Slide no. 1 Fast reviews Fast reviews for small immature organizations Hans Schaefer Software Test Consulting N-5281 Valestrandsfossen,

Ensure that the right functions are performed Ensure that the these functions are performed right and are reliable.

1 Software Quality Assurance. 2 Quality Concepts - 1 Variation control is the heart of quality control Software engineers strive to control the – process.

Formal Methods in SE Software Verification Using Formal Methods By: Qaisar Javaid, Assistant Professor Formal Methods1.

Economic Justification. Good Enough Quality Time to market Time to market Time to profit Time to profit.

Software Engineering Lecture 8: Quality Assurance.

Software Engineering 2 Term Project by: Feras Batarseh Nestor Rivera.

SOFTWARE TESTING Sampath Kumar Vuyyuru. INTRODUCTION Software Testing is a way of executing the software in a controlled manner to check whether the software.

References & User group Reference: Software Testing and Analysis Mauro Pezze Software Engineering Ian Sommerville Eight Edition (2007) User group:

©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.

©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 22 Slide 1 Verification and Validation.

Verification and Validation

Software Quality Assurance

CSC 480 Software Engineering

Cleanroom Software Engineering

12 Steps to Useful Software Metrics

Prepared by Stephen M. Thebaut, Ph.D. University of Florida

Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.

Object-Oriented and Classical Software Engineering Fifth Edition, WCB/McGraw-Hill, 2002 Stephen R. Schach

Testing and Inspection Present and Future

Presentation transcript:

© 2000 Hans Schaefer Slide no. 1 Integration between reviews and test Can you save test work after inspections? Self assessment about how you do inspections Integration between reviews and testing Hans Schaefer

© 2000 Hans Schaefer Slide no. 2 Integration between reviews and test Can you cut down test after good reviews and inspections? Can you rely on inspections alone? What is a good inspection? How to know? What to cut down?

© 2000 Hans Schaefer Slide no. 3 Integration between reviews and test Can you rely on inspections alone? NO! You need to measure the FINAL quality. Test finds issues inspections don't find well: Issues that are hidden in the connections between many parts. Performance problems New errors introduced after inspection Surviving errors

© 2000 Hans Schaefer Slide no. 4 Integration between reviews and test Cleanroom Software Engineering and Testing Cleanroom heavily relies on inspections. Inspections replace unit test. System test replaced by statistical usage testing (software reliability engineering). Reasoning: ”If you have no chance to test your unit, you will de better inspections!” But: This has never been verified in large projects. Conclusion: Cleanroom PLUS traditional testing!

© 2000 Hans Schaefer Slide no. 5 Integration between reviews and test What is a good inspection? The right (qualified) people attended They had time to prepare Well led meeting 3 to 7 people Meeting in chunks of <= 2 hours Material met entry criteria Check lists Concentration on MAJOR issues Follow up of issues found People know inspection technique Defect detection percentage known Assess yourself!

© 2000 Hans Schaefer Slide no. 6 Integration between reviews and test How to know inspections were good enough? And the results as well? Inspection database Check against other inspections Experience in how testing goes after good inspections - in YOUR organization! Experience in which defects disappear from testing

© 2000 Hans Schaefer Slide no. 7 Integration between reviews and test What you can cut down after inspections Defect repair time during testing Test re-execution (less faults require less repairs and regression test) Getting the test to execute at all (Start trouble) Some, but not all unit testing Other testing only after experience data available Do more test where inspection found many defects!

© 2000 Hans Schaefer Slide no. 8 Integration between reviews and test Danger If an inspection finds few defects: Maybe the software is good? Maybe the inspection was bad?