rmtoo is a free and open source requirements management tool.

rmtoo uses a different approach than most other requirements management tools: it comes as a command line tool which is optimized for handling requirements. The power of rmtoo lies in the fact that the development environment can handle the input and output files – there is no need for a special tool set environment.

Example: if you need to handle baselines (and there often is), rmtoo can be configured using a revision control system (e.g. git). The revision control system can handle different revisions, baselining, tagging, branching and many other things extremely well – there is no reason to reinvent the wheel and making it less efficient.

rmtoo fits perfectly in a development environment using text editors and command line tools such as emacs, vi, eclipse, make, maven.

• Use simple text files as input – use your favorite editor
• Many different output formats and artifacts are supported:
  • PDF – with links to dependent requirements
  • HTML – also with links to dependent requirements
  • Requirements dependency graph
  • Requirement count history graph
  • Lists of unfinished requirements including priority and effort estimation – e.g. for use in agile project development
• Fully integrated revision control system: git. Usages: history, statistics and baseline handling.
• A topic based output handling provides a common set of files for different types of output (PDF, HTML, …)
• Analytics modules: Heuristics help to evaluate the quality of requirements
• Constrains: inherited and automatic checking of constraints
• SCRUM artifacts: all artifacts which are used in SCRUM are supported: e.g. Selected for Sprint, Assigned, Finished, Statistics, and Burndown diagrams.
• Modules to support commercial biddings based on a given set of requirements
• Emacs mode files for editing requirements and topics included
• Configurable output in XML
• Fully integrated with Makefile handling of all artifacts
• Fully modular design: additional output requires minimal effort
• During parsing most common problems are detected: all syntax errors and also many semantic errors.
• Fully automated test environment – tests about 95% of the code and is shipped with rmtoo packages to check for possible problems in different environments.

rmtoo is not a fully integrated, tries-to-do-everything tool with a colorful GUI or different database backends.

rmtoo comes with man pages which describe the functionality, the input and output files.

Included in the rmtoo package is a set of requirements that describe the rmtoo functionality itself. This provides a good overview of rmtoo and is a good starting point for working with rmtoo.