[Pharo-dev] [ann] system attraction view

Tudor Girba tudor at tudorgirba.com
Fri Oct 4 08:14:20 EDT 2013


Hi,


On Fri, Oct 4, 2013 at 1:41 PM, Goubier Thierry <thierry.goubier at cea.fr>wrote:

> 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?
>

My argumentation is that if we look at a class isolated it will have a
certain shape, and because we are exposed to this view (the IDE is always
showing me only that) all the time we will optimize it such that the shape
is tidy. But if we look at the class in the context of its interactions the
shape will be less recognizable. The chosen layout is a very simple one,
and the goal is not to say whether the structure is good or bad. This is
neither good nor bad. It simply argues how steering the architecture has to
take these forces into account.

In the mean time, I'm slowly discovering we have amazing software
> architecture visualisation tools :)


They really are amazing :). If you want to get more information about it,
you can join the Moose mailing list:
http://www.moosetechnology.org/about/contact

Would really like to setup a project on that if I get the chance.
>

What do you mean? What kind of a project?

Cheers,
Doru


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/<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
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131004/e8b36267/attachment-0002.html>


More information about the Pharo-dev mailing list