Prof. Mohamed Batouche Quality Control.

Slides:



Advertisements
Similar presentations
Chapter 24 Quality Management.
Advertisements

Chapter 24 Quality Management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management.
Verification and Validation
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #7 Software Engineering.
Stepan Potiyenko ISS Sr.SW Developer.
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is software? Software errors, faults and failures Classification.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
SE 555 Software Requirements & Specification Requirements Validation.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Verification and Validation.
Chapter 24 - Quality Management 1Chapter 24 Quality management.
 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 24 - Quality Management 1Chapter 24 Quality management.
Chapter 24 - Quality Management
1CMSC 345, Version 4/04 Verification and Validation Reference: Software Engineering, Ian Sommerville, 6th edition, Chapter 19.
OHT 4.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Prof. Mohamed Batouche Costs of software quality Introduction  More and more, commercial companies or public organizations are requiring.
Chapter 24 - Quality Management Lecture 1 1Chapter 24 Quality management.
International Software Quality Models ISO
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
CS 4310: Software Engineering
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management 1.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 22Slide 1 Verification and Validation u Assuring that a software system meets a user's.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
S/W Project Management
Product Quality, Testing, Reviews and Standards
Quality Assurance ITEC Rick Price. Expectations This course is not purely a lecture course – Classroom participation is a large portion – Everyone.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Verification and Validation.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management.
Verification and Validation Chapter 22 of Ian Sommerville’s Software Engineering.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 22 Slide 1 Verification and Validation Slightly adapted by Anders Børjesson.
Prof. Mohamed Batouche Software Configuration management.
This chapter is extracted from Sommerville’s slides. Text book chapter
Disciplined Software Engineering Lecture #7 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
Quality Assurance vs Quality Control
Software Testing and Quality Assurance Software Quality Assurance 1.
Prof. Mohamed Batouche Main Components …
SoftwareVerification and Validation
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
This chapter is extracted from Sommerville’s slides. Textbook chapter
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 7 1 Design and Code Reviews - Overview What are design and code.
Quality Management Managing the quality of the software process and products.
1 Chapter 3 1.Quality Management, 2.Software Cost Estimation 3.Process Improvement.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Bzupages.com Verification and Validation.
CHAPTER 9: VERIFICATION AND VALIDATION 1. Objectives  To introduce software verification and validation and to discuss the distinction between them 
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.
©Ian Sommerville Software Engineering, 7th edition. Chapter 22 Slide 1 Verification and Validation with edits by Dan Fleck Coming up: Objectives.
Project management Topic 8 Quality Review. Overview of processes Prepare for Quality Review Questions list Meeting Agenda Review Meeting Sign-off Product.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Verification and Validation with edits by Dan Fleck.
This chapter is extracted from Sommerville’s slides. Textbook chapter 22 1 Chapter 8 Validation and Verification 1.
by: Er. Manu Bansal Deptt of IT Software Quality Assurance.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
Verification and Validation. Topics covered l Verification and validation planning l Program Testing l Software inspections.
Software Quality Control and Quality Assurance: Introduction
CSC 480 Software Engineering
Software Verification and Validation
8.3 Control Quality The process of monitoring and recording results of executing quality activities to assess performance and recommend necessary change.
Quality Management chapter 27.
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Software Quality Engineering
Verification and Validation
Verification and Validation
Chapter 13 Quality Management
Software Testing “If you can’t test it, you can’t design it”
Software Reviews.
Presentation transcript:

Prof. Mohamed Batouche

Quality Control

 Quality control is designed to: detect and correct defects,  whereas quality assurance is oriented toward: preventing them.  Quality assurance is a managerial function that prevents problems by heading them off, and by advising restraint and redirection. 3

 Quality control consists of well-defined checks on a product that are specified in the product quality assurance plan.  For software products, quality control typically includes specification reviews, inspections of code and documents, and checks for user deliverables. 4

 Quality control is defined as the processes and methods used to monitor work and observe whether requirements are met. It focuses on reviews and removal of defects before shipment of products.  This involves checking the software development process to ensure that procedures and standards are being followed.  There are two approaches to quality control  Quality reviews;  Automated software assessment and software measurement. 5

 This is the principal method of validating the quality of a process or of a product.  A group of people carefully examine part or all of a software system and its associated documentation to find potential problems.  Code, designs, specifications, test plans, standards, etc. can all be reviewed.  Software or documents may be 'signed off' at a review which signifies that progress to the next development stage has been approved by management. 6

 There are different types of review with different objectives  Inspections for defect removal (product); - use of checklists  Reviews for progress assessment (product and process); - concerned with plans, costs and schedules  Quality reviews (product and standards). – Ensure that standards have been followed,... 7

8

 The main technique for achieving quality is the software review and walkthrough.  Checklists are list of items that should be checked during the review.  Checklist may contain questions to be answered. 9

Check list for java code:  are any while or if conditions closed with semicolon “;” ?  are all variables declared ?  does every ‘‘{’’ have a matching ‘‘}’’?  does every equality comparison have a double ‘‘=’’? 10

Check list for reviewing software design:  Are all significant functions shown in design?  Are all significant attributes specified in design?  Are all names related to purpose and type and are they unambiguous?  Are all relationships between classes specified?  Do all functions have the data necessary for the function to execute? 11

 WILLIAW E. LEWIS, “SOFTWARE TESTING AND CONTINUOUS QUALITY IMPROVEMENT”, THIRD EDITION, CRC Press,  K. NAIK AND P. TRIPATHY: “SOFTWARE TESTING AND QUALITY ASSURANCE”, WILEY,  IAN SOMMERVILLE, SOFTWARE ENGINEERING, 8 TH EDITION,  ADITYA P. MATHUR,“FOUNDATIONS OF SOFTWARE TESTING”, PEARSON EDUCATION,  D. GALIN, “SOFTWARE QUALITY ASSURANCE: FROM THEORY TO IMPLEMENTATION”, PEARSON EDUCATION, 2004  DAVID GUSTAFSON, “THEORY AND PROBLEMS OF SOFTWARE ENGINEERING”, Schaum’s Outline Series, McGRAW-HILL,