Look at using a spreadsheet. However anyway you set-up a Traceability Matrix, using a spreadsheet, a Free tool or Test Director the requirements need to be finalized before you start creating Test case or the traceability matrix.
When the requirements change - everything else changes so you would be best waiting for stable requirements and then using you Test Director Tool.
Originally posted by lynneM: the requirements need to be finalized before you start creating Test case or the traceability matrix.
<font size="2" face="Verdana, Arial, Helvetica">lynne.
This would be an overstatement in many orgs not following a 'traditional waterfall' development methodology.
A more typical approach would be to identify 'stable' requirements incrementally and build the test cases and traceability matrix incrementally as well. Granted, there is rework associated with the 'stable' requirements that get 'wobbly' and you might even have to throw out some test cases [img]images/icons/mad.gif[/img] but the incremental approach allows you as the tester to jumpstart the case design process and identify potential testing problems earlier in the cycle.
The difficult part is getting to an understanding with your project members regarding what constitutes a 'stable' requirement, the impacts of making unexpected changes, enhancements v refactoring, etc.
You are correct AND retro. [img]images/icons/cool.gif[/img]
I would go for stable - however at the point where this is started I would expect to see Change Control done for the changing of requirements so that overall cost and effort of the change is identified.
To determine the stable time you need to have something set-up in your process - can be getting business signature, could be a PM decision point or the agreement that the requirements are ready for detail design to begin.
However I strongly believe that nothing should be built from requirements until the "stable" point has been reached - leads to inefficient rework.
If I used pen and paper for a traceability Matrix - I would not do this until I had finished testing the app - it would be way to expensive in erasers.
I have not failed. I've just found 10,000 ways that won't work" --Thomas Edison
For me the spread sheet worked for couple of projects. No issues with it except continuous updations whenever any changes to existing requirements or test cases.
Even using a tool wont be that simple for a task like this.
If you are specific abt tools then TestDirector is a good one.