1 SEG4910 – Projet génie logiciel en fin d’études / Software Engineering Capstone Project Review of Quality Assurance Timothy C. Lethbridge Derived from.

Slides:



Advertisements
Similar presentations
Object Oriented Analysis And Design-IT0207 iiI Semester
Advertisements

By Rick Clements Software Testing 101 By Rick Clements
Unit-V testing strategies and tactics.
SOFTWARE TESTING. Software Testing Principles Types of software tests Test planning Test Development Test Execution and Reporting Test tools and Methods.
Testing and Quality Assurance
Software Testing By Marcin Starzomski :P. What is Testing ? Testing is a process used to help identify the correctness, completeness and quality of developed.
Software Architecture Prof.Dr.ir. F. Gielen
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 6/e (McGraw-Hill 2005). Slides copyright 2005 by Roger Pressman.1.
Chapter 9 Testing the System, part 2. Testing  Unit testing White (glass) box Code walkthroughs and inspections  Integration testing Bottom-up Top-down.
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is software? Software errors, faults and failures Classification.
Program Testing Nelson Padua-Perez Chau-Wen Tseng Department of Computer Science University of Maryland, College Park.
Illinois Institute of Technology
Creator: ACSession No: 12 Slide No: 1Reviewer: CSE300Advanced Software EngineeringJanuary 2006 Testing Strategy CSE300 Advanced Software Engineering University.
 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.
Chapter 11: Testing The dynamic verification of the behavior of a program on a finite set of test cases, suitable selected from the usually infinite execution.
Introduction to Software Testing
SEG4911 – Projet génie logiciel en fin d’études / Software Engineering Capstone Project Thoughts about Agile Design and Release Management Timothy C. Lethbridge.
Software Testing Verification and validation planning Software inspections Software Inspection vs. Testing Automated static analysis Cleanroom software.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Software Testing.
Chapter 8 Software Quality Assurance
 CS 5380 Software Engineering Chapter 8 Testing.
SOFTWARE TESTING Scope of Testing  The dynamic Indian IT industry has always lured the brightest minds with challenging career.
Software Testing The process of operating a system or component under specified conditions, observing and recording the results, and making an evaluation.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Test vs. inspection Part 2 Tor Stålhane. Testing and inspection A short data analysis.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
1 SEG4910 – Projet génie logiciel en fin d’études / Software Engineering Capstone Project Review of Analysis and Iterative Development Timothy C. Lethbridge.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Software Verification, Validation and Testing.
Statistical Software Quality Assurance Implies –Information about defects is collected and categorized –An attempt is made to trace each defect to underlying.
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
1 SOFTWARE TESTING Presented By Abhilash.S  What is Software Testing?  Fundamentals of software Testing Error/Mistake? Defect/Bug/Fault? Failure? 2.
1 Introduction to Software Testing. Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Chapter 1 2.
Anton Krbaťa Ján Budáč  Verification: "Are we building the product right ?„  Validation: "Are we building the right product ?"
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
July, 2008 Impati – Software Test Solutions. July, Contents Testing Service Overview and Approach Test Services and Industries Key Services Offering.
Software Testing and Quality Assurance 1. What is the objectives of Software Testing?
SEG4911 – Projet génie logiciel en fin d’études / Software Engineering Capstone Project The Final Drive to Your A+ Timothy Lethbridge University of Ottawa.
Software reviews Cost impact of software defects Defect amplification model Review metrics and their use – Preparation effort (E p ), assessment effort.
Teaching slides Chapter 9. Chapter 9 Software Testing (Verification & Validation) Introduction Software testing & software engineering methodologies Introduction.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
Software Engineering Lecture 8: Quality Assurance.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Software inspections l Involve people examining the source representation with.
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
Verification vs. Validation Verification: "Are we building the product right?" The software should conform to its specification.The software should conform.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
Software Testing. Software Quality Assurance Overarching term Time consuming (40% to 90% of dev effort) Includes –Verification: Building the product right,
Software Testing Kobla Setriakor Nyomi Faculty Intern (Programming II)
Software Testing Strategies for building test group
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Software Engineering (CSI 321)
Software Testing Basics
Rekayasa Perangkat Lunak Part-13
TESTING TOOLS MANUAL APPROACH BY J.ADI SESHU.
Software Verification and Validation
Chapter 9, Testing.
SUCHITA M.DAKI TYIT(sem v)
Chapter 9: Class Tournament
Software Quality Engineering
Introduction to Software Testing
Lecture 09:Software Testing
Verification and Validation Unit Testing
Static Testing Static testing refers to testing that takes place without Execution - examining and reviewing it. Dynamic Testing Dynamic testing is what.
Baisc Of Software Testing
Chapter 7 Software Testing.
Chapter 10: Testing and Quality Assurance
Presentation transcript:

1 SEG4910 – Projet génie logiciel en fin d’études / Software Engineering Capstone Project Review of Quality Assurance Timothy C. Lethbridge Derived from notes by Liam Peyton

2 Increase customer confidence Improve work processes and efficiency  Save time that would be used fixing defects Enable company to better compete Increase management and investor confidence Quality Assurance and Productivity go Together

3 Cost of corrections Req. Design Code Dev. System Field test test Operation

4 Testing White Box Verification  Test-Driven Development, Code and design Inspections, coverage, formal program verification, invariants Black Box Testing  Requirements scenarios, equivalence classes and boundaries  Unit Testing (Junit, HttpUnit, custom code) Architecture-driven Test driver and test data for each component  System Testing (of released executables) End to end, simulated customer environment  Usability Testing  Acceptance Testing “Real” users doing “real” scenarios (test environment)

Inspection Significant changes should have their designs inspected before implementation Every commit should be inspected by multiple people Periodic walk-throughs of entire system 5

6 Example Sources of Defects Misinterpretation of customer/user needs /communication Unanticipated scenarios never accounted for  Changing operating system or regulations, feature interactions Incomplete or erroneous specifications Intentional deviation from specifications Violation of programming or design standards Error in data representation Inconsistent component interface Error in design logic Incomplete or erroneous testing Inaccurate or incomplete documentation Error in programming language translation of design Weakness in user interface

Tracking and continual improvement Have a goal to reduce the number of high priority defects Track over time Remove defects before adding features Data mine for common causes  Improve processes to reduce common causes Show graphs of accomplishments 7