On Mon, 2007-07-02 at 15:51 +0200, Tudor Girba wrote: Let me first clarify this design decision: - As we are working with tuples in Crocopath, changing the representation as well as adding additional measurements in the future (which is likely to happen) requires changing all our querying scripts every time. - Secondly, some measurements (Coupling & Cohesion) are calculated as a post processing step. Being a seperate entity, it is easy to append them to the fact base. This means that it was pure convenience to implement it like that. However, there is a difference in what constitutes our meta-model and how we put in in a certain file format (read RSF, or, MSE). The presented meta-model is extracted from our RSF representation. Producing MSE with 'inline' measurements is not a problem for us. Therefore, if you want to make it an attribute of the respective entities that's fine for us. Another option that you might consider is gathering measurements per entity in a QuantitativeData entity - which would only double the amount of objects in the system at most. cheers, Bart -- 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