Yesterday, I visited an interesting presentation from Tudor Girba. He showed us several ways for visualize code. One of the most interesting visualization was Code City.

 

(ArgoUML from http://moose.unibe.ch/tools/codecity)

 

I couldn’t wait to visualize our current software project. First of all, you have to create a MSE file of your code. The MSE file as a generic file of your source code. This is done with iPlasma, as described here http://moose.unibe.ch/news/iplasma-to-moose-screencast.

 

After you have created an MSE file, you can now visualize your code with Code City. Just download it from http://www.inf.unisi.ch/phd/wettel/codecity.html, run it, import the MSE file and create your city. Enjoy!

 

For better code analysis, I changed the configuration of the “buildings” in my city. I changed the width and length of class element …

… to a linear mapper based on the lines of code.

 

Code City is very helpful to compare different parts of the application and to just visualize the software!

 

 

 

 

1. I am glad you liked it. I am sure Richard Wettel, the author of CodeCity, would be pleased to know that, too

   Comment by Tudor Girba — 12.3.2009 @ 22:48

2. ” … For better code analysis, I changed the configuration of the “buildings” in my city. I changed the width and length of class element …”
   IMHO _better_ is relative: I would suggest the following: In our project metric X is more suitable than metric Y …
   Reason: A metric X is not better then metric Y. It may be that you are not interested in X, or X has no meaning for you in the current situation.

   Comment by Frank Buchli — 13.3.2009 @ 09:08

3. Frank, that’s right. I just wanted to express that there is the possiblity to change the parameters of the building. And that you should know, what you’re painting

   Comment by Stefan Jäger — 13.3.2009 @ 10:39

Name (required)

Mail (will not be published) (required)

Website