IBM Engineering Lifecycle Management (ELM) Reviews - Page 6

DOORS and DNG provide the capability to interact with other MBSE tools such as Rhapsody, and RQM to name a few, which allows a comprehensive solution to requirements management and product design. Each tool has its benefits and its drawbacks, however both tools are well supported.

Review collected by and hosted on G2.com.

DNG can improve on its usability, for example in DOORS it is easy to look at a hierachy tree, where in DNG it is not obvious, if its there ( i have not seen this). The ability to import and export is a bit clunky and when needing to make large scale changes this capability falls short, in contrast this is quite easy in DOORS, Review collected by and hosted on G2.com.

I like the web client interface and its association with other web applications on the Jazz platform. I like the flexibility in adding more applications via OSLC. Traceability with other applications is also a big benefit. Going further all data being stored in a relational database and be referenced many times rather than copied is a huge benefit over classic DOORS. Add in the ability to configuration manage your requirements using GCM facilitate requirements reuse by reference across my entire product line. Review collected by and hosted on G2.com.

DNG has some hard constraints like not being able to move projects/component from server to server .... one must be near perfect in the partitioning of data. Linking constraints are an all or nothing proposition. Configuration of change constraints must be set every time you create a stream. The type system also has hard constraints that cannot be violated otherwise you will corrupt the type system (duplicates). Type system must be identical to clone and copy, otherwise you incurr data loss. Review collected by and hosted on G2.com.

The Easy. linking with other documents Review collected by and hosted on G2.com.

The way to export in Word format Review collected by and hosted on G2.com.

We have probably overused the workflow management for RTC with our work items in IT. However, it has allowed us to manage roles and permissions in RTC and store all of our work items in 1 tool. Originally, we used excel or an old Lotus Notes database. We use it as a source code repository and it has allowed us to tie in locking down of the streams for change control and be consistent using one code respository for .net and java based applications. Review collected by and hosted on G2.com.

We are currently struggling with migrating to the cloud and running online verifies which appears to be a bug in the software. Also, we are doing a POC to move our source code for our Duck creek application off of the tool set due to issues with code merge challenges and merging efforts. This has introduced defects to production and cause a nightmare of code mgmt in our IT department because of the size of the manuscripts in the application as it is thousands of lines of code. It also does not allow us to be devops and we are going in that direction and looking at other source code repositories.

Another challenge we struggle with is management of the roles/permissions. This is really cumbersome to manage. Review collected by and hosted on G2.com.

DNG provides the capability to add custom attributes for tracking and reporting on requirement metadata. I especially like that I can trace my requirements to User Stories in Workflow Management and Test Cases in Test Management to manage my large scale software development project. This traceability allows me to provide detailed reports to my customer that demonstrate that requirements have been implemented and fully tested. The interface is easy to use (for creating requirements) and the views allow me to query requirements by user defined attributes. You can easily generate a requirements document from DNG using the "module" feature. Review collected by and hosted on G2.com.

There is really no downside other than the licensing costs if you have a small project. I believe the cost are worth the full lifecycle capability of the full IBM ELM tool suite. Review collected by and hosted on G2.com.

This solution helps users and business get connected correctly with more clarity of data and reports. Review collected by and hosted on G2.com.

As of now I don't think there are any disadvantages using this. Review collected by and hosted on G2.com.

I like how customizable the tool is. It allows teams and users to really configure the tool for their specific needs. The tool is also very tightly integrated with many other IBM tools. Review collected by and hosted on G2.com.

One of the things with the extreme customizability is that when the tool is integrated to the other tools, the more customized it is, it tends to break certain aspects of the tool. Either that or, the configuration is not easily defined to make it work. Review collected by and hosted on G2.com.

The zero deploy web based applications are very cost effective. Sharing requirements directly with Test, and developers reduces misunderstanding, and versioning errors. Review collected by and hosted on G2.com.

DOORS Classic has a very large following, and user trained base. DNG requires a re-think of how requirements are managed. Some industries can adapt quickly, others, not so fast. Review collected by and hosted on G2.com.

The ability to integrate with other systems while allowing controlling access and permissions to content plus changes. The OSLC and REST API are extensive enough the extend the system to meet regulatory requirements efficiently Review collected by and hosted on G2.com.

Lack of consistency across interfaces and intuitiveness of the interface leads user to the conclusion the system is too complex thus costly to develop products in. Configuration needs to be careful to focus consistency across work items and rest of the system. Review collected by and hosted on G2.com.

We use RTC to manage our workflow. It is a fairly complete tool that helps to better manage the work of employees. Mainly, tickets are generated, which will be tasks that each of the employees will manage. It has the possibility of changing the state in which it is found, what kind of

In short, it is a layer of managing work items with flexible process flows, revisions, approvals, discussion features captured / grouped in one place. It allows to obtain the complete information of the work element with the history of how it evolved. Review collected by and hosted on G2.com.

The administrator controls are powerful, but there is a fairly complicated learning curve and you will need the support of the colleagues who already know how to use it or the IBM manaual. It is too powerful to manage it easily from the start if you are new as an administrator.

The concept of the SDLC in RTC is very good and clear, but if you bring this tool to an existing organization, your developers, testers, etc. They will NOT accept it easily. You MUST make sure you have adequate time to train, have sessions to experiment and ask questions, and offer unlimited retraining sessions. Seriously. Make RTC administrators own that, because that will ultimately save you time and frustration as an administrator, since people will start learning the RTC method and will be less and less likely to cause alarms and panic in the last hours before to schedule an implementation. Review collected by and hosted on G2.com.