Polarion Requirements' valuable features include requirement and test management integration, link tracing, work item specifications, and workflow processes. Users appreciate its user-friendly and configurable nature, making it ideal for collaboration, folder organization, and report generation. Flexibility through APIs facilitates seamless data exchange with tools like IBM DOORS and Jira. Traceability, document generation, and electronic signatures enhance its utility. Its ability to manage various file types while maintaining visibility and historical tracking is highlighted.
- "The most beneficial features of Polarion Requirements for traceability include the traceability function and also the historical and matchmaking or cross-referencing, which was very good."
- "The most beneficial features of Polarion Requirements for traceability include the traceability function and also the historical and matchmaking or cross-referencing, which was very good."
- "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."
Polarion Requirements needs improvements in user interface friendliness and usability. Licensing complexity and performance issues with large work items are concerns. Enhancements are needed for workflow flexibility, import features, and test management capabilities. Integration challenges can occur without a programming background. Better document tracking and comparison, as well as risk analysis features, are desired. Some users experience difficulties with stability due to shared licenses, and traceability and bulk editing present challenges.
- "The user configuration had some issues; you need to know all the details, so it's not really friendly for those who are not IT savvy."
- "The areas of Polarion Requirements that have room for improvement include usability, and the user interface, which was a little bit poor."
- "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."