1. Prof. Mohamed Batouche batouche@ksu.edu.sa

2. Quality Control

3.  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

4.  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

5.  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

6.  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

7.  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. 8

9.  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

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

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

12.  WILLIAW E. LEWIS, “SOFTWARE TESTING AND CONTINUOUS QUALITY IMPROVEMENT”, THIRD EDITION, CRC Press, 2009.  K. NAIK AND P. TRIPATHY: “SOFTWARE TESTING AND QUALITY ASSURANCE”, WILEY, 2008.  IAN SOMMERVILLE, SOFTWARE ENGINEERING, 8 TH EDITION, 2006.  ADITYA P. MATHUR,“FOUNDATIONS OF SOFTWARE TESTING”, PEARSON EDUCATION, 2009.  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, 2002. 12