Hi Tudor,
I found your visualisation very interesting, and wondered about one
thing linked to your blog post and if I got it right.
The visualisation you're showing is able to show, at the single class
level, if a class is more or less regular (i.e. tidy == well designed?)
but you show that it will loose very shortly it's tidy shape if the
classes it joins to are added to the visualisation. And I wondered if
this was a choice on the graph layout algorithm you've choosen, i.e.
that maintaining the tidiness of the class could be done with a
different layout algorithm? Maybe one which has a measure of tidiness of
the class at the local level, and weight it against the position and
attraction of its links to the other components in the application?
In the mean time, I'm slowly discovering we have amazing software
architecture visualisation tools :) Would really like to setup a project
on that if I get the chance.
Regards,
Thierry
Le 03/10/2013 23:34, Tudor Girba a écrit :
Hi,
I built a new visualization that has two goals:
1. show how the architecture of a system is fluid rather than rigid.
2. look good and serve as advertisement device for Moose, Roassal and Pharo.
A description of mainly point 1. can be found here:
http://www.humane-assessment.com/blog/system-attraction/
I already used it as a splash screen for a couple of presentations, and
it catches the eye.
The code can be found in Moose, in a separate tiny FAMIXSystemAttraction
class. You can invoke it on any class group (note: it can take a long
time to render for large groups).
Cheers,
Doru
--
www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
