I am project lead on the Eclipse Requirements Modeling Framework (RMF),
which also contains a tool called ProR for requirements engineering (http://eclipse.org/rmf).
In two weeks, we'll start a sprint to improve the GUI. We welcome
feedback, so that we can prioritize properly before starting the sprint.
More details can be found here:
"Raise your quality standards as high as you can live with, avoid wasting your time on routine problems, and always try to work as closely as possible at the boundary of your abilities. Do this, because it is the only way of discovering how that boundary should be moved forward."
"We all like our work to be socially relevant and scientifically sound. If we can find a topic satisfying both desires, we are lucky; if the two targets are in conflict with each other, let the requirement of scientific soundness prevail."
"Never tackle a problem of which you can be pretty sure that (now or in the near future) it will be tackled by others who are, in relation to that problem, at least as competent and well-equipped as you."
Here is an interesting blog entry by Shane Paterson that explains why a Naval Architect is called Architect. I don't quite agree with his suggestion to change Solution Architect to Solution Engineer, but that is another question.