| || |
Dynamic Requirement Numbering
We are implementing TestDirector and if I use the Requirements Tab | View | Numeration option TestDirector automaticly assigns numbers to Requirements. This looks great, however if you delete a requirement (or parent folder) above another requirement TestDirector automatically reassigns the 1st requirement number to the 2nd requirement (parent folder).
I am just looking down the road and think this may be a nightmare to try to regulate. I was just wondering
1) Is anyone using the TestDirector Numberation.
2) If so how are you handling this.
We are thinking about adding our requirement number to the Requirement Name field.
Re: Dynamic Requirement Numbering
Their 'numeration' is meant to be dynamic. It actually assigns a 'requirement ID', that by default, is not set as one of the fields you see on the page. This number does *not* change if you delete requirements. However, you might consider *not* deleting requirements... they should probably, for change control purposes, be left there and deemed invalid, or what have you - perhaps moved to a 'Refused' folder? Or marked as "Reviewed - Refused" as opposed to "Approved"?
At any rate, if that number doesn't give you what you need, I would just create a new field that's a number you assign - keep in mind with that, however, that it will have to be set manually, so then you have 'human error' probability in there!