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.
"I would say that the best feature of the solution is that since everything is in one place, and if you make any changes, then they are recorded or tracked."
"The data logs are ver conveneint."
"It has the features of: traceability, configuration management, and user access."
"The traceability matrix in DOORS improved our project outcomes. It helps ensure coverage of requirements at different levels, from user requirements to software requirements to test requirements."
"It is a stable solution."
"IBM Rational DOORS keeps everything organized."
"When you install DOORS locally, you have the flexibility to do what you want with the solution. You can add functionality and do many things that you can't do with other tools or do well enough to satisfy your users' requirements."
"I really like the customization that can be done using the DOORS Extension Language (DXL)."
"The product's initial setup phase was straightforward."
"It is a complete solution. It has more features as compared to other tools, especially the open-source one that we use. It is also easy to administer."
"Jira is very useful for project management for internal projects."
"We integrate Jira with QRadar which is helpful."
"I have found the most valuable features of Jira to be ticketing, life cycle workflow, definition, and creation. Many of the features are useful."
"It's easy to deploy."
"The most valuable features are that it is good for tracking the issues and it provides for the usage of Confluence."
"Issue linking has enabled teams to trace issues."
"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."
"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."
"We worked with the web interface."
"Polarion Requirements' most valuable features are link tracing, book entry, and sequence training features."
"Its flexibility and APIs are the most valuable."
"I like the way this solution is structured."
"It is easier to produce documents using the platform."
"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."
"Not all Rational Team Concert operations are available from the web client. Certain operations, like creating streams or components, still require using the desktop application. They're not accessible through the web interface. And in my opinion, this limitation should be removed."
"The software and GUI is very outdated."
"They need to provide users with information on what options would be best for their setup."
"The images are not clear. We have to use them as OLE objects. And in the testing part, I'm not sure how to link it with it. This is my main concern."
"The kind of dashboard is not very convenient."
"The performance could be improved. It doesn't run as smoothly as it could."
"Both the performance and the price could be improved."
"There are problems with communicating between DOORS and Microsoft Office."
"The challenge which I frequently see from Jira is the label. When you search for a label sometimes, it suddenly disappears. If there's a mismatch due to all-caps or lower case, you won't be able to find it. It won't even come up as a recommendation or suggestion. That's something that can be really frustrating, as people create labels in their own specific ways and then no one else can find anything."
"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."
"I would prefer it if the solution was more intuitive."
"Once a story is closed, all the records, versions, and documentation associated with it are gone. We lose the traceability of what was done."
"I'd like to see better notetaking capabilities so every user can get notes when someone provides comments on a Jira ticket. So if they don't want to provide the comments on the Jira ticket, they can get the personal notes in a Jira tool for every profile."
"We'd like to see Jira have more integration with a development ID."
"A more organized hierarchy is important. Reporting and JQL create issues for me. They do not completely cover the reporting part that I need to report in terms of my capacity to plan. In the same token, there is no record at this very moment to provide me with one export with epics story points, tasks, or issues and their sub-tasks at the same time."
"The help desk and services management features are in need of improvement."
"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 usability of the solution should also be improved."
"The risk assessment functionality needs improvement, like FMEA risk management."
"Integration can be a little tricky if you're not aware of basic computer science or programming language."
"If we have more than one thousand work items in one live-book then it becomes almost unusable."
"It is stable enough but if you would like to work with more requirement objects, then you will get timeouts."
"Its user interface could be more user friendly. In addition, a lot of features are missing for test management. It should have the test case ordering feature."
"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."
