- If I had to pick any weaknesses, I'd say that customization is too rigid.
- . Workflow script code allows you to customize a lot of what happens in the system, but not enough events are exposed to provide full control.
- User-defined fields can be created, but you are limited to a pre-defined set of field types: user list, lookup list, string, date, number. This covers most needs, but does have some limit. For instance, there is not a CheckBox style option (which actually used to exist in older versions of TestDirector).
- Not all modules provide customization or workflow handling.
- The Quality Center client tends to crash too frequently with Access Violation errors. Maybe this is the browser they host it in, maybe it's the ActiveX technology they use, or maybe it's just bad code.
- Back-end overhead. The system may be too big and to demanding for most organizations.
- You will need to install, manage and maintain a Database Server, an Application Server, and sometimes even a Web Server. Not to mention back-ups and other procedures that need to be done regularly.
- This is something people seldom take into account and for some organizations this is simply too much for what they gain.
- Customizations are not only rigid, but they demand knowledge of VBS and in many instances of the Quality Center API. Many times this knowledge is not there, and the organizations are left with an expensive tool that can potentially help them but it's not right for them...
- Slow over long distances. This is specially true for companies that are distributed around the World.
- Even if the system is Web-Based and you can connect using your browser, as you start working from remote locations (e.g. US vs Europe or Asia) the response time starts getting very annoying, unless you have some pretty advanced back-end communication channel.
Thursday, June 7, 2012
What are the disadvantages of HP Quality Center?
Posted by gtulasidhar at 1:28 AM