I have worked a little with IBM DOORS and not at all with the other tool. What I think is essential in Req Management tool is to have the following:
- integration with the testing tool
- capability to create coverage analysis based on test cases developed
- integration with development platform
- capability to prioritise requirements based on a risk analysis formula (must be calculated otherwise each BA will assess risk subjectively)
- capability to create an integration matrix (very useful for document review and QA)
- easy to use and pretty similar to the previous method used by BA team (most likely word)
- can integrate process diagrams
- can structure requirements by levels
- defects can b associated with requirements
Between the two I would choose IBM mostly due to integrations but this is a contextual choice.
Search for a product comparison in Application Requirements Management
I don't have access to both the tool but you may consider following points
while comparing features
General Industry acceptance Vendor reliability Existing solution
in ACS Multi site access Consistent response time regardless of
size/location Training Useability Scalability Should support
off line use Security Web based access Edit in word feature
Condition
based mandatory fields Content level filtering Inline editing
Workflow
visibility Permissions visibility Centralized project dashboard
Library
feature Set link using Drag and Drop Requirement and Test Management
Documents Flexibilty on requirements categories/structure Various
representation of requirements Documents or Content Items identification
Reorder the content items Requirement and Test Management
Processing Baseline
of requirements Versioning of requirements Ability to categorize
requirements Voting on requirements Concurrent editing, review,
markup, & comment Grouping of related requirements Bulk
processing Ability
to derive finer grain requirements and maintain traceability back to higher
level requirements. Cross-projects requirements sharing Identify
inconsistencies Cross-sites requirements sharing Track the
fulfillment and status of the requirement Automatic notifications to the
stakeholders Managing requirements dependencies Quality and
consistency checking Verification of requirements Content level
filtering Integration Interface with R&D investments
prioritization Integration
with Design/MBD tools Integration with Product Lines tools Integration
with Defect Tracking tools Integration with Test Management tools
Integration
with Config Management tools Integration with Project Management
tools Traceability
of requirements throughout development cycle Export into another
requirements tool Import from another requirements tool Export to
Word/PDF/Excel Import from Word Synchronization to Word Usage of
the tool for release planning Generic/External API Export Template
customization (At user side) Visualization & Reporting Easily
configurable views for different stakeholders. Support for multiple
project views into a shared requirements library Generate default reports
Traceability views and reports per product feature. Statistical reports
Requirements coverage analysis and reports. Query capability to show
relationships and interactions Requirement progress/status
reporting Charts
to identify empty traces
Administration Manage servers Reliability Support Open database
system (standard query access) Deploy new configuration on the
server Support
and Maintenance
Application requirements management is a critical aspect of software development and project management that involves the systematic identification, documentation, analysis, and tracking of requirements for an application or software system.
I have worked a little with IBM DOORS and not at all with the other tool. What I think is essential in Req Management tool is to have the following:
- integration with the testing tool
- capability to create coverage analysis based on test cases developed
- integration with development platform
- capability to prioritise requirements based on a risk analysis formula (must be calculated otherwise each BA will assess risk subjectively)
- capability to create an integration matrix (very useful for document review and QA)
- easy to use and pretty similar to the previous method used by BA team (most likely word)
- can integrate process diagrams
- can structure requirements by levels
- defects can b associated with requirements
Between the two I would choose IBM mostly due to integrations but this is a contextual choice.
In short, Doors is the best RM tool
I don't have access to both the tool but you may consider following points
while comparing features
General Industry acceptance Vendor reliability Existing solution
in ACS Multi site access Consistent response time regardless of
size/location Training Useability Scalability Should support
off line use Security Web based access Edit in word feature
Condition
based mandatory fields Content level filtering Inline editing
Workflow
visibility Permissions visibility Centralized project dashboard
Library
feature Set link using Drag and Drop Requirement and Test Management
Documents Flexibilty on requirements categories/structure Various
representation of requirements Documents or Content Items identification
Reorder the content items Requirement and Test Management
Processing Baseline
of requirements Versioning of requirements Ability to categorize
requirements Voting on requirements Concurrent editing, review,
markup, & comment Grouping of related requirements Bulk
processing Ability
to derive finer grain requirements and maintain traceability back to higher
level requirements. Cross-projects requirements sharing Identify
inconsistencies Cross-sites requirements sharing Track the
fulfillment and status of the requirement Automatic notifications to the
stakeholders Managing requirements dependencies Quality and
consistency checking Verification of requirements Content level
filtering Integration Interface with R&D investments
prioritization Integration
with Design/MBD tools Integration with Product Lines tools Integration
with Defect Tracking tools Integration with Test Management tools
Integration
with Config Management tools Integration with Project Management
tools Traceability
of requirements throughout development cycle Export into another
requirements tool Import from another requirements tool Export to
Word/PDF/Excel Import from Word Synchronization to Word Usage of
the tool for release planning Generic/External API Export Template
customization (At user side) Visualization & Reporting Easily
configurable views for different stakeholders. Support for multiple
project views into a shared requirements library Generate default reports
Traceability views and reports per product feature. Statistical reports
Requirements coverage analysis and reports. Query capability to show
relationships and interactions Requirement progress/status
reporting Charts
to identify empty traces
Administration Manage servers Reliability Support Open database
system (standard query access) Deploy new configuration on the
server Support
and Maintenance