When working with HP technology Quality Center (QC), the first thing that came to my mind was "INTUITIVE" thing, and shorted time implementation than other cheaper solutions, that because the other HP solutions (QTP, LR) are really easygoing and friendlies, but the real thing is that it is not that much as thought, so, the implementation took me more time, because QC is too open, you can do whatever you want on it, it is a brainstorm that has to be carried out in order to determine how your process can fit on it. Researching further with experts on Testing discipline, told me that QC has its own definitions for software testing (scenarios, test cases, procedures, etc) and that is the reason that is not too standard. If you want to implement a TESTWARE on QC, you can not have it on one module, but it need to be distributed in several modules to make it work (could it be a tricky solution), as I understood, QC is only a repository for QTP, and LR scripts, that was the purpose it was constructed, but never for managing a testing process.
