It is hard to write good requirements - as far as possible rmtoo should support writing good requirements.
Because rmtoo is aimed to be used in productive development environments, there is the need that all the different outputs (e.g. PDFs, graphs, ...) must be generated automatically (without user interaction).
This typically describes the input and output and all the parameters needed (but not the ideas behind).
Software not only needs to be good --- also the 'marketing' aspect should be considered: the more people / companies rmtoo using, the more bug reports and comments there will be, the better rmtoo will be.
It's not very easy to e.g. visualize the dependency graph. Also typically for the testing department a document is needed that decribes the requirements (features) of the product.
First the requirements must be read in (and checked for syntactic - and if possible for semantic) problems.
Then the requirements must be analyzed.
As a last step the output artifacts must be generated.
To get started, concentrate on the major things, which are really needed.
Use techniques which are available.
This tests the interaction between the different layers of implementation and makes sure that the interaction works.
Each class, function and method must be tested. Each decision and error condition must be tested.
This gives the possibility to run a set of regression test and check the whole functionality of rmtoo.
The world needs a good, usable and free Requirements Management Tool.
It looks that there are no such programs out.
But: it's complex!