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
IBM Rational ClearQuest
Score 7.0 out of 10
N/A
A customizable database workflow application development and production system that provides better visibility and control. IBM Rational ClearQuest is change management software that helps improve developer productivity while accommodating the methodologies, processes and tools that best fit the project and the people on the team. It provides tools and processes used to maintain control of changes while catering to the diverse needs of the developer.
N/A
Pricing
IBM Engineering Lifecycle Management
IBM Rational ClearQuest
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM Engineering Lifecycle Management
IBM Rational ClearQuest
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
IBM Engineering Lifecycle Management
IBM Rational ClearQuest
Considered Both Products
IBM Engineering Lifecycle Management
Verified User
Analyst
Chose IBM Engineering Lifecycle Management
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 …
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.
If you are familiar with IBM Rational Suite products, RequisitePro will add up due to the synergy between other components. Beyond that, if your business is not structured to an adequate development methodology or lacks the degree of maturity or necessary resources, probably RequisitePro does not add much value. If you work with developers in the requirements analysis, they probably prefer to use an SVN repository.
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.
Performance can be an issue. Make certain the server is sized properly
There is a large difference in capability of the Thick Client Version compared with the web based version. Make certain each job function has proper access to be able to do what is required of them.
Learning curve is not too steep, but would suggest having someone with experience setup the repository. Highly suggest getting a contractor to assist to get the repository up and running.
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.
Most likely as it's one of the powerful tools in the organization. We needed this tool to track all the process related documentation and also to capture signatures.
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.
Please keep in mind that this all has to do with you you customize the user interface. It becomes very easy to house all of your requirements, but it may and can make life difficult for you if you do not think ahead of how you want the app to work and house your data
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.
IBM has good support and knowledge base. With the wealth of information on their site and the support desk, we were able to quickly resolve issues. It is smart to build up a COE and a group that manages the software otherwise it is quick to be able to lose the knowledge as team members are assigned different duties
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.
IBM clearquest would the BEST option if you are looking for managing change requests, managing project workflows, generating reports on status of requests. The reason being: cost, cost and cost. It almost handles everything that you would need for your project including bug tracking unless you want something really fancy (like HP QC) with a higher cost that supports a wide variety of needs which you might need to evaluate based on your project needs. For example, if you would be really making use of all those additional features provided by HP Quality Center. To be honest it depends on your project size, the skills of team members and of course budget!
IBM Rational ClearQuest has provided a workflow that works without unique software methodology. As a result we deliver complete software products to our clients in a 6 to 8 week development time frame.
As a result of our highly customized implementation, we have 8 resources supporting IBM Rational ClearQuest. Three of the resources are full time configuration management staff that administer and support the tool set and the other 5 are from the testing group that handle ClearQuest user support issues in addition to their testing duties.
