Feature request/discussion: Trace to requirements

Hello.

I was thinking about creating a tool which would add traceability from code 
and doxygen pages to "requirements". Requirements traceability analysis (in 
my professional experience) seems to be a major gap in existing tools out 
there today.

Basically, I'm thinking of adding two tags:
@traceTo (output) and @traceFrom (input/source).  Perhaps more future advanced 
requirements would define layers/groups of traces (from Software Designs, 
Software Requirments, System Requirements, etc).

In general, I think this could create:
1) Hyperlinks to source requirements in a page
2) Pages of requirements analysis, specifically: Trace matrix, Code that has 
no requirements, Code that has no output, etc.

I'm still working out how to interface with requirements databases / where the 
requirements would be stored. But before I started any more in depth 
research, I figured I would post a query to this mailing list and see if you 
have either a) thought of this before / started implementing down this road 
or b) know of others that have.

Greg

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/