TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I am trying to determine the standard steps needed in the process of
performing a failure analysis for software product failures/problems
that occur in the field (i.e. at customers' sites).
I am also interested in how to record the results of such a failure
analysis--i.e. what the contents of some "software field failure
analysis" form would have to be to be useful and to meet regulatory
requirements (as would be the case for medical software with patient
safety risks).
Did anyone write documentation describing such a failure analysis
process and and how to record its results? Or could anyone direct me to
references, websites, people, etc., related to this topic?
