1) If the relationship window is open, double-clicking on an item in the project explorer window would be equivalent to selecting on an item and then 'edit relationship'.

2) It might be nice to have the exporer window on top of the relationship window.

3) As I've been adding a lot of relationships to existing requirement pair(s), I keep having to 'return' to a folder after I select the relationships from another folder. For example, if I have two folders:

Sys Requirements (Items A, B, and C)

SW Requirements (Items X, Y and Z).

If I'm going in order in the Sys Requirements folder, and select 'edit relationships' for A, then select it's relations (say X, and Y), I 'end up' exploring in the SW requirements folder. I then have to 'return' to the Sys Requirements folder to select B, then do the same.

If there was a way to have a 'tripple' view: 1st column 'pane' would have the edit relationships and 'master' explorer, a 2nd column 'pane' would have a 'slave' explorer that I select items from, and the 3rd would be information for the 'master' explorer item AND the 'slave' explorer item (vertical placement).

I realize that the trace matrix would be a much easier format, but  I have so many requirements, it's not really feasable to handle it this way.  If the matrix could be worked at a folder level (instead of group), this might be sufficient, but I think this other approach might be useful under normal circumstances. For example, as I'm developing Group A information (say requirements), and want to also work Group B information (test cards), I can quickly add items to either group and select relationships without having to scroll between the two different groups.