Дмитрий Лапшин, "The importance of TEX and Internal Quality. How explain and “Sell” it to the Client?"
Download as PPTX, PDF0 likes209 views
This document discusses quality and defect removal in software development. It makes three key points: 1) Quality comes at a cost of both time and money, and developers must balance quality with schedules and budgets. Not all defects have equal consequences. 2) Defect prevention upfront is critical and more efficient than detection and removal later. The majority of defects can be removed through requirements reviews, architectural reviews, design reviews, and code reviews. 3) Tools and processes like continuous integration, code reviews, testing, and defect tracking help contain defects and improve efficiency in defect removal. The goal is achieving high defect removal efficiency across requirements, architecture, design and code.
Дмитрий Лапшин, "The importance of TEX and Internal Quality. How explain and “Sell” it to the Client?"
- 1. Click to edit Master title style 1 1
- 2. Click to edit Master title style 2 TEX and Internal Quality
- 3. Click to edit Master title style 3 Quality: Constant or Variable? 3
- 4. Click to edit Master title style 4 4 “QUALITY IS NOT A COMPROMISE IN PROBLEM SOLVING” WHAT “VARIABLE” ARE THEY TALKING ABOUT HERE?!
- 5. Click to edit Master title style 5 A TALE OF TWO CARS 5 $$$ $
- 6. Click to edit Master title style 6 OUT WITH THE BUBBLE, IN WITH THE CRISIS: NO EASY-EASY MONEY ANYMORE 6
- 7. Click to edit Master title style 7 7
- 8. Click to edit Master title style 8 QUALITY IS ABOUT INVESTING MONEY… 8 ROI Threshold
- 9. Click to edit Master title style 9 …AND TIME 9
- 10. Click to edit Master title style 10 COMPETING ON SCHEDULE AND QUALITY 10 P(L) Probability of loss S(L) Size of loss RE Risk exposure
- 11. Click to edit Master title style 11 TAKEAWAYS SO FAR 11 Quality is NOT free (sorry, Mr. Crosby) Not all defects are born equal: Loss of human life is unacceptable… …but easily recoverable loss often is. We are racing against time and money
- 12. Click to edit Master title style 12 REACHING THE SWEET SPOT D e f e c t r e m o v a l e f f i c i e n c y i s k e y t o g e t t i n g t h e r e 12
- 13. Click to edit Master title style 13 WHY IS DEFECT PREVENTION CRITICAL? 13 • 2-3X longer, more than 2X as costly testing schedules. • If defects remain undetected and unremoved until testing starts, it is too late to bring a software project back under control • Prevention and Appraisal activities remove many more defects per Engineer-Hour than Failure activities.
- 14. Click to edit Master title style 14 DEFECT INJECTION AND LEAKAGE 14 User Needs Defect-Free Requirements Defective Requirements Defect-Free Architectural Design Defective Architectural Design Architectural Design based on Defective Requirements Defect-Free Detailed Design Defective Detailed Design Detailed Design based on Defective Req. Detailed Design based on Def. Arch. Defect-Free Code Code based on Defective D.D. Code based on Defective Req. Code based on Defective Arch. D. Defective Code
- 15. Click to edit Master title style 15 FIXING THIS LEAKING PLUMBING 15 Software Defect (Bug) System Fault System Failure Human (Developer) Error Processes Methods Tools Fault Containment Fault Tolerance Reviews Inspections Testing
- 16. Click to edit Master title style 16 TEX TOOLS FOR DEFECT REMOVAL 16 Pre-code • Technical design reviews Post-code • Code reviews • Static code analysis • Unit & integration testing • Testing by developer Enablers • Continuous integration • Gated check-ins / pre-tested commits
- 17. Click to edit Master title style 17 EFFICIENCY HI-SCORE 17 REQUIREMENTS ARCHITECTURE DESIGN CODE REQUIREMENTS TESTING 87% 5% 10% 5% ARCHITECTURE REVIEWS 10% 85% 10% 2,5% TECH DESIGN REVIEWS 14% 10% 87% 7% CODE REVIEWS 15% 12,5% 20% 85% UNIT TESTING 4% 2.5% 7% 35%
- 18. Click to edit Master title style 18 PURITY REQUIRES A FILTER CHAIN 18 Project size Target DRE Small to average 98% Large 95%
- 19. Click to edit Master title style 1919 MEET THE PIPELINE
- 20. Click to edit Master title style 20 L E V E R A G E O R A B S O L U T E E V I L ? 20 TECHNICAL DEBT
- 21. Click to edit Master title style 21 IS THERE A GOOD TECH DEBT? 21 InadvertentDeliberate Reckless Prudent We don’t have time to design! We must ship now and deal with the consequences! What’s layering? Now we know how we should’ve done it Technicaldebtquadrant©2009MartinFowler
- 22. Click to edit Master title style 2222
- 23. Click to edit Master title style 23 HORROR STORY TIME 23
- 24. Click to edit Master title style 24 QUESTIONS?