| || |
Error Condition Reviews?
I plan to propose to my company's technical and operations management team, the holding of meetings to try to identify the types of error conditions that one of our systems may encounter in the field and their likelihood of occurrence. And then plan how the system should handle each error.
When I worked in the medical device industry, these meetings were mandatory. They were called FMECA. I think that stood for Failure Mode Effectiveness and Criticality Analysis?
Anyway, just curious if any of you hold these type of error/failure analysis meetings in non-regulated companies and if they are a separate meeting altogether or handled as part of say a design review meeting. I think they should be separate, as they can take a whole hour at least.
Thoughts? Opinions on their value?
Re: Error Condition Reviews?
I've done this as part of JAD sessions when functional specs were being written; the information was included in specs.
I wish every company I worked for held them; I think it's an outstanding idea. Holding a separate meeting just to address error conditions focuses attention on them specifically and I firmly believe the result is better code from the get-go, and less confusion and heated discussion during the testing period.