IBM Rational RequisitePro

IBM Rational RequisitePro

Score 7.3 out of 10
IBM Rational RequisitePro


What is IBM Rational RequisitePro?

IBM Rational RequitePro is an application requirement management offering.
Read more

Recent Reviews

Read all reviews
Return to navigation


View all pricing

What is IBM Rational RequisitePro?

IBM Rational RequitePro is an application requirement management offering.

Entry-level set up fee?

  • No setup fee


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Would you like us to let the vendor know that you want pricing?

12 people want pricing too

Alternatives Pricing

What is iRise?

iRise offers a prototyping and design platform for software development.

What is PractiTest?

PractiTest is presented as a cloud-based test management tool that provides its customers with an end-to-end system to meet testing and QA needs. It is described by the vendor as flexible but methodological, enabling organizations to ensure visibility and communication at all levels. The solution…

Return to navigation

Product Details

What is IBM Rational RequisitePro?

IBM Rational RequitePro is an application requirement management offering.

IBM Rational RequisitePro Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation


View all alternatives
Return to navigation


(1-2 of 2)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
IBM Rational RequisitePro is leveraged as the Requirements Repository as well as the sole source for tracking User Stories and related Artifacts. Business Partners enter the user stories into the system, and then the are cataloged and go through our Agile Sprints and track through Quality Assurance. This allows everyone to have a real time view of requirements and how items are moving to production.
  • Flexibility to customize the repository to meet the needs of your process and business unity
  • Compatibility with Microsoft Office tools
  • Flexible reporting capability to extract data and report in Excel
  • Ability to tie requirements and break them do to trace requirements to implementation
  • 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.
Better for larger teams, it doesn't provide the value as the cost may not have the ROI. You may want to look at some other tools that are available in the cloud to manage requirements. Due to the fact that the tool has the capability for customization, it is imperative that in large teams that the tool is used in a consistent manner.
  • Allowed our team to create a library of requirements available to the larger organization
  • Consolidated reporting and creates a transparent view status information
  • Supported moving from Waterfall to Agile Software Development Methodology
RequisitePro integrated better with our tech stack, and allowed us to leverage our process. Many products that are available focus in on using their internal processes or required fields/data rather than allowing the flexibility and business defined processes. Keep in mind that if the process that is part of the product will meet your needs, then I would not discount the product.
Business Analysts, Systems Analysts, Product Owners. It is used in our agile process to manage use cases and user stories to aid in flowing of work to our scrum teams for software development. Testing teams also use the data to build test cases and end to end functional scripts. No work is done without it first coming through ReqPro.
It is a small team to build out workflows and to manage data setup and requests. As our requirements workflow is modified, we directly update Reqpro to support the needs of the team. It is important to have a knowledge of the RDBMS you employ for requirements as well as reqpro.
  • Requirements Management
  • Project Prioritization
  • Commmunication
  • Build out of documents for audit
  • Tracking of Team Velocity
  • Understanding Dependencies
  • Document Management - Requirements
  • Further Reporting
  • Build out of details for audit requirements - data extraction
Learning Curve is there, plus there performance can be an issue. It is best to understand where the server is located in relation to the team. Creation of new documents and mapping the requirements into ReqPro from Office can be a challenge to learn. Best to get help to do the initial document setup.
It replaced Word Documents/Excel sheets used to manage requirements. The big push was to get us to a place where we could interrogate requirements and have transparency to see them across multiple teams. It also allows reporting to show where a piece of work is in the pipeline, and who is managing it.
  • Product Features
  • Product Reputation
  • Existing Relationship with the Vendor
The tool was a great tool for the money, but did have the need to purchase one license per person. Floating licenses are available, but the functionality is less for the web version. Having this tool integrate with other IBM tools is very convenient and does provide a productivity lift for the team.
Look at how the tool fits in the enterprise and the number of people using it. Make sure your process fits within the tool rather than making the tool fit your process. Overall it is a good tool and does the job, but make sure you have a set in process before moving forward with it.
  • Implemented in-house
  • Third-party professional services
We used a COE in house plus external services.
Change management was a major issue with the implementation
We were moving to agile development and needed a means to track use cases and user stories from start to finish.
  • Understanding how to implement our process in the application
  • Mapping of fields between the MS Office and IBM ReqPro DB
  • Working through Performance issues.
It had to be quick due to the demands of our implementation.
Since our company has a large suite of IBM tools, the full support was purchased for this one as well as part of our ELA. It is a good thing to do, as it is very handy during upgrades it is quick to reach out and get the needed information to support the software.
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.
Yes. We were able to use our IBM ID and login to the support site. Question was acknowledged immediately and answered within 3 business days. Information given was direct and pertinent to our issue and they had a tech call us to walk through the remediation of the issue that we had identified during our conversion to a new hardware platform.
We were moving to a new hardware platform and noticed that some of our functions were not working properly. IBM assisted looking through some of our own code and changes to resolve an issue. It ended up that a newer person on the team had hard coded a value and caused the issue.
  • Integration with MS Office
  • Screen Building Capabilities
  • Report Exports
  • Easy to design complicated screens
  • Reporting from the RDBMS was a challenge
  • Due to performance issues had to extract data to excel to make it widely available.
Though it was available, licensing was an issue and it did not have all the capabilities of the thick client application. It made it so more could access it, but we found it wasn't used as many team members needed the full User interface that was available tin the Client Version.
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.
Miguel Angel Merino Vega | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
We have many projects simultaneously. Project management is vital in our industry, and within this, we want to have well-drawn artifacts. From the conception stage, it is important to evolve the software requirements, and that is where RequisitePro becomes important in the management of the project and the team in terms of the visibility of documents.
  • Traceability of artifacts, coom requirements, use cases, functionalities, etc.
  • Document management and easely MS Office integration
  • IBM Rational products integration
  • Learning curve, especially if you're not familiar with IBM Rational tools
  • Payment product
  • SVN Integration
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.
  • Requirements management saves overwork and minimizes risks.
  • Minimize time in the manual elaboration of documents, that translates into money
IBM Doors could be better at document management for a higher price. If you need more complex traceabilily, Doors is the way to go. If you need less, free and simple management, a common SVN is ok for you.
Return to navigation