Hmm, could you please let me know what are HPQC and FMEA tools? I used to think FMEA stand for Failure Modes and Effects Analysis, which is indeed a useful "tool" by means that it helps you to do the design better. Just as state-transition-model is a useful tool to design test cases. It has nothing to do with test documentation storage.
Perhaps you have found (or been recommended) a software tool that somehow helps you with FMEA? Could you tell me the vendor name or anything?
HPQC - HP Quality Center.
This is a test management tool
Reference to my question -
Managing the Testing Process - Rex Black
Chapter 1 - Defining What's on your plate: The foundation of a Test Project
Potential Cause(s) of failure
This columnn lists possible factores what might trigger the fialure - for example, operating system error, user error, or normal use. In my experience, this column is not as important as others when you are using an FMEA strictly as a test design tool.
My question - How do we use an FMEA as a test design tool.
I use HPQC, so I would be more interested in understand on how we can use FMEA to design test cases in HPQC
If however you are not familiar with HPQC, I would like to know how we can use FMEA for test design
Yes I've used HP Quality Center some time ago to store designed test cases. Please keep in mind it's storage tool, not the design tool, just as UML is design tool, while file system is a tool to store and manage your UML diagrams.
Are you sure Rex Black fail to describe how to use FMEA in a test design process? Don't he recommend to use the "lists of possible factors" (extending it with your own) to design test cases for each item in the list?
I think one possible integration between FMEA and HP QC may be to define each factor as a requirement item to be covered, so you could trace back test cases to those items. But I have never done anything like this, so it's just a guess.