Discussion Locked

RIT press release, defects, & customers

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Tell us what you think about the RIT's recent press release (which quantified the cost impact of software defects to the U.S. economy) and the customers perspectives on software defects, as featured in this week's Application Developer Management newsletter. How are you currently addressing QA issues? How effective is that method? Do you know how much downtime impacts your customers' work?

2 replies

by captb

Good points in the article, but it is becoming more and more a misnomer to refer to "testing" as QA. Quality Assurance refers to the process of software development and related improvements. Quality Control or "testing" is a separate function. Both should be taken into consideration during a development process. QA will address "how" you approach testing. There is no argument on my part that you need testing either by the development staff or a separate QC staff earlier in the process. Take a look at some of Demming's writings on the difference between QA and QC. QC will find the defects but won't prevent them. QA processes will assist you in preventing them before they occur. Testing is definitely a QC function.

by iforesight

I think the study is great. However, the fact that these issues are serious today is one sign amonsgt many many others that the i.T industry has lost and is still loosing fundamental levels of professionalism - that is, it should be doing things right the first time rather than in a amatuer and short term, unethical fashion.

It cannot understand why (well in fact yes I can, but that goes back to ethics and greed etc which we all know a lot about !) it is today that studies like this need tobe done to CONVINCE people to use Quality Management methods. The studies need to be used to determine how methods can be improved not to motivate people to use them.

There is the misguided and naive view that we have to develop software very fast to be competitive and get quick high volume sales, otherwise the company is 'dead'. Seems a very desperate way to run things to me.

I am sure the building industry would love to build architectured houses in one week, but its just not possible.Likewise for INNOVATIVE software development. The fact that quality gets cut shows the expectations are highly unrealistic - its also misleading our customers and therefore is unethical business practice.

However, there is considerable information on good methods for Quality Management of software development. V-testing, X-testing, design reviews, methodology. The sad fact is the majority of the industry today doesnt use them, which is highly embarrasing.

The I.T industry is in a depression and will remain that way until fundamental attitudes and business practices change. Let's hope studies like this facilitate this attitude change so that we see sustainable/ethical (one can't be achieved without the other) business practice emerging.

This discussion is closed to new replies.