Discussion Locked

Good beginner article - discuss trends

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Bug trackers like PVCS or version control tools like visual source safe (there are many other good ones) solve the problem only upto a point i.e. after the bug has been located.

Tools help in regression testing that reduce bugs.

Unfortunately we are back to where we were 25 years ago. The new technologies do not have the "eperience repository" and what is needed in this new world where "a bug prevention" technology that is not assciated with ISO/CMM processes of QA, peer reviews etc.

So, the ROI is more in cost savings by reducing down time and not prevention of down time.

Is there a cost/benefit analysis of acceptable error like 6 SIGMA?

Any thoughts?

1 reply

by jay eckles

Bug prevention is a classic software engineering/QA topic. I suggest that you read what some of the prominent authors have to say about the subject. Someone in your computer science or software engineering department is bound to have a copy of Roger Pressman's Software Engineering: A Practitioner's Approach. I recommend chapers 8, 25, and 26.

If you're looking for research on Six Sigma, I believe you'll have no trouble whatsoever finding it. A simple google search turns up nearly 400,000hits. There are of course easier ways to filter out serious research from GE marketing material...

Good luck.

Jay
www.jayeckles.com

This discussion is closed to new replies.