李彤《软件工程》教学课件ch27.pptVIP

Quality reviews This is the principal method of validating the quality of a process or of a product. A group examines part or all of a process or system and its documentation to find potential problems. There are different types of review with different objectives Inspections for defect removal (product); Reviews for progress assessment (product and process); Quality reviews (product and standards). Types of review A group of people carefully examine part or all of a software system and its associated documentation. 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. Quality reviews Review functions Quality function - they are part of the general quality management process. Project management function - they provide information for project managers. Training and communication function - product knowledge is passed between development team members. Quality reviews The objective is the discovery of system defects and inconsistencies. Any documents produced in the process may be reviewed. Review teams should be relatively small and reviews should be fairly short. Records should always be maintained of quality reviews. Comments made during the review should be classified No action. No change to the software or documentation is required; Refer for repair. Designer or programmer should correct an identified fault; Reconsider overall design. The problem identified in the review impacts other parts of the design. Some overall judgement must be made about the most cost-effective way of solving the problem; Requirements and specification errors may have to be referred to the client. Review results Software measurement and metrics Software measurement is concerned with deriving a numeric value for an attribute of a software product or process. This allows for objective comparisons between techni