A basic analysis is just a simple work item relationship display. Figure 1 shows the output.

For any item underlined, double-clicking it will open that work item in Microsoft Test Manager at this point

Basic Analysis.png
Figure 1 - Basic Output

There are a couple of things that may be interesting to you here. The first is the direction of the arrows - they only go one way even though all links are bi-directional in TFS. What Figure 1 is telling you is that a User Story (Story 1) Affects a task (Affects 2), has a successor task (Successor 5) and has two child tasks (Task 1 and Task 2). It also shows that it is tested by a test case (Tested By 6). Bug 9 is also tested by this same test case (Tested By 6). At the same time, Story 1 is affected by a task (Affected By 1), is a successor to another task (Predecessor 3) and is related to another task (Related 4).
To achieve this graph, I selected Story 1 from the list of work items.
Holding your cursor over each of these links will describe the link in more detail.

A variation on this type of analysis is achieved by selecting the Changeset link type from the list of link types as shown in Figure 2.

Basic Analysis with Changesets.png
Figure 2 - Basic Analysis with Changesets

Here, each changeset is associated with the work item that it was related to upon check in (or that was added afterwards) and each file in the changeset is grouped in that changeset. Here you can see that Doc1 shows up in several changesets. You will also notice that this graph shows Story 1 and Story 2.
To create this graph I selected Story 1 from the list of work items and all of the link types.
I will cover this in more detail in another section but what happened here is that starting at Story 1 it determined that Task 1 is a child of Story 1 and that Changeset 33 is associated with Task 1. Then it determined that Doc1 was part of Changeset 33 and it looked at all of the other changesets that Doc 1 is a part of and traced those back to the work items which is how Story 2 got on this diagram.

A third variation is grouping everything by Iteration. Figure 3 shows the results of this analysis.

By Iteration.png
Figure 3 - Grouped by Iteration

This is a different project that shows all of the work items in all of the iterations.

Last edited Mar 21, 2010 at 7:48 PM by jefflevinson, version 3


No comments yet.