Several tools are used in the organizations to define and document requirements. These tools differ from each other in their features, capabilities, and goals. These distinct characteristics provide a foundation to select and customize tools for different software projects. Some of the commonly used requirements tools are listed in Table.
Table Requirements Engineering Tools
Tool | Description |
Analyst Pro | Analyzes and traces requirements. It automatically records and lists any changes to the requirements in the entire requirements engineering process. |
Caliber RM | Facilitates communication amongst development teams (as it is used for web-based requirements management) by providing a centralized requirement data to the distributed team members. It is also used for cross-project query and analysis, standard queries for quick access to requirement data, and advanced online analytic processing functionality. |
CORE version 3.1 | Enables the user to extract the requirements from the source documentation and then analyzes them for completeness, consistency, and testability. This tool also traces each requirement to a behavioral model, which describes the interactions and process sequences. |
Catalyze | Approaches organizations in a proper manner to easily gather business and system requirements. For this, it uses structured view of requirements and divides them into functional and non-functional requirements. |
Cradle version 4.0 | Provides requirements capture facility which extracts and examines user requirements. When new versions of the documents are released, this tool evaluates the difference between the two versions and provides impact assessment. |
Generic model approach to requirements capture (GMARC) | Provides elicitation of requirements by using a generic approach to enhance reusability and encourage standardization across the projects. In addition, it includes traceability of requirements in a hierarchical manner. |
Internal requisite analyzer (IRA) | Provides an integral support for requirements engineering process as it manages requirements in the development cycle. In addition, it adds graphical functions and guarantees the specification quality for large and complex projects. |
Requirements traceability management (RTM) | Supports multiple users to work on the same requirement at the same time by applying ‘locking control’ on the basis of requirements. It allows users to change records or problem reports and associate them with specific requirement data. |
Objectiver | Enables the analyst to elicit and specify requirements in a systematic manner. |