IBM Engineering Lifecycle Management (ELM) is an end-to-end engineering solution used to manage system requirements to design, workflow, and test management, extending the functionality of ALM tools for better complex-systems development.
N/A
Modern Requirements4DevOps
Score 8.0 out of 10
N/A
Modern Requirements4DevOps is a fully-featured Requirements Management tool built into Azure DevOps. By partnering with Microsoft, Modern Requirements is able to offer a fully integrated solution within Azure DevOps, TFS, and VSTS. The Modern Requirements solution provides the ability to: Create documentation without leaving an Azure DevOps project Construct Diagrams, Mockups, and Use Case models that the user can connect requirements directly to Build…
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.
We tried the Modern Requirements4DevOps AddIn to see if it brings a added value to our development. I have to say that I would distinguish between types of projects in which it is beneficial and in which it is probably "over engineering". Certainly, bigger development projects with higher complexity are more suitable than small and not really complex projects. However, for the bigger projects Modern Requirements4DevOps definitely helps to deal with the complexity as it adds way more contextualisation to the various entities. It really helps to understand which requirements led to which action in a diagram or task during development. It helps to control the complexity and inform all team members along the project.
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.
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.
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.
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.
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.
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.
Modern Requirements4DevOps is an AddIn for Azure DevOps Server (Microsoft Azure DevOps) and extends the native features of Azure DevOps in the area of Requirements Engineering, Requirements Management and Reporting. Azure DevOps already contains tons of valuable features. However, for bigger and more complex projects Modern Requirements4DevOps extends Azure DevOps by further features. Thus we used both products alongside.
Better communication --> thus less misunderstandings
More Transparency about requirements --> adds context and helps to build a common understanding
Traceability of Requirements --> we used the baseline also to look into the history of requirements to understand how certain requirements have changed
