Giới thiệu phương pháp kiểm tra Fagan
Fagan Inspection Method WWW.VIETNAM.ECCINTERNATIONAL.COM Workshop on Software Inspection Myths of Peer Reviews Need for Software Inspection Types of Reviews Inspection Team Inspection Process Individual Responsibilities Exercise: Overview Exercise: Preparation Time Exercise: Defect Logging Meeting Exercise: Causal Analysis Meeting Exercise: Summary Presentation Inspection metrics How to make Inspection happen Closing Session M Rajamanickam (Raja) has more than 20 years experience in all facets of Quality Management and Process Improvement. Practitioner of Fagan Inspection for more than 15 years and conducted Inspection training to many prestigious clients in India, Japan and Vietnam Process improvement consultant, who helps clients in the countries like India, USA, Japan, China, Taiwan, Brazil, Australia, Malaysia,Vietnam, etc Visiting faculty in many universities and business schools including Great Lakes Institute of Management, Chennai, India Lean Six Sigma Corporate Champion, Certified Scrum Master, Certified CMMI Lead Appraiser, and a passionate trainer. Earlier jobs include Vice President of Corporate Quality at HCL Technologies and Manager, Quality at Oracle India Holds ME (Industrial Engineering) from PSG College of Technology and Exec MBA from Great Lakes Institute of Management Raja can be reached on his email: mrajamanickam@gmail.com 4 Participate and share reserve your questions at any time Maintain punctuality during the start and breaks No web browsing/mails/skype during the the session pls! Mobiles in silent mode? Don’t Anything else to be added? Let us understand your specific expectations from this workshop Quality Dept Verify that specifications are satisfied Verify conformance to standards Identify deviation from standards and specifications Collect data for improvement Reviews waste lot of time Reviews are costly Hard work alone results in quality Everyone always tries to produce high quality products Reviews can be done only by Senior Staff Please follow the instructions of the faculty 10 Rework Requirement Development Product 11 Source : Software Inspection - An Industry Best Practice, IEEE Computer Society Press, 1996 12 Source : Software Inspection - An Industry Best Practice, IEEE Computer Society Press, 1996 13 Source : Software Inspection - An Industry Best Practice, IEEE Computer Society Press, 1996 14 Catching Defects early in the Development Process is Economical 15 How about Testing? System Test Requirements Integration Test Design Coding Unit Test Testing starts too late in the development process In testing, you find only symptoms, not defects Testing is expensive 16 According to studies, Inspection is three times more effective in finding defect than testing Inspection finds most of the problems testing would find, and does so more efficiently However, some subtle bugs may escape inspection, and could only be detected through testing by executing the software code So, inspection and testing should be considered as complementary processes 17 Without Inspections 20 Requirements 40 Design Code 100 50 Unit Test Integration Test 20 System Test 10 240 Total Defects 10 Defects goes to the customer Source : Software Inspection - An Industry Best Practice, IEEE Computer Society Press, 1996 With Inspections 20 Requirements 10 40 Design 15 Code 100 50 Unit Test Integration Test 20 System Test 10 Reduced Defects (Total 41) Improved Product Quality Reduced Rework Costs Source : Software Inspection - An Industry Best Practice, IEEE Computer Society Press, 1996 Without Inspections Requirements Design Code With Inspections 15 18 145 72 Unit Test Integration Test Reduced Defects (292 – 42) Improved Product Quality Reduced Rework Costs 36 System Test 18 Source : IBM Corp., Software Product Assurance, NY, 1987 Source: A history of Software Inspections – Michal Fagan Introduction of Inspections in each phase of the Development Process reduces Defects and Rework Costs Inspection Process works regardless of o Type of Software o Type of Design Methodology o Programming Language 22 Development productivity improvement (30% to 100%) Calendar time reduction (10% to 30%) Reduction in development effort (9% to 40%) Reduction of testing costs and time Maintenance cost reduction (35% to 65%) 23 Raytheon Reduced "rework" from 41% to 20% Reduced effort to fix integration problems by 80% IBM hour of inspection saved 20 hours of testing Saved 82 hours of rework in released product Inspections Resulted in 23% increase in coding productivity 38% reduction in defects detected after unit test AT & T Inspections Resulted in 10 fold increase in quality 24 IBM Santa Teresa Lab 3.5 hours to find bug with inspection, 15-25 through testing C Jones Design/code inspections remove 50-70% of defects Testing removes 35% Paulket al.: Cost to fix a defect in space shuttle software ◦ $1 if found in inspection ◦ $13 during system test ◦ $92 after delivery HP ◦ 80 % of defects detected by Inspections were unlikely to be detected by other methods 25 Review Use Set the product, not the producer standards to avoid disagreement over style an agenda and maintain it Identify problems, but don’t attempt to solve them Take written notes Limit the number of participants 27 ...Workshop on Software Inspection Myths of Peer Reviews Need for Software Inspection Types of Reviews Inspection Team Inspection Process Individual Responsibilities... Source: A history of Software Inspections – Michal Fagan Introduction of Inspections in each phase of the Development Process reduces Defects and Rework Costs ? ?Inspection Process works regardless... Often used for code reviews Inspections The most beneficial (to be discussed extensively now on) 39 13 40 Quality Dept ? ?Inspection Guidelines ? ?Inspection Teams ? ?Inspection Process Individual