Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Software Disasters

401 views

Published on

Доклад Mitko Mitev на SQA Days-22. 17-18 ноября 2017. Санкт-Петербург, Россия
www.sqadays.com

Published in: Education
  • Be the first to comment

  • Be the first to like this

Software Disasters

  1. 1. Software Disasters
  2. 2. Software Disasters “To err is human, but to really foul things up you need a computer.” – Paul Ehrlich • U.S. economy loses every year approx $60 billion from reworks, lost productivity and actual damages arising in a faulty software. • Failure rate of software projects is between 50% - 80%. • For every 100 projects that start, there are 84 restarts. Software bugs can be annoying, but faulty software can be also expensive, embarrassing, destructive and deadly.
  3. 3. Software Disasters Software Failures 2016 In 2016 there were published: • 1519 stories about software failures. • 548 were separate fails • 363 companies affected. The most common for failures were 3 categories: • Software bugs – 432 • Usability glitch – 38 • Security vulnerability – 78
  4. 4. Software Disasters Software Failures
  5. 5. Software Disasters
  6. 6. Ariane 5 The explosion of the Ariane 5 (1996) • Self destroyed after 36 seconds • Reason: Overflow - trying to save 64 bit data in 16 bit format • Estimated loss: $ 8 billion
  7. 7. Mars Climate Observer Mars Climate Observer Fail (1998) • Crashed due to wrong trajectory • Reason: Wrong units – Imperial (USA) instead of Metric (NASA) • Estimated loss: $ 200 million
  8. 8. Therac - 25 The deadly radiation therapy (1985) • 100 times overdose • Reason: Race condition
  9. 9. Doom days for USA US lack of electricity (2003) Before After Reason: Race condition
  10. 10. Apple Maps Apple Maps go nowhere…fast (2012) • One the most Epic fails: Missing entire towns, Disturbed images, Clouds … • Reason: NOT very well tested mapping • Loss: Reputation damage, Google – 
  11. 11. Black Monday Black Monday (1987) – $ 500 billion
  12. 12. Black Monday Black Monday (1987) – $ 500 billion • Systems crashed leaving investors blind • Reason: Load testing not done properly • Estimated loss: $ 500 billion, 22,6 % of Top 500
  13. 13. Knight Capital Group Knight Capital (2012) – lose it all in 45 minutes • 4 million trades of 397 million shares in 45 min • Reason: NOT tested software installed on 1 of 8 servers. Bid and Ask prices - opposite • Estimated loss: $ 460 million, fines of $ 20 million
  14. 14. Pepsi Bottle Glitch Pepsi Bottle Glitch (1992) Pepsi Philippines launched a promotional activity dubbed as “Number Fever” and offered prizes up to P1 million ($37 000) for holders of bottle caps with the number 349. • 500 000 people claimed the prizes, • Company refused to pay all of them, • Pepsi officials claimed that a computer glitch picked the number by mistake • Pepsi faced more than 1000 criminal and civil suits and lost millions • Angry claimants burnt 37 trucks • Pepsi plant in Davao City was attacked • Grenade killed three persons and caused suspension of the plant’s operation;
  15. 15. Amadeus Amadeus – smack airports across world in Sep 2017 • 125 airlines blocked because of check-in failure • Reason: Bug in Cloud solution • Estimated loss: Unknown
  16. 16. Even more disasters • Intel Pentium floating point division bug • Mariner I Space Probe • Patriot Missile timing bug – 28 dead • AT & T Network down due to Out of service msg • World of Warcraft virus
  17. 17. Why get rid of QAs then? The respondents are 2500 IT professionals, research by Computing
  18. 18. New Trends DevOps? • Time to Market • High Quality • Company Effectiveness
  19. 19. New Trends Is DevOps going to kill QA? The answer is No. In a perfect DevOps world: • everyone is responsible for QA, But: • but not everyone has the knowledge and expertise to do QA right. • only half of the processes are being aligned with what is supposed to be DevOps. Critics say DevOps is good for start-ups, but usually turn out to be a bottleneck for corporations.
  20. 20. Future QAs The shifted role of QAs in Agile and DevOps? • QA owns continuous improvement and quality tracking • not only product, also the process. • Tests are code • release every day or week, no place for manual testing • Mentoring the Developers – in TDD, better test cases
  21. 21. The shifted role of QAs Questions?

×