We primarily use this solution for requirement engineering.
Our deployment is on a private cloud from Siemens.
The interface for this solution needs to be made more user-friendly to provide a better user experience.
If we have too many work items in one LiveDoc then usage can be limited because the loading times are very slow.
In the next release of this solution, I would like to see the limitations removed.
There should be a better facility for importing, such as from an IBM Rational Doors document.
The configuration would be much simpler if it had limited functions for synchronizing with JIRA, for example.
I have been using this solution for two years.
The stability of this solution is not bad, but it could be better. If there are too many work items in one LiveDoc then usage is limited, which requires a workaround.
You have to take care not to use more than 1000 workitems in one livedoc, in other case the loading times will be so long, that you get timeouts for them. Baseline comparisons and other oprations will be timeouted also.
I don't think that this solution scales well. The problem is that they don't have the memory being used entirely. I think that it has something to do with the architecture.
I think that we have plans to increase usage, although I do not have the details as to how. I've got some information from the Siemens colleagues and I see that we cannot improve too much, or in too many ways, due to limitations in the architecture. It means that we have to split our project and use something with fewer objects in it.
There are approximately ten people using this solution.
Technical support for this solution is ok.
The initial setup of this solution was straightforward, and there were not too many problems with it. The process took a few hours.
I know of some other solutions, but they are different. For example, I think that IBM Rational DOORS is much better for requirements engineering, but it lacks other capabilities from Polarion. Merck may be better. It seems nice and seems to have the same capabilities, but I only have limited experience with it.
My advice to anybody who is implementing this solution is to use less than one thousand work items in one LiveDoc. Otherwise, their experience may be poor.
I would rate this solution a five out of ten.