To prevent discovering later I already had this requirement and having to combine them.

Add and edit block diagrams, state diagrams, etc.

This way, I can more easily add an empty use case

Use an algorithm that looks at the requirements that are linked to the version. Perhpas with the effort and risk values.

I'd like to see a very detailed real-world sample for the product including a step-by-step walk through and several requirements iterations with a fictitious product. This should be provided as a ground-up tutorial with a completed DNA project illustrating the final product (MSDN style).

adding a req/cat to a selected category is usually the right thing to do, but sometimes a sibling is what I want. Perhaps holding down the control key while adding a requirement will place it as a sibling.

WBS could be auto-generated based on the hierarchy.

Would help with categorizing requirements

Terms like Requirement, Section, Version

Syncronize dna requirements and data using a Microsoft Sharepoint server

Syncronize Dna requirements and data using Micrrosoft Team Foundation Server