2 Jul
2007
2 Jul
'07
3:51 p.m.
Excellent. I added it to the wiki.
I noticed you use Measurement.
We used to have Measurement as well, but this proved to induce a lot
of overhead because we ended up with tons of Measurement objects in
memory. As a consequence in our current FAMIX, we store measurements/
properties as attributes directly in the entity Class. For example,
for number of methods, we would have a FAMIX.Class.NOM attribute,
while you would have a Measurement object.
Would it be a problem for you if you would adapt your tools to not
have explicit entities for Measurements?
Cheers,
Doru
On Jul 2, 2007, at 10:29 AM, Bart Van Rompaey wrote:
On Sun, 2007-07-01 at 19:35 +0200, Tudor Girba wrote:
--
www.iam.unibe.ch/~girba
www.iam.unibe.ch/~girba/blog/
"No matter how many recipes we'll know, we'll still value a chef."
Hi,
LOOSE Research Group will also participate in the definition of FAMIX
3.0.
Radu, could you give a short overview of MEMORIA? I would say a UML
diagram would do just fine.
The input for the discussion up to this point is given by:
- SCG FAMIX:
http://smallwiki.unibe.ch/moose/famixmetamodel/
- SEAL FAMIX:
http://seal.ifi.unizh.ch/wiki/swiki/show/FamixCore
The UA likes to contribute their meta-model as well:
http://www.win.ua.ac.be/~bdubois/images/metamodel.png
Its a RSF-alike model transformed from FAMIX CDIF.
cheers,
Bart
Cheers,
Doru
--
www.iam.unibe.ch/~girba
www.iam.unibe.ch/~girba/blog/
"Every thing has its own flow."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Bart Van Rompaey
Lab On Reengineering
Dept. of Mathematics and Computer Science
University of Antwerp
Office location: CMI - G.2.22
Office phone: +32 3 265 34 05
URL: http://www.win.ua.ac.be/~bvromp