[Forgot Reply-All again...] You're probably aware of these dependency analysis tools, and the paper by Robert Martin. I've collected a set of dependency links I've come across in my Furl archive. You can see them here if you're interested: http://furl.net/members/shadeltd/dependency%20analysis
--Tim On 7/21/05, Aaron Kagawa <[EMAIL PROTECTED]> wrote: > Hey Christoph, > > I think a dependency reducer would be interesting. But, I'm not sure about > the exact calculations of the reducer. For example, I'm not sure how to > interpret the average dependencies. I suppose the best thing to do is to > give it a try; besides it shouldn't take that much development effort. > > One calculation that might be interesting is something similar to the issue > reducer that calculates the delta of outgoing or incoming dependencies. Or > maybe not, because plotting the sum of incoming/outgoing overtime should > allow us to see the changes. Anyway, I think the best thing to do, is to > use a GQM type strategy in determining what reducers would be most useful > in answering a Question. > > BTW, I've been wanting to add a Dependency entry into the > DailyProjectDetailAnalysis for a while now > <http://hackydev.ics.hawaii.edu:8080/browse/HACK-251>, but wasn't quite > sure what data it should provide. For example, is the sum of all > dependencies actually interesting? > > thanks, aaron > > At 10:44 PM 7/20/2005, you wrote: > >Hi guys! > > > >What do you think about having a telemtry reduction function which can > >plot stuff like 'average dependencies per class/method/package', 'sum > >of ingoing' , 'sum of outgoing' or 'sum of all dependencies', > >filtered by workspaces? > > > >Would this be useful? > > > >Cheers, > >Christoph >
