As a quality manager for an automotive coatings company, I see many similarities between what the author describes and general manufacturing regarding quality and the solutions.
Having developed departmental applications (and a few company ones), I understand the temptation to defend one's program. It is amazing how users will find ways to do something unexpected. The programmer blaming the user is similar to the design engineer crying customer abuse with a product fails in the field.
The only exception I would take with the article is if the specification was actually wrong. I had a case of this years ago when I was programming an embedded controller in C and the formula I was given by the customer was incorrect. There was no way I could have known that would cause an error.
Question - Has anybody in the software quality field thought about, or used, a variation of a Failure Mode Analysis and Effects (FMEA) tool to improve the quality of the code?
Last Visit: 31-Dec-99 18:00 Last Update: 26-Apr-24 1:12