The Collage of Devankur Thakur

"It ain't braggin' if you can do it."-Dizzy Dean, 1930's baseball player

  Home  |   Contact  |   Syndication    |   Login
  72 Posts | 83 Stories | 740 Comments | 952 Trackbacks

News

Article Categories

Archives

Post Categories

Image Galleries

Blogs to Read..!

My Other Blog..!

Software Testing Related Links

Ten rules of 'Zero-Defect Software Development' by Steve Pavlina, CEO, Dexterity Software: http://www.dexterity.com/articles/zero-defect-software-development.htm

1. Test your product every day as you develop it, and fix defects as soon as you find them.
2. Review your code regularly.
3. Rewrite poor-quality modules.
4. Assume full responsibility for every bug.
5. Handle change effectively.
6. Rewrite all prototyping code from scratch.
7. Set QA objectives at the beginning of every project.
8. Don't rush debugging work.
9. Treat the quality of your code at the same level of importance as the quality of your product.
10. Learn from every bug; each one represents a mistake that you made.

posted on Tuesday, July 05, 2005 2:13 PM

Feedback

# re: Rules of 'Zero-Defect Software Development' 9/3/2008 7:47 AM Inder P Singh
Is Zero-Defect software development really possible? Can these rules guarantee software with no bugs? How are the following problems handled with these rules?
1. There are problems (incompleteness or inconsistency) in requirements.
2. The software passes all tests but new tests are not developed. Unknown bugs may reside in the software.
3. The users use numerous configurations on which the software is run. The exact distinct configurations are unknown to the developers.
4. Some untested test data values result in problems.

Do we need to contemplate further on the problem of executing a zero-defect software development?

Inder

Post Feedback

Title:
Name:
Email: (never displayed)
Url:
Comments: 
Please add 5 and 3 and type the answer here: