Requirements Numbering and Moving

[Doug Blake]

I have a couple of issues with the numbering of requirements.

Level numbering would seem to suit my application at first sight, but level numbers arent fixed and I need fixed numbers. The auto numbering doesnt work since its not hierarchical. New elements usually fit themselves into the top of the tree, so all numbers get incremented. Then I have to MOVE DOWN the element to the correct place in the tree. I think it would be better to add new elements to the bottom of the tree where they take up the next level number.

Also, if the number of elements is large, moving elements via a context menu, one place at a time is too slow. Drag and drop would be much better in the same way that it works in your favourites tree in Internet Explorer. You can drop between or on items to move urls to the current or lower levels.

[qwerty]

If you need to use EA as your primary RM tool you should make yourself familiar with automation. To get unique IDs you will need according tagged values which can be set by automation. Be aware that it's quite tricky to keep them consistent.

An alternative is to use RaQuest (no idea whether that is still supported, but I guess so) or a "real" RM tool from where you just mirror your requirements.

q.

[Takeshi K]

For your information, RaQuest does not hierarchical numbering. But with RaQuest, you can specify prefix to each Package and use multiple auto-numbering.

Recently RaQuest is released every month or two months, still supported:-)