Managing use case requirements

[Robert Sheridan]

We are identifying our requirements in advance and mapping them to use cases that will deliver them using realisation links.  In some cases these are existing use cases that will need to be updated when the new requirements come into scope so these use cases have delivered and pending requirements associated with them.

I am looking for a way of when we generate documents they only include the pending requirments and was wondering if anyone had any suggestions.  I had thought to make the delivered requirements internal but have not found a way to move an external requirement into a use case.

thanks
Robert

[Ian Mitchell]

My advice would be to avoid Internal Requirements: there's little to be gained by making them internal, and you lose the ability to give the Requirement an independent identity, and link it to other elements (people, issues etc).
As for printing just the requirements of a particular status, I can't speak for the EA RTF generator, but eaDocX has no problem with this.