We have implemented a traceability matrix in Contour that will show any two groups. Such that you could quickly view the relationships between all test cases and requirements. Not only that but you can quickly add a relationship by clicking on the xy cell. This was a very exciting feature for us until we tried it with hundreds of requirements, it's just too much data for anyone to try and view at once.
One solution would be to use filters. For example you could build the matrix based on "all Requirements for a particular release that are not complete" as one axis and then, "all Test Cases that are complete for a particular release". This would reduce the number and ensure that you're working on only what matters to you.
Any other ideas or thoughts? Maybe there is a better view all together. (For example we are implementing a trace tree)
When we work on relationships between levels of requirements, we often work within only a few folders (or folder hierarchies) at a time. Would it be possible to filter a trace report by allowing us to select one or more folders within one of the groups? This would allow us to create a report based on the organization already present in the folder structure.
In a large dataset, a filter like this might produce a long, skinny matrix, if a matrix graphic were produced. That would be good for some uses, maybe unwieldy for others. For example if I need a summary of test cases linked to a particular requirement folder & subfolders, I'd want a matrix with the selected items on one axis, but see the other axis limited to just the items with relationships.
Another thought: would it be possible to somehow show the folder structure for items in the Traceability report? It would be helpful if that bit of organization was not lost in the report.
We are planning on including additional ways of filtering data. For example we where going to include the ability to select tags as part of a filter but we could also include the ability to select one or more folders in a group, but I don't think that completely answers your question.
I'm actually curious to hear more on how you're using the trace matrix or the report. In my mind the matrix table is good for quickly seeing items that are missing a relationship. So for example in my project it could be important to have each Feature trace to a Test Case to ensure 100% coverage. The matrix would show any gaps. Your comment seemed to indicate that you just want to see a summary of only the items that already have a relationship.
The reason I bring this up is because traceability in general is such an important part of RM and Contour that we are planning on separating out a whole relationships page. This will include a graphical trace diagram, a trace tree and the matrix. As well I could see including features like what you're asking where you can customize the view to show relevant items. Could you provide a couple of quick scenarios on how your team uses relationships to manage data?
As far as the report goes this is very customizable. It should be possible to produce a report like what you seeking in Contour today. I'll double check but basically you're looking to combine the SRS report with the Traceability report?
I'll reply the the last point first.
I'm working on two large requirement Groups (SyRS and SRS). Each group is organized with folders (the folders work great). In fact I rely on the Project Explorer and folder structure for navigation and get a bit lost when I encounter an item's short name standing alone somewhere, like in a Relationship Table or a Traceability Matrix. So I developed a work-around by adding an abbreviated folder name to the beginning of each short name. Now when I see an item short name, I know where it lives in the hierarchy and what the Item is there for.
So the Traceability Matrix and Relationship Tables are easier for me to read and navigate because of the Short Name style I use. But the short name work-around is a bit of a pain.
So I guess my original question was too narrow (and confusing - wrote "Traceability Report" instead of "Traceability Matrix"). What I really need is a capability that helps me recognize the hierarchy of an item when I see it somewhere outside the Project Explorer.
Ah, yes. I know what you mean. I struggle with that as well. Even using backstage, or a traditional wiki, or computers in general make me feel that way. That was the impetus for the "find me" feature but that assumes you've selected the item. Sounds like you want some kind of quick reference without having to leave the current view.
I like the idea of providing a quick view into an items location. For me, that not only includes it's folder but could include it's tags as well. (Some customers are using the tags like folders)
Not quite sure how this would get implemented. Maybe we could provide a small icon by an items name or id that when clicked shows a small bubble with the relevant information...just thinking out loud.
Derwin & Paul -
I've posted other thoughts under some Feature Request posts:
Feature Request: More on Relationships
Feature Request: Batch update on Relationships
Feature Request: Relationship table shows status
