Apart from my momentary nausea initially invoked by the concept of automatically induced heirarchical requirements....
Let me add this.
Although TK is (as usual) right, I reckon that "this way lies madness".
A requirement is a reqirement is a requirement .. etc
From the point of view of 15 years as a system tester, any "parent" requirement is immediately overidden, or at least subsumed by its' children. There is no, I repeat, no point in producing heirarchical requirement structures other than to prove to someone who cannot implement systems that their incomplete and anachronistic view of the world is incomplete. Further, there are no, repeat no, dependancies between requirements ... unless they are ill formed ... I'll leave that at an exercise for the reader.
A final plea, before they commit me finally ...
To all requirement writers,
ESCHEW OBSFURCATION, (please). Do not, do not, do not try to produce heirarchically structured requirements.
(The nice lady with the hot chocolate is calling me now, I must away..............)
regards
bruce
and you thought I'd stopped raving
