cs427-20 - Software Quality Assurance How can you tell if...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
CS427 20-1 Software Quality Assurance How can you tell if software has high  quality? How can we measure the quality of  software? How can we make sure software has high  quality?
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CS427 20-2 “Quality is free” Quality Effort
Background image of page 2
CS427 20-3 Cost of fixing an error Design Code Dev. Test System Test Field operation 3-6 times Req. 10 times 15-40 times 30-70 times 40-1000 times 10 1 time 100 1000 1
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CS427 20-4 Johnson’s Law If you don’t test for it, your system doesn’t  have it. Is it easy to use?   Easy to maintain?   Does it crash? Does it match the documentation? Does it make customers happy?
Background image of page 4
CS427 20-5 Ways not to improve quality Say “Be more careful!” Say “Quality is important.” Find out whose fault it is and fire him.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CS427 20-6 How to improve quality Measure and compare Determine root cause of problems Create ways to eliminate problems
Background image of page 6
CS427 20-7 If you don’t see it, it doesn’t exist Measure quality over time (metrics) Display in a public place Make quality goals, then check to see if  you meet them.
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CS427 20-8 How to appraise quality Requirements reviews by customers prototyping Analysis and design models formal reviews, inspections Current system bug reports user tests surveys
Background image of page 8
20-9 The story of TeX A detailed history of all errors in TeX can  be found in chapters 10 and 11 of the  book Literate Programming and in chapter  34 of the book Digital Typography by  Donald Knuth. http://c2.com/cgi/ wiki?
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 06/14/2009 for the course CS 427 taught by Professor Jones during the Fall '07 term at University of Illinois at Urbana–Champaign.

Page1 / 29

cs427-20 - Software Quality Assurance How can you tell if...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online