One of the items that seems to be missing wrt Relationship management is listing items that don't have a relationship, either by folder or by group. The traceability matrix can get you there, but not if you have a large amount of requirements, like I do. As I've been updating my requirements from the last year+ of development, I've been updating relationships, and finding that sometimes I don't have a derived requirement for a system level requirement, or vise-versa, but it's hard to find out where those are.

This could be shown in something as simple as an extra column in the folder table with # of relationships. But that may not give the full picture, as a system level requirement may relate to another system level requirement, and thus it would be misleading that there might be a derived requirement for that requirement.

Another idea would be to add a filter indication for 'relationship' and check for 'derived', 'related'. But then it's tough to indicate 'the absense thereof'.

Something a bit more versitle would be something akin to the 'impact analysis' for folders and groups where you could see one of two tables: 1 with item ID's, Short Names, relationship counts for each type (derived, related, etc), or 2) a list of items that don't have any relationships. Clicking on any column would take you to that item. You would certainly want a 'back' so you could get back to where you left off in the list.

All of this really falls under the concept of traceability analysis to make sure that system requirements have derived requirements, test cards, designs, etc. and that there isn't a leaf child (e.g. a low level requirement that doesn't have an originating requirement). So although there is a good start to what you have so far, I think this aspect of the system needs some more features that allow better management and snapshots of where things are in that process.