I guess that I agree with all three of you. There are two problems being discussed and both are really problems developers face. When there are errors, bugs, or defects in the software and it does not execute as expected that is a problem. When people use software it can be really messy and they can introduce errors.

The real issue in the development of software is the development of a product that will do what is expected when the correct data and procedure are followed. And at the same time when the human element is introduced to the process it is inherent in the development of the software to "guide" the user into doing it right.

Historically we have people who have called this business Software Engineering. That is not just the applied science of Software Development but it is also the engineering of a process built into the software to motivate or entice the user to do it right. In the development of software we often leave the correct path so cryptic and unclear that the user is at a disadvantage and is lucky if they get it right. We can eliminate some human error, not all and we have to remember but we can eliminate some human error with clearly defined pathways through our software and automating the solutions such that the process tells the user that they are about to really blow it or that they are doing it right.

Problem is that if we seek to develop a solution that is without defect and the process and procedure is perfect we spend far above the normal allowable resources and get into financial problems in our projects.

If I were to state what I think the problem is I would say that the compromise between what we are willing to pay for and what we need to build it correctly, far too often causes the usability and performance of the software to suffer.

M.