|
From: Rob H. <ro...@in...> - 2006-07-13 11:19:56
|
Indeed - we have Juergen! Previously he used JDepend to check for cycles and then would fix them. Now he uses a tool called SonarJ to do this. In the coming weeks Juergen and I will be working to roll out SonarJ across the entire team to make sure everyone can keep our package cycle count as low as possible. Regards, Rob On 13 Jul 2006, at 00:09, Thomas Risberg wrote: > Rob, > > You beat me to it :) > > Thomas > > > On Jul 12, 2006, at 5:44 PM, Rob Butler wrote: > >> Even better, they have Juergen! >> >> Hi Juergen. ;) >> >> Thanks again for making the spring framework so great. >> >> Rob >> >> --- Ivica Aracic <iv...@gm...> wrote: >> >>> Dear Spring developers, >>> >>> my name is Ivica Aracic, I am a PhD assistant at the >>> Darmstadt >>> University of Technology. >>> My research is concerned with the question how >>> graph-based software >>> visualizations can facilitate reasoning about >>> software architectures. In >>> the context of this work I have analyzed >>> architectures of prefuse >>> (http://prefuse.org/), jedit (jedit.org), and >>> spring. >>> >>> Except of spring all of these projects had some more >>> or less bad >>> dependecy cycles at the architectural level, making >>> the comprehension >>> difficult. However, after analyzing spring I was >>> surprised that there >>> was not a single cycle at all in the dependency >>> graph at the >>> architectural level (see screenshot). So my question >>> is, how do you >>> ensure this property in your development process. >>> Are you using metric >>> tools or some other tools to regulary check >>> dependencies at the >>> architectural level? >>> >>> Screenshot: >>> >> http://www.bytelords.de/public/spring-architecture.jpg >>> >>> Best Regards, >>> Ivica Aracic >>> >>> >>> >>> >>> >> |