Software Inspection And Defect Management
Download as PPT, PDF•10 likes•6,527 views
The document discusses software inspections and defect management. It defines key terms like defects, defect classification, and causes of defects. It explains that rework makes up 44% of project costs and discusses how inspections can help reduce defects and rework. Formal inspections involve individual preparation, overview meetings, review planning, inspection meetings, and follow up action to identify and address defects early. Benefits of inspections include increased productivity, reduced defects, and preparation for subsequent phases.
Software Inspection And Defect Management
- 1. Software Inspection and Defect Management Kubendran G
- 2. Content Introduction Quality Management Defect Defect management Defect Classification Cost to fix Defects Defect Trends Defect Control Inspection – Review Software Inspection Process Case study In Formal Inspection Formal Inspection Roles, Responsibility and Process Benefits of Inspections Conclusions & Questioners Feedback
- 3. Project Efforts Rework is the cost of detection of defects, correction of defects, detection of regression defects and correction of regression defects Effort and Time + Rework Work
- 4. Rework Phase – wise Distribution of Rework Requirements : 1% Preliminary Design : 4% Detailed design : 8% Code & Unit Test : 12% Integration & System Test : 19% Total Rework : 44%
- 5. Overview of Quality Management Reduce Rework to reduce time and costs of Projects Quality Assurance - Prevention of defects Quality Control - Detect defect early Testing can be static and dynamic Testing- Testing application.
- 6. Defect Defect, fault, Problem, Error, Incident, Anomaly, Variance, Failure, Inconsistency, Feature, Bug The software does not do something that the product specifications says it should do The software does something that the product specification says it should not do
- 7. Potential Defects The software does something that the product specifications does not mention The software does not do something the specifications does not mention but should The software is difficult to understand, hard to use, is slow or – in the tester’s eyes – will be viewed by the end user as just plain not right.
- 8. Defects 4 Cs Clear Consistent Correct Complete
- 9. Causes of Defects Omission : I forgot something that I knew I had to do Ignorance : I forgot something, because I did not know, I had to do it Commission : I did something wrong although I knew how to do it right Typography : I typed something wrong though I knew how to do it right
- 10. Causes of Defects Knowledge : I did something wrong because I did not know how to do it Information : I did something wrong because I did not have the right information or information was misleading External : I did nothing wrong. The problem was somewhere else and the defect was introduced by some other person
- 11. Defect classification INSPECTION REPORT Major Defect Minor Defect Potential Defect ( Investigate, Clarify) Q – to be sorted during third hour off-line PROCESS ANALYSIS MEETING REPORT Process Improvement Suggestion Product Improvement Suggestion
- 12. Cost to fix Defects
- 13. Defects Trends Defects Profile without Reviews Design Requirements Code Unit Test Integration Test System Test 20 40 100 50 20 10
- 14. Defects Control Defects Profile with Reviews Design Requirements Code Unit Test Integration Test System Test 5 (20) 10(40) 15(100) 7 (50) 3 (20) 1(10) Reviews Reviews Reviews
- 15. Review - Inspection Review: Presentation of each SW Component to the Group in each Development Phase Discussion and Coordination with other components Goal: Clarification and Accept/Reject Decision Inspection: Quality Improvement Process to the software project Goal: Defect Detection & Defect Prevention
- 16. What is Software Inspection/ Review Review is a team process to identify defects in software work products early and efficiently. Review is a process where a group of people scrutinize a work product with the intention of finding defects. They find the defects, discuss and help eliminate the defects and the cause of defects Review is a powerful, efficient and effective process for defect management
- 17. Software Inspection Process Document Inspection Document Inspection Document Inspection Code Inspection Document Inspection Applying Testing Tools Code Inspection Requirements Design Test Implementation Implementation Test Quality Control Test Plan
- 18. Inspection - Objectives Defect Detection documents are checked for cleanness and consistency against rules Defect Prevention learning from defects found suggesting improvements Benefits
- 19. What is Software Inspection/ Review (cont..) A simple process to identify defects Highly structured meeting Forum for independent evaluation Form of static analysis or static testing Early, in-process validation technique Form of quality and reliability engineering Performed by software engineering
- 20. Objectives of Software Inspection Identify as many defects as possible Identify defects in early stages of life cycle Identify defects before testing and fielding Identify defects cheaply and inexpensively Reduce development and maintenance costs Shorten development cycle time Quantitatively control quality and reliability
- 21. InFormal and Formal Inspection Informal Case Study Formal Case Study
- 22. Formal Inspection Process Log Bugs, agreed by all . Defect Logging Meeting The rework is verified, final inspection data is collected and summarized, and the inspection is officially closed. - Baseline the doc. Follow up Action, Update the bug status. Rework Root cause analysis. Process Analysis Meeting Team members inspect the work individually looking for defects in the work product. Individual Preparation Optional phase where team members who are unfamiliar with the work product to be inspected receive orientation. Overview Meeting Identifies work product to be inspected and sets the inspection schedule. Review Planning Description Inspection Stage
- 23. The Formal Inspection Team Author The individual that assumes the role of Author will be ultimately responsible for updating the work product after the inspection. PM. Moderator The Moderator is responsible for ensuring that the inspection procedures are performed through out the entire inspection process. Lead. Reader The reader is responsible for leading the Inspection Team through the inspection meeting by reading aloud small logical units, paraphrasing where appropriate. Recorder The Recorder will document all defects that arise from the inspection meeting. This documentation will include where the defect was found. Inspector All of the Inspection Team individuals are also considered to play the Inspector role, independent of other roles assigned. Observers or Passive player or QA
- 24. Benefits of Inspections IBM Inspections Resulted in: 23% Increase in coding Productivity 38% Reduction in Defects detected after Unit test AT&T Inspections Resulted in: 14% Increase in Productivity Tenfold Increase in Quality Inspections are 20 times more effective than Testing HP 80% of Defects detected by Inspections were unlikely to be detected by other means
- 25. Conclusions Reviews prepare the ground and stabilize SDP Adaptation of the inspection method for the Environment Gain in quality and experience Appreciated by authors and peers Help for team building in a distributed environment Team Success
- 26. Future Good understanding for the next phase: stabilize inspection process and keep style provide a helpful framework based on experience use it through entire development cycle ‘ lighter’ inspection - faster turnaround time use sampling techniques keep real logging meetings where possible provide metrics stay flexible and efficient Quality http://atddoc.cern.ch/Atlas/DaqSoft/sde/Welcome.html [email protected]
Editor's Notes
- #2: This presentation reports on the evaluation of Review and Software Inspection which is part of the Software Development Process for the Back-end software of the ATLAS Data Acquisition system. .