Dependency Analysis is a special form of work item analysis in that it links the files directly to their work items. Figure 1 shows an example graph which I will discuss afterwards.

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

Dependency Analysis.png
Figure 1 - Directed graph of a dependency analysis

The first item to note is that unlike the regular analysis, the files are not grouped by changeset and in fact every file shows up only once.
The second item to note is that the file names are just file names, not file names + changeset number as they were on the regular analysis.
What this allows you to do is that a file was associated with many different work items that may all lead back to different requirements. It also lets you see how many different requirements have effected a file. From this you can hide any links you want (to get Figure 2 I have hidden all of the intervening links between the requirements and the files) and view the graph as a Dependency Graph as shown in Figure 2.

Dependency Analysis 2.png
Figure 2 - Dependency Graph

What you are seeing here is that if I make a change to Doc 1.txt I am going to potentially effect both Story 1 and Story 2. From a testers perspective this provides insight into what tests I might have to run to verify that there are no regressions and from a developers perspective I might screw up two requirements.

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


No comments yet.