PTC Integrity Requirements Connector vs Polarion Requirements comparison

"I would say there is value in how powerful, configurable, and user-friendly it is."

"The biggest improvement would be in the transparency we have now. We have very complex products. We make whole systems with difficult and diverse areas such as hardware, software, mechanical and printing, etc. To get the overview of all the requirements into a system, at that sizing, is the main advantage we have in the organization now."

"The solution is especially great for organizing folders effectively."

"In my opinion, Polarion Requirements' most beneficial feature is the ability to manage specifications within a work-like document that functions as a work item. Its collaboration features have worked very well and have been very useful. We can easily exchange information with the testing team, the business, and with DevOps."

"My company mainly utilizes the product for documenting internal standards, guidelines, and requirements. Currently, we're focusing on using it for internal purposes, but the vision is to expand its usage to include contract requirements and tracking functionalities. While we're not there yet, it has proven effective for managing our internal documentation needs."

"It is easier to produce documents using the platform."

"Its flexibility and APIs are the most valuable."

"A valuable feature from my side would be the comparison corporization."

"It is a stable solution...I rate the support a nine out of ten."

"It is not a stable solution, as we had issues with shared licenses."

"If we have more than one thousand work items in one live-book then it becomes almost unusable."

"I am somewhat satisfied with Polarion Requirements' functionality, but I feel a lack of certain functions regarding the review, which is a bit too limited."

"The one thing I would mention is the license policy is a little bit difficult. For different roles, you will need different license models. That seems a little bit difficult for us. Especially when you introduce such a complex system, you want to know the right way is to do licensing. It's not clear what that best way would be. The solution will be here for a long time, and I just think it could be more clear."

"In my opinion, the main area for improvement in Polarion Requirements is its user interface. It should be easier for engineers to understand how it works, as many features are not very easily understandable for end-users."

"The platform's review process for the documents could be better."

"We encountered numerous challenges, such as issues with requirements, project management, timing, and planning. The main problem with Polarion at the outset, I believe, was our limited understanding of the planning phase. During that time, we were more focused on change management related to requirements. Recognizing the importance of planning has been a key realization for us. Another mistake we made was not comprehending the need to document these requirements to manage all the work items effectively. Now, we understand the significance of this documentation. As a result of these insights, we have started to see a growing number of competitors from Polarion in this field. One potential improvement could be enabling Polarion to export work items not just to Microsoft Office but also to other office tools."

"The areas of Polarion Requirements that have room for improvement include usability, and the user interface, which was a little bit poor."

"The training material for PTC Integrity should be made a little bit easier or more useful for the user."

"I rate the solution's pricing a seven out of ten."

"The pricing model is flexible. You don't have to pay for the full functionalities. And it's a one-time investment for the licenses. You purchase what you need and then can work with that."

"Polarion Requirements is a little pricey."

"The product's price is high."

"I believe the cost is subjective. It seems a bit pricey, but it depends on your perspective. To provide some context, I compared the prices with GitLab and Jira. Unfortunately, I couldn't find Jira's prices. However, GitLab costs around 40 euros, and DeepLab, which I recently discovered, also falls in a similar price range. I'm not sure about DeepLab's features or interface improvements, as they might have been implementing requirements management over the past six months. In contrast, Polarion costs around 50 to 60 euros based on the 2021 prices I have. While it may seem a bit expensive, it's worth considering whether the additional investment, perhaps around 68 euros per user, is justified. It might appear costly at first glance, but it's essential to acknowledge that it can greatly streamline your work processes."

"It is expensive but not for what it is. It is just the right price for what it is. Its price is also similar to other solutions."