As of version 5.0, IBM Rational Requirements Composer is renamed to IBM Rational DOORS Next Generation. For more details,
read this blog.
Bridge customers, requirements, and deliverables
Define and capture business needs and manage all types of requirements across the project lifecycle.
IBM Rational Requirements Composer: Define, collaborate, and manage requirements
for your development or project team. Features >
What's new in 4.0.6
Many usability improvements for modules, including faster artifact creation, new options for the module editor, and the ability to specify the artifact types that you prefer to work with.
High quality business requirements and good management practices in the development process (waterfall, iterative or agile) leads to the best outcomes. Engaging stakeholders - early and often - in defining and validating requirements improves the likelihood that projects will deliver what customers need. Using well defined requirements in an organized managed process allows business analysts, developers, and other team members to analyze the information to help drive key business decisions. Traceability across requirements can expose gaps and impact from change. Analysis features then give team members the power to discover key status, release, and value information during development based on good quality requirements.
Requirements are expressed in many different forms visually and textually and they can come from many sources and tools: spreadsheets, presentations, whiteboard snapshots, etc. Requirements Composer will bring these "information islands" together and connect them with traceability to expose them to the broader development team for collaboration and analysis.
Requirements Composer helps project teams define what the business needs to accomplish, structure their ideas as text, stories, use cases, process diagrams, work items and tests.
Analysts and others who author documents have all of these tools and features available, with similar user interfaces, in one location, using a common repository.
Impact and requirement gaps in project information can be viewed and exposed using built in traceability viewers to show how changed requirement will affect the down/up stream for development.
Project team members will be able use standard reporting views that include attributes, filters, sorts, traceability and other critical information for development decisions.