Re: Feature request/discussion: Trace to requirements

Well,  I "fat fingered" send instead of save...

I was going to say that test cases are constantly added, and software
requirements may trace to different code in different release streams.  

Perhaps, rather than trying to maintain a set of "traceability links" in
code, we could maintain a unique ID for each "set" of code (i.e.,
function, feature, API,.....).  We could then automate traceability
linkages in a database.

Other ideas ????

Regards, 
Larry 


-------------------------------------------------------------------------
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/