We performed a comparison between IBM Rational DOORS, Jira, and Polarion Requirements based on real PeerSpot user reviews.
Find out what your peers are saying about IBM, Atlassian, Siemens and others in Application Requirements Management.
"The program is very stable."
"It's a very interesting tool. I like that it's simple. You have to create your document, add your templates, and have your headings and definitions, and it's done. You must attribute the discipline and fill out the comment field for requirements. It also provides you with unique IDs for each requirement. I like that it never duplicates IDs."
"Compared to other tools that I have used over the past 20 years, DOORS is the best of the best."
"We have different generations of all products. It lets us select and see unique attributes for each release or generation. You can use attributes to define a selection area to see which equipments are for the old versions and which ones are for the new versions. This inbuilt view is what I like in IBM Rational DOORS. So, for a database and a set of requirements, it will select and show unique attributes for a release or a generation."
"IBM Rational DOORS keeps everything organized."
"I really like the customization that can be done using the DOORS Extension Language (DXL)."
"It is a stable solution."
"It is a mature product that is stable."
"It improved communication, as it was a popular tool, and most people enjoyed using it."
"We've found the scalability to be good."
"Workflow administration is an easy process, especially with respect to defects."
"It's an open-sourced product that is easy to customize."
"Jira's collaborative features, such as comments, notifications, and real-time updates, facilitate better communication."
"It's a very complete product overall."
"The adaptability of the Scrum and Kanban boards for other uses, with careful use of the customization features."
"It's flexible and it can provide a lot of different options, such as dashboards, that you can create and manage."
"We worked with the web interface."
"Polarion Requirements' most valuable features are link tracing, book entry, and sequence training features."
"We can easily customize it because of the web services and open APIs. Also, the APIs are available. We integrated Polarion with one of Siemens' products, Teamcenter, which is especially useful for automotive industries. There is an open API for integration with Jira as well, so for me, customization is a strong point."
"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."
"I like the way this solution is structured."
"Its flexibility and APIs are the most valuable."
"It is easier to produce documents using the platform."
"They need to provide users with information on what options would be best for their setup."
"The problem is that because the GUI is so bad, you either have to spend a lot of money customizing the interface yourself, or a lot of money on training."
"It used to be very clunky."
"There are problems with communicating between DOORS and Microsoft Office."
"IBM should integrate some solutions they already own toenhance the utility of the product further. Specifically import and export to Office products is more difficult than it needs to be."
"The low performance of the solution is probably because it is quite an old tool."
"The web application DOORS Web Access doesn't have the same functionality as the standard client, so it's not a real substitute. For example, web Access only provides writing requirements, but you can't do much more with it."
"The interface needs an area to be able to type your query and actually be able to find them."
"We'd like to see more collaboration tools implemented within the product itself."
"The hierarchy for Jira tickets is too flat."
"Slow when integrating with other components."
"Performance is something that can always be improved upon in a feature release. Additionally, it would be a benefit to add Markdown in Jira because sometimes it might be better to describe everything in Markdown because it is a common language structure."
"Not very intuitive for project admins."
"The initial setup was a bit problematic in terms of getting access to Jira. That goes for a few users, including me."
"The solution should be more user-friendly and include integration with different tools."
"The work items structure is not hierarchical and that needs to be changed. It's too flat."
"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 risk assessment functionality needs improvement, like FMEA risk management."
"If we have more than one thousand work items in one live-book then it becomes almost unusable."
"Polarion Requirement needs to have a feature where we can track changes and compare documents. Currently, we do it manually."
"It is stable enough but if you would like to work with more requirement objects, then you will get timeouts."
"It is not a stable solution, as we had issues with shared licenses."
"The usability of the solution should also be improved."
"Integration can be a little tricky if you're not aware of basic computer science or programming language."
