I would rate the product 9 out of 10.

From my perspective, I grasp the Polarion solution quite effectively. It appears to be the most suitable interface for me in terms of document management. Utilizing these documents to meet all the necessary criteria is crucial. Additionally, it's essential to consider the requirement of one license per user. Because, by addressing this aspect, you can automate a wide range of tasks, including those related to value plans and consumer rates, among others.

I rate the product a seven out of ten. 

It depends on how deep they want to go into that mechanism. They really need to commit to using the tool for all of their requirements gathering. What you can do, if you absolutely must do some of the things outside the tool, is use the link field and put the hyperlink to something else outside the tool, which is feasible. But if they do that, they need to pay attention that people will move out of the software to receive the rest of their information elsewhere. It has advantages and drawbacks. I would rate Polarion Requirements a nine out of ten.

It's a good product. If Polarion improved its usability a little, I’d rate Polarion Requirements a ten out of ten. However, right now I rate it a seven out of ten.

Overall, I would rate the solution a ten out of ten. 

I definitely recommend it. In my opinion, it's easy to use and access. You don't need to install any external software. 

Since it's server-based (and can be cloud-based), it's simple to access.

I would recommend Polarion Requirements as it makes test engineering easier. I'd rate Polarion Requirements seven out of ten.

My advice for anybody who is implementing this solution is to use it only for smaller projects.

I cannot think of any features that should be added, but some effort should be put into making the existing ones more usable.

I would rate this solution a five out of ten.

I rate the solution eight out of ten.

We are using the on-premises deployment model.

My advice to others considering implementing the solution is that you should check your requirements for such a tool and process. Everything depends on the company. Our experience was to first fix the process of engineering requirements for vendor tools. We had to prepare for the introduction of the solution very well by creating a proper process. It's very important to go through everything beforehand.

I would rate the solution nine out of ten.

For anyone interested in the product I would suggest evaluating it in real conditions, with a specific project because of the issue with requirements.

I would rate this product a two out of 10.

I rate Polarion Requirements an eight out of ten.

Polarion should not be used for project management. It should be used for feasibility and requirement management. I would recommend to use it first to understand the features and then improve it. We wanted to improve and adapt it to our new requirements, but we never finished doing that. So, we are not able to release. It is a little bit hard to understand the features. That's why I am recommending to use it first. 

I would rate Polarion Requirements an eight out of ten. It is quite a good solution.