Likelihood to Recommend IBM Engineering Requirements Management DOORS former IBM Rational DOORS profits very much from the mighty market position it had till today. It had been the most favored requirement engineering tools suite with the highest investments in the infrastructure concerning hardware, software, and knowledge sources. It was embedded in knowledge sources of test stands, hardware labs, and knowledge database servers. It allowed for some of the highest profit changes and made the fame with it. But the paradigms of requirements engineering change. If not were superseded by completely different approaches for the target solution worlds. The foremost position in the selling tables is unstable if changes are not solved or coped with by the strategist at IBM and their customers. Since the highly successful alternative suits are already at the market, and some are from IBM already the lifecycle for IBM Engineering Requirements Management DOORS is at the later highs. But the suite is still at the very top and very popular. There are still many problems unsolved and many wishes at the customers to make the use more comfortable and efficient at the overall level. If the time of setting up the software package is passed the adoption get more extended and complicated. There is a lot of work at the stage around and the expertise will be required for a long time from now.
Steffen Jäschke Projektspezialist bei Steffen Jäschke EinzUnt Physik, Berechnungen
Read full review Great to manage your issues in a clear and centralised way. If your development teams work with
Jira , it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up
Read full review Pros Easy to use with well defined template and user defined fields. New team can setup a project area easily by copying an existing template and adding customized fields for their special needs. It can be used during almost the whole project cycle and give us a better view and control on the projects. Lots of built-in report functions. Read full review Manageable workflow to ensure all users follow the same process. Can ban boards for easy visual of ticket status. Very flexible tool that can adapt to lots of different uses outside of the traditional service desk model. Added communication tools help you get out of e-mail jail. Read full review Cons Wireframes are quite basic. If you need intuitive and interactive wireframes to elaborate the requirements. you probably need to define outside the tool and then upload as image. ER (define data dictionaries) modeling is not there. Use case modeling is quite basic. You can visualize the use case and actors relation but the tool does not enforce the rules. Does not support offline work. Read full review Ability to control the number of email notifications received (Note: this is a new feature in the Latest release but I personally haven not extensively looked at it and how well it solves the existing problem). No way to reply to multiple tickets at once, say you got 4 tickets in for the same issue, there is no way you can reply to them in one stroke. Other Ticketing systems do have this ability. Using a large number of add-ons to customize and add additional features adds up quickly and can become rather expensive. Request forms are very basic and there is no native dynamic field ability available. Read full review Likelihood to Renew At the moment we are required by contract to continue to use the IBM DOORS software for our current client. Given that it can be expensive, if we were to use it after our current client's needs were met, we would have to secure other projects in order to justify the continued use of the software.
Read full review Usability The UI is terrible and not intuitive. Users need training in order to complete tasks. Much like SAP, it's not the clearest tool. The tracing feature is especially complicated because you must write the scripts yourself. There is a learning curve. Also, even the setup, installation, and logging in each time takes a considerable amount of time.
Read full review I gave JIRA a score of 9 since I am happy with the service it offers. I can easily see the SLA since it gives me visibility. I can pull up the reports I need. I can reach out to our clients using the PR ticket so it is hassle-free for me.
Read full review Support Rating It does a basic job and has the potential to complete some robust reporting tasks, however, it really is a clunky piece of software with a terrible user interface that makes using it routinely quite unpleasant. Many of our legacy and maintenance projects still use DOORS but our department and company use many alternatives and are looking for better tools.
Read full review I have not used the technical support from Atlassian. In terms of online help and resources, they are a bit limited thus making it more of a challenge to troubleshoot issues and learn more functionality. There aren't a lot of resources available on the Atlassian site besides developer documents. It would be nice to have a blog or forum where users can get the help they need.
Read full review Implementation Rating No problems
Read full review Alternatives Considered It was easier to do all the change management-related activities, even configurations were handled very effectively. New process definitions and initiatives made it easier for better project deliverables. Effective resource allocations and better reporting and defect management. The overall cost of the tool is great too and well within budget.
Read full review When I evaluated
Spiceworks , it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did.
JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into one service desk solution, and
JIRA was the better option since it was less expensive and geared towards being a ticketing system.
Read full review Return on Investment If you can setup DOORS to your project, you will experience lower costs. Also, less rework in the project, which means lower times to achieve your milestones. Finally, the cost of setting up a related project is considerably lower, and the estimates obtained in the process are much more precise. Read full review JIRA has been incredibly useful. Our work is more organized and easier to view by the team members as well as upper-level people. Our work is correctly assigned and when there are issues, they can be immediately addressed within the tool. Users can attach screenshots or files of issues that help clarify the ticket. Developers can attach relevant data as well. Read full review ScreenShots Jira Service Management Screenshots