Software Quality Assurance: Lecture 19. This lecture will cover the following: rework and open issues in rework; follow-up and follow-up entry criteria; prevention meeting; data recording and reports; inspection process monitoring; record data from the prevention meeting;...
Software Inspections – – Inspection Process Lecture # 19 Recap and Today’s Lecture: Inspection Process Planning and scheduling Overview Preparation Inspection meeting Analysis meeting Rework Follow-up Prevention meeting Data recording and reports Inspection process monitoring Rework Rework Fixes identified defects and resolves any open issues noted during the inspection In some cases, the repair may require a Change request to be written because of the nature or impact of the defect Open Issues in Rework The open issue is accepted as a defect and repaired The open issue becomes a change request for further investigation The open issue was incorrectly identified as potential defect and is closed as a non-defect Rework: Responsibility The producer is responsible for all open issues, fixing all defects, and writing any change requests Rework: Other Roles The moderator or designee is assigned to discuss open issues with the producer during rework and to come to concurrence with the producer Rework: Entry Criteria The list of defects and open issues is provided to the producer for resolution The moderator or someone assigned meets with the producer to review rework and open issues The inspection report is completed, is on file, and available Rework: Tasks The producer repairs accepted defects identified during the inspection meeting The producer resolves any open issues The moderator meets with the producer to discuss resolutions of open issues Change requests are written for any open issues or defects not resolved during the rework activity Either the minor defect list or marked work products with minor defects noted are used to repair the minor defects Rework: Validation/Verification - The follow-up activity is scheduled; where the rework will be verified by the moderator or assigned designee SQA has reviewed sample results of this activity in the project 10 Data Recording and Reports: Tasks Record data from overview, if held Record data at the inspection meeting, including preparation data Record data at the optional analysis meeting Record data during the follow-up activity, including sign-off to close the inspection 37 Data Recording and Reports: Validation/Verification - The inspection verifies the data at the end of the inspection meeting and optional analysis meeting SQA review sampled reports The producer reviews the report completed by the moderator 38 Data Recording and Reports: Validation/Verification - Data should be considered for this activity; e.g., how much effort is used for recording and reporting 39 Data Recording and Reports: Exit Criteria The data are complete and agreed to by the inspection meeting and analysis meeting participants The data gathered during the follow-up activity are complete and agreed to by the producer and moderator 40 Inspection Process Monitoring 41 Inspection Process Monitoring This activity is held concurrently with other activities and after inspections The purpose is to evaluate the results of the inspection process as performed in the organization and to propose suggestions for improvement 42 Inspection Process Monitoring: Responsibility The inspection process coordinator or SEPG is responsible for monitoring and suggesting improvements 43 Inspection Process Monitoring: Other Roles Management ensures that inspection process monitoring is integrated into the inspection process The inspection process improvement team proposes actions for inspection process improvements based on the monitoring and analysis of the inspection coordinator 44 Inspection Process Monitoring: Entry Criteria Reports and results from inspections over a period of performance are available A coordinator is assigned Resources are allocated for inspection process improvement team 45 Inspection Process Monitoring: Tasks - Gather the inspection process data provided since the last monitoring report Review inspection reports and related data for trends and results against objectives Interview inspection participants to ensure understanding of results and to gather other inputs 46 Inspection Process Monitoring: Tasks - Perform analysis using data from the inspection reports, interviews, and surveys Provide the analysis to the inspection process improvement team for review and proposal to management for inspection process management 47 Inspection Process Monitoring: Validation/Verification - The inspection coordinator performs monitoring actions per agreed periods for analysis The inspection process action improvement team meets per agreed periods for recommendations SQA reviews monitoring activity on a random basis to ensure it is being performed 48 Inspection Process Monitoring: Validation/Verification - Data gathered during this activity How much effort is expended How many proposals for improvement are made How many improvements are put into action 49 Inspection Process Monitoring: Exit Criteria Reports of analysis are developed Actions for improvements are proposed Actions are implemented for inspection process improvements 50 References Software Inspections by Ronald A Radice, Tata-McGraw Hill, 2003 (Chapter 3.8-3.12) 51 ... 18 Follow-up: Tasks - The producer writes any change requests that may be required The moderator completes the inspection report and marks the inspection as closed 19 Follow-up: Validation/Verification... to account for repairs 12 Follow-Up 13 Follow-Up Verifies that all defects and open issues have been adequately fixed, resolved, and closed out 14 Follow-up: Responsibility The moderator... Follow-up: Validation/Verification - Data gathered during this activity How much time was spent in follow-up How many open issues were disputed 21 Follow-up: Exit Criteria Any change