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.
Let one thing do one thing.
It is now possible to use preinstalled VMs on AWS EC2.Within minutes you can create a complete environment for rmtoo evaluation or small projects.
To use a preinstalled VM, login or create an AWS EC2 account. Then create a VM. When asked for the image, choose Community AMIs and search for rmtoo. Choose the image and continue with creating the VMs. For the VM you can use any AWS flavor. A detailed description of the VM’s content is available. There is also a detailed description of how to use the preinstalled VM, how to use rmtoo there and how to start your first project.
Unique Feature Set
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.
Download and Project Infrastructure
rmtoo works well as a requirements management tool. It is currently used in commercial and open source projects all over the world.
Because there were no bug reports or user requests for some time, there were no new releases for some month now.
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.
There are two presentations which give an introduction to rmtoo.
This is a good starting point to get an impression of how rmtoo can be used in your projects.
The first presentation gives an rough overview about all the features of rmtoo and reasons why and when rmtoo should be used in a project.
This presentation also includes a Do’s and Don’ts list and can be seen as a management summary.
rmtoo is self contained in the sense that the requirements for rmtoo are described with the help of rmtoo itself.
Because the document was created with the help of rmtoo this can be seen as an example of an output document, including backlog, list of requirements that must be further elaborated upon and all requirement descriptions.
The requirements document for rmtoo describes every feature in detail. The document also includes a roadmap, which describes the planned but not yet implemented features.
Requirements Dependency Graph
The requirements dependency graph is one rmtoo output artifact. There is a requirements dependency graph available which describes the current state of rmtoo itself.
Topic Based Requirements Dependency Graph
The topic based requirements dependency graph is similar to the standard requirements dependency graph, except that the requirements for one topic are clustered.
Data Visualization with Tulip
One supplied output module writes data in the format that it can be read by the Data Visuzalization Software ‘Tulip’. Please note that the Tulip application operates on graphs – and not on digraphs. Therefore some information of the dependency graphs cannot be displayed in Tulip. It is possible with Tulip to layout graphs in 2D and also in 3D.
Comments from users
You’ve created a wonderful piece of software that fills a very specific need, does it well, and holds lots of promise for growth and maturity in the future. [Dipin, 2010-11-17]
Here are two lists of links: one list provides more information about rmtoo itself and the other shows links to other requirements management tools.
Links to requirements management resources
- Requirements Management Tools from Ludwig Consulting Services: List of available requirements management tools. This website also discusses a lot of different aspects of requirements management.
- Requirements Tools at Volere: Another list of requirements tools – each with a short description and the major features.
- Requirements Tools List from Ian Alexander: On this page, the tools are divided into different subject areas.
- OSRMT: This is an open source requirements management tool. It comes with a GUI.
Releases and Version Numbers
The rmtoo project has the methodology ‘Release early, Release often, And listen to your customers.‘
There are no long development cycles: when a new feature is implemented, a new version is released. Therefore a new version is sometimes released just a few days after the previous one.
Implementing a new feature includes:
- Writing requirements for the new feature
- Writing the source code
- Writing test cases
- Writing documentation
If there is a new feature it is fully available when it is released.
License and Support
rmtoo is copyright flonatel GmbH & Co. KG and Andreas Florath.
The tool is licensed under GPL v3.
Commercial support for rmtoo is available. Please contact email@example.com
flonatel GmbH & Co. KG
Andreas Florath (Geschäftsführer)
Raerener Strasse 10b
Registergericht Aachen; HRA 6727
USt-IdNr.: DE 271561931